Personalized Community is here!
Quickly customize your community to find the content you seek.
Check out the latest Sales updates!Learn about the key capabilities and features of Dynamics 365 Sales and experience some of the new features.
Download overview guide | Watch Sales video
2020 Release Wave 2Discover the latest updates and new features to Dynamics 365 planned through March 2021.
Release overview guides and videos Release Plan | Preview 2020 Release Wave 2 TimelineWatch the 2020 Release Wave 2 virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
I'm trying to configure a workflow that will create a new order record when the status is updated. When i click on "Set Properties" I get an error looking like this. I know that there are no problems loading or accessing the order entity and the form.
Any idéas on how this can be solved?
This is a general error and does not contains any useful information.
I would recommend you clear the browser cache or change another browser to see if it works.
Also, could you provide a screenshot of the workflow?
This is very generic information.
Please close the workflow window. Clear Browser Cache and Try again.
If you face the same error continuously, please contact MS support.
The same problem still exist after clearing cache and trying different browsers, both egde and firefox (I usually use chrome)
I can't see any problems with the workflow itself. I just can't open the set properties form.
i had a similar problem, i solved it just adding a step:
add an update step where you update the record created in the create step.
I dind't check if my problem is now solved, but the workaround worked. Good luck :D
If you are still facing this issue then I would request you to submit a support ticket so that Microsoft can assist you on this issue.
Business Applications communities