Personalized Community is here!
Quickly customize your community to find the content you seek.
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
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 1 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
Recently, we were working on SLA. We provided necessary conditions in Applicable When and Success Criteria sections. In Success Actions section, we wanted to update Customer Record(OOB entity “contact” renamed) and clicked on Set properties as shown below:
On click of it, we got “Invalid Argument” error as shown:
To fix this issue, we copied the URL of this window and decoded it. We got the root cause of this issue by looking at the decoded URL. The decoded URL contained the following piece of information:
Error Details: Wrong type of attribute UI properties passed to the attribute “custom_field”.&RequestUri=/SFA/Workflow/entityform.aspx?entityFullName=contact.regardingobjectid&entityname=contact&mode=1&primaryentity=task&readonlymode=true&relatedattributename=regardingobjectid&stepId=UpdateStep30&workflowId=712b088a-9dc1-4b3a-acc2-a1e8e8ebcacf&user_lcid=1033
We found that one of the custom field(“custom_field”) we had created was causing this issue. This field was put on the form.
We understood the problem. We had created a field with same schema name earlier with “Single Line of Text” type and later we realized that the field should have…
View original post 71 more words
Business Applications communities