Tip #731: Hide and protect your custom CRM API

Protect yourself by covering

Yesterday we illustrated how you can wrap some server-side functionality as a custom API to be consumed by the developers. One of the undesired side effects is that business can now poke their nose into the API when building workflow processes: If your API is a smoking gun and you don’t want business to accidentally […]

Tip #676: Keep your pants on and timestamps intact

Illusion of integrity

Let’s say you have a field that requires complex calculations that are impossible to express as a calculated field. For example, the requirement could be to figure out the “real” full name for a contact taking into account the country, ethnicity, contact’s preferences, their royal title, and a phase of the moon. The first reaction […]

Tip #637: Tipster guide to Microsoft Flow – codeless integration between CRM and other apps

Friday Flow

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 […]

Tip #523: Tipster guide to invoking custom actions without code

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 […]

Tip #123: Waiting for Godo in CRM workflows

Wait 1 day with timeout

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. […]

Tip #93: When to cancel workflow

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 […]