Dynamics 365 Cannot use child workflow because child workflows only support embedded connections Recently we have been playing with Child Flows in Power Automate (Microsoft Flow) as part of a solution with Dynamics 365 however when we selected the child flow to be executed we received the error "The workflow with id '9017e2ce-1501-ea11-a811-000d3a6aaf7c', name PowerApp -> Update a record cannot be
Dynamics 365 Unable to import solutions Dynamics 365 V9.1 (Error Code 8004801a) Came across another fun issue today with Dynamics 365 V9.1 that caused me a small inconvenience. Looks like there is another attribute being added to the FetchXML on new views that isn't in the correct format to be supported in the Schema for import. This leads to this. On
Dynamics 365 Supported Workaround for the Chrome Quick Create bug While researching the Chrome Quick Create Bug I came across a post to enable "Legacy Form Rendering" that it would work however it causes other issues. This morning while reading through some other articles it kept coming up. This spurred me to actually try it and lo and
Dynamics 365 Quick Create Form not working in Chrome An issue got raised to me that the Quick Create forms we not working intermittenly. I took a quick look around I found the the quick create forms would work the first time they were used but then failed to load for every use after that. After searching around for
