Sometimes inspiration comes from unlikely sources. In this case it was not having written a tip for a few weeks and knowing George would meter out Spießrutenlaufen if I did not post soon. Thoughts of such things give one time to reflect and so I am going back to basics and addressing one of the […]
Tip #1109: Add variables to your workflow (when Actions don’t work)
Back in Tip #736: Add variables to your workflows, George ‘bringing discipline to the rest of us’ Doubinski suggested the excellent Tip of using an Action to simulate a variable in Workflows. I went to use this Tip this week for a lookup and, to my chagrin, found there is an exception to the Tip. […]
Tip #1040: Why Can We Stack Values in Workflow?
Back in the days when George Doubinski used configuration, he talked about using constants in workflows.However, this is only the tip of the configuration iceberg. Just above our Default Value box we can stack values for insertion into our field. What does it mean to stack the values and what happens when we do? When […]
Tip #1015: Remove mandatory and locked fields
Tip 1006: “Remove the stuff you don’t need. Doing tickets for internal helpdesk and don’t need entitlements? Turn it off and remove it from the form.”. Easy for Joel to say. Dynamics 365 has a lot of baggage, both good and bad – let’s see what happens when I create a new Case form. We […]
Tip #741: Cannot update fields with workflow
When trying to update a record with a workflow, you may find some fields are grayed out on the form and cannot be updated, even if the field is not read only on the form. This can happen when a field is on the form multiple times. Go to the first instance of the field […]
Tip #293: What’s the point?
Welcome back to the Tipping Truckstop, where the tipsters gather to discuss pressing CRM matters. It’s DeCRMber already and the trucks are all festively decorated for the holiday season, so grab a cup of eggnog and pull up a stool. Today’s question is: In CRM 2013 and 2015, we have a field data type of “Floating […]