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 1Discover the latest updates and new features to Dynamics 365 planned through September 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 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
I have a CRM (2015) workflow that runs on Accounts when the primary contact changes. When a user views any account record in the CRM iPad app, it is causing that workflow to fire. Upon further investigation, it looks like the mobile app is always saving records when you navigate away from the, (even when using the back arrow to return to the list of records).
Is this normal (the iPad app always saving records when you view them)? If I look at the same record in the web app after just viewing it in the iPAd app, the modified by and modified on is definitely being updated. This is more than just a record save though, because it's triggering a field change workflow. I just want to make sure other people have the same behavior so I can rule out a customization?
If it's normal behavior for the iPad app, how do I write a field-change workflow rule that accounts for changes correctly?
Do you have auto save enabled on the org?
If you disable it, this shouldn't be caused. Auto save will cause similar issue on web app if someone is doing interim changes and it triggers, workflow will fail then as well.
By experience, it probably triggers more frequent on IPAD and mobile apps on user actions.
I think the behavior is different:
If I navigate to an account record in the web client and then navigate away without changing anything, it never auto-saves. If I do make a change to a field causing it to auto-save, it does save the account, but it doesn't trigger field change workflows for different fields.
In the iPad app, if I navigate to an account record, and then navigate away without changing anything, it not only auto-saves, it triggers the changed field workflow.
If someone could at least confirm that they are experiencing the same behavior, that would be a big help:
We found the issue. There was a form script that called a function that only ran on mobile. It included a line that was forcing a submit on the primary contact field:
Commenting it out resolved the issue. Looking at what the function this was called in was supposed to so, it doesn’t look like it was necessary.
Business Applications communities