Breaking news from around the world
Get the Bing + MSN extension
Now Available in Community - MBAS 2019 Presentation Videos
Catch the most popular sessions on demand and learn how Dynamics 365, Power BI, PowerApps, Microsoft Flow, and Excel are powering major transformations around the globe. | View Gallery
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 TechTalks | Customer Engagement TechTalks | Talent TechTalks | Upcoming TechTalks
MS Connect Suggestion: Allow Parenthesis in Workflow Step Conditions
I have a Workflow related MS Connect Suggestion I’d like you to vote for.
I would like to request the facility to use parenthesis in Workflow Step Conditions in order to simplfy the creation of the conditions.
For example, currently a condition may need to be entered as:
VendorClass = “EU” and ItemClass = “IT” and CostCentre = “NEWCASTLE”
VendorClass = “EU” and ItemClass = “IT” and CostCentre = “LONDON”
VendorClass = “EU” and ItemClass = “IT” and CostCentre = “EDINBURGH”
And that is with only an or clause on one of the parameters. I might have 6 VendorClasses and 20 ItemClasses; it gets real big, real quick.
If parenthesis could be used, as in a mathematical equation, I could enter the condition as:
VendorClass = “EU” and ItemClass = “IT” and (CostCentre = “NEWCASTLE” or CostCentre = “LONDON” or CostCentre = “EDINBURGH”)
This would shrink the amount of work required to create anything but the simplest of workflow processes enormously.
You can vote of the suggestion here
Read original post MS Connect Suggestion: Allow Parenthesis in Workflow Step Conditions at azurecurve|Ramblings of a Dynamics GP Consultant
Business Applications communities