cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
bwilliamson
Frequent Visitor

Dynamics 365 Flow that triggers on update of a case

I have a flow that uses the When a record is updated action as its first step.  When a case is updated in CRM, the flow is crashing with the following message:

The property name '_slainvokedid_value@Microsoft.Dynamics.CRM.lookuplogicalname' is invalid; property names must not contain any of the reserved characters ':', '.', '@'.

This is the first step in the workflow, there are no inputs other than the CRM server name and entity, and it seems to be failing while reading the property list from the entity that changed.  This is Dynamics 365.

slainvokedid is a property in CRM, _slainvokedid_value@Microsoft.Dynamics.CRM.lookuplogicalname is not.

10 REPLIES 10
bwilliamson
Frequent Visitor

They have apparently been making changes on the server side to both CRM and this flow connector.  Where it was using incidents before, it is now using Cases in the update service, but the creation of a task is now broken.  Since about a week ago it has been running consistently without the metadata error, but I did have to recreate the entire workflow and remove the creation of the Task attached to the case at the end.

 

Helpful resources

Announcements
MPA User Group

Welcome to the User Group Public Preview

Check out new user group experience and if you are a leader please create your group

MBAS on Demand

Microsoft Business Applications Summit sessions

On-demand access to all the great content presented by the product teams and community members! #MSBizAppsSummit #CommunityRocks

MBAS Attendee Badge

Claim Your Badge & Digital Swag!

Check out how to claim yours today!

secondImage

Are Your Ready?

Test your skills now with the Cloud Skill Challenge.

Users online (66,419)