Apparently, for people who like bending their joints backward, Friday Flow is a thing. We’ve decided to join the bandwagon and in today’s video we will show you how to create a basic workflow between SharePoint and CRM using Microsoft Flow. Flow is a cloud service, currently in preview, that allow you to create automated […]
Hey, it’s Friday and time for another video tip. In the last week’s video we talked about how to create custom action, add parameters to it, define conditions and steps, etc. This week we continue by demonstrating how to call your custom actions from real-time workflows (or dialogs) without writing any code. Give us your […]
I recently received a frantic email from a friend testing an upgrade from CRM 4 to 2015. He was testing workflows, and they did not appear to be working, as the completed workflows did not appear in the workflow history for the record. It turns out that they were working, but when we had upgraded […]
This week’s tips all seem to be about workflows and here is an old favorite of mine. I always found it interesting how non-intuitive wording around Timeout condition pushed majority of developers to use rather convoluted but easier to read and understand Wait conditions when a workflow needs to be paused for a fixed duration. […]
In yesterday’s tip we suggested to avoid wait conditions altogether; but if you must use them: Combine waits and check condition. So you have a process that emails a customer service representative three days after the case is open. No need to email them if the case has been closed, right? After the wait, have […]
Workflow wait conditions can be very useful. Say you need to have an email go to a customer 30 days prior to their contract renewal, it can be tempting to use a wait condition. However, excessive use of wait conditions has a downside. Performance: each waiting workflow instance carries performance overhead. The more waiting workflow […]
If you decided to follow our previous tip and cancel workflows only when necessary, you may wonder what does the Set Properties button for this step do. As it turns out, stopping workflow has a single property called Status message: The best use of this property comes with the new real-time workflows in CRM 2013. […]
When a workflow needs to be stopped, workflow editor offers two choices: Succeeded and Canceled. The main difference is that Canceled status is considered to be an error which has the following implications: Log records are retained (if flag is set to retain logs for failed workflows). For real-time workflows the transaction the workflow is […]
As some people noticed, in CRM 2013 OnLoad event handlers are not firing after save of the form. This is by design as form saves and refreshes are now granular. That means that some of the code migrated from 2011 may not work as expected if it relies on OnLoad event being fired after every […]
Executing real-time workflows has it’s own security setting. It is in addition to and separate from executing a background workflow. Open up the security role, move the Customization tab, scroll down to Miscellaneous Privileges and assign the appropriate scope.
of the