Customer Insights - Segments - Expand output entity

Segments

Recently I found another new feature that allows to extend the output entity, generated when you define a segment, in Customer Insights.

Lets say, we create a new segment called "Promo Customers", that contains Customers that have earned more than 200 Loyalty points in your bonus programm and you want to market these customers.

You would navigate to Segments and create a new segment from blank:

First you define a name and can add a short description, explaining your segment:

Then you define the filter criteria of your segment. In this case our segment is based on a measure, that calculates the sum of all loyalty points per customer:

After clicking on save, your segment will be calculated:

Once the segment has been calculated, you can view it and you will see a list of all customers that apply to the filter criteria:

So we can see our segment has 158 members and a list of all the members containing all fields of their customer profile.

But what we do not see is how many loyalty points they have earned. We just now they have >= 200 points.

So far so good, but roughly a month ago a new feature has been added called "projected attributes".

Projected attributes

This feature allows to extend your segment output entity, with information used in your filter criteria. In our case the segment is based on a measure, which means we could add the information how many loyalty points the customer earned.

So we edit our segment and click on "Projected attributes":

Then we can select the attribute we want to add to our output entity:

We click on save and the segment refreshes. After refreshing an additional column has been added at the end, showing the loyalty points earned:

You might have noticed that the output is displayed as an array. The reason is, that you can not only expand a single value of a measure, but you could also have a segment based on a transactional entity, where more than one value could be returned. In this case you can also choose more than one attribute:

And if multiple transactions exist, the result is displayed in an array:

Comments

Power Automate Get absolute Sharepoint URL from document location

Document Locations If you enable Sharepoint document integration in your model driven apps, you can define for which entities the possibility to upload documents to sharepoint shall be offered and you can define a folder structure. Possible folder structures can either be based on account or contact, which means if you create child items (e.g. opportunities, activities, ...) sub folders are created below. If an entity is enabled for document management a "Files" tab is added to the form of your model driven app and as soon as you click on that tab a folder is automatically generated on Sharepoint. Once the folder has been created you have options to create new or upload existing file or to open the document location (folder) on Sharepoint: What happens behind the scenes is, as soon as you click on the files tab your model driven app checks, weither a "document location" for this item already exists, or not. The document location is an own entity in C

Send e-mails with a link to the record via Power Automate

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

Working with Optionset lables in Power Automate

Connector Types Power Automate currently offers 3 different connectors, to connect Power Automate with your Dynamics 365 instance: Dynamics 365 Common Data Service Common Data Service (current environment) Today we will look on ways how to retrieve option set labels via the different connectors, for our sample accounts: Dynamics 365 This connector should not be used any more , since in April 2019 it has been announced as being deprecated. https://flow.microsoft.com/en-us/blog/nine-new-connectors-in-april-and-improved-visibility-into-trigger-failures/ With the Dynamics 365 connector it was quite easy to work with optionsets, since it offered both the optionset value (int) and the optionset label (name) in the dynamic content: And here we go, these are our results: Common Data Service Since the Dynamics 365 connector has been deprecated, this is the connector you should use. If you perform a "Get record" or "List records&

CRM addicted

Search This Blog