CRM addicted

Measure templates Recently a new feature has been added to Customer Insights, which allows to create measures based on templates. If you select "Choose a template" various templates are offered, that allow the calculation of popular KPIs, like Average transaction value, Loyalty points earned or Time since last purchase: If you select one of the templates, e.g. "Loyalty points earned" a short description of the measure based on an example, the formula behind the measure and the data, which is required to calculate the measure, is displayed: As we can see, this template is based on activities and the activities need the following information: - How many loyalty points have been earned with a purchase - Activity timestamp of the purchase Which means we have to setup an activity first, before we can define our measure. Activities In this example, we have an entity called "posPurchases", which contains transactional data in the following format: To add a new ac

Automate Document Creation Recently I had the requirement to automate document creation with Document Core Packs. You can do this via classic workflows, like explained in this article: https://www.mscrm-addons.com/Blog/PostId/9776/automerge-workflow But on the one hand, whenever you open the solution explorer and want to add a new classic workflow, you are presented a message, telling you that classic workflows are already quite outdated and you should have a look at Power Automate. And on the other hand, this classic workflow references a CRM record (document template), so you will have to reconfigure it in each of your environments, since the template will have a different GUID accross your environments. So I had a look, how to achive the same via Power Automate. Trigger We start with adding a new flow, that triggers on update of a record using the Common Data Service (current environment) connector, since we can define the filtering attributes there, so that our flow doesn't tri

Environment variables Flows often require different configuration across your environments and this is where environment variables come handy. Environment variables allow you to store different configuration variables in each of your environments or to fallback to a default value. I just recently used them to define the "sender" (name of a queue) of a notification e-mail in a flow. Define environment variables You can add a new environment variable via the new maker studio (make.powerapps.com), by opening one of your solutions and click on New -> Environment variable: After having defined your default and environment specific value it should look like that: Using environment variables in a flow To retrieve the value of an environment variable, we add a list records action, where we search for the environment variable by schema name and expand the query with the environment specific value (stored in a linked entity): Finally we initialize a variable, where we either set the

Today we gonna have a look at how to send an e-mail with a link to a CDS record via Power Automate. In the good old classic workflows, you could directly reference the "record URL" from the dynamic data. But since UCI has been launched and you have the possiblity to target different apps, you already had to do a few more steps in the classic workflows as well. The URL to a CDS record consists of multiple things: CRM URL appid entity name record id So we will work this out one after the other. First we add a "List record" action to lookup the appid of the app, we target. We look for "model driven apps" and filter by the name of the app: Then we initialize a variable with the resulting app id: Then we initialize another variable and extract the CRM_URL: Then we fetch our records, where we want to send out a notification with a link, in this case we look for workorders fullfilling certain criteria: Now we compose the record URL: As a next step we create a new