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
First of all we need a text field to contain our alert. Initially I added this to the header of the record but found out that it is not possible (or, at least, I could not figure out how) to widen the field meaning my alert was being cut off. In the end I added a tab to the top of the form body and added the field to a section in the tab.
When blank the field is almost invisible so I clicked into it for the screenshot. I also turned off the label for the field as we do not need it.
Next, I set up a business rule to grab the user’s attention.
All the rule does is prevent the user from saving if the Alert field contains data and forces the user to clear the field first, making them acknowledge the contents.
Now we simply set up another Business Rule, Workflow or whatever we like to populate the Alert field. When this is done, we are set. For example, let us say we want to warn the user of all Accounts beginning with A.
When the user opens up a guilty record, they are confronted with:
Until they clear the message, they will not be able to save any changes to the record.
A word of warning though, Business Rules fire in the order they are activated so if you add a rule to populate the Alert field, make sure you deactivate and reactivate the Alert Rule afterwards so it checks AFTER the field is populated and not before.
A simple and effective alerting system which forces the user to read the message before interacting with the record. If you need such an alert and do not want to rely on a coder to adjust it as the business alert criteria change over time, consider this option.
Business Applications communities