Check out the latest features available in Dynamics 365 for Customer Engagement, including LinkedIn Connect, Voice of the Customer and Universal Resource Scheduling.
2019 release wave 2 Discover the latest updates to Dynamics 365Release overview guides and videos Release Plan | Early Access Availability
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 and Operations TechTalks | Customer Engagement TechTalks | Talent TechTalks
Using CRM 2016 on premise version 188.8.131.52
Upon create/update of some fields in a custom entity we fire a workflow . Depending upon the status of the record the workflow may then execute a child workflow which will update fields on the relevant entity. With our version of CRM 2016 the 2nd workflow encounters an error when being called and is stuck in a waiting state. Error details on the workflow is Workflow suspended temporarily due to error: Unhandled Exception: System.Data.SqlClient.SqlException: Cannot insert the value NULL into column 'WorkflowLogId', table
We have not updated our workflows or made changes to them and they work fine in current production which is still on CRM 2011.
Looks like there might be a reference broken somewhere. If you try to recreate the workflows do you still see the issue?
If you are setting any input parameters to the child workflow, please make sure that the records are active and the values passed to the child workflow are not null. If possible, can you share the details of the workflow configured which will help to analyze this issue?
There are no input parmeters. On the parent workflow if the entity record has a particular value it calls the child workflow to make updates to the record.
Looks like it may be a Microsoft bug that is fixed in version 8.2.1 and/or 8.2.2 according to documentation.
I added a 1 minute wait condition to the beginning of the child workflow that was failing. So far in several attempts it seems to have resolved the issue.
Please mark our answer as verified, if it has helped you to resolve your issue.
Business Applications communities