Relationship Insights, as part of Dynamics 365, has been a great feature, often used (and sold) as part of the Sales Application to be able to remind users that there are important deadlines or meetings coming up. In recent releases, the feature has now been made available to customise as part of public preview, allowing us to create custom insight cards to display to users (and teams) across the platform. This results in tailored and streamlined recommendations for users, allowing them to receive insight and take action quicker.

This post covers how to get started setting up a simple custom card from a custom entity.


  1. It would be helpful to ensure you have a model-driven app to test your new custom insight card. The Sales App has a Dashboard with them on out of the box, so if you’re rushed, you can always use this.

Setting Up

1. Open the sales app, and navigate to App Settings

2. Go to System Configuration under ‘Sales Intelligence’ and Accept the Conditions.

3. Click ‘Configure’ under the Assitant feature

4. You should then see the configuration screen for the Relationship Assistant. Turn on Preview (top right corner) and just take a short moment to review the screen. This screen is where you can order the importance of the cards and see all of the current switched on relationship insights, configuring high priority. Click ‘Create a new card’











5. You will need to confirm preview features, as, at the time of writing, this feature is in Preview. Select ‘agree’ to the terms and conditions (providing you do agree) and click ‘Enable preview features’ to proceed.

6. [Optional Step] You can now select a current card template to begin from, go ahead and click ‘Due date today’ and this should open Microsoft Flow. The example in this post is actually a more basic example and it’s easier to start with a blank flow if you prefer. (If you do, click ‘Create a flow from blank’).


Creating the Custom Card

Creating a custom insight card is surprisingly simple. You may notice the templates are all triggered on a scheduled basis, and whilst this is a great way to generate these insight cards, it is not the only way. I find they are also a great feature to trigger off an action, for example creating a specific record. The example below demonstrates this, where the trigger is the creation of a custom ‘Technology Association’ record, and also followed by a generic step of creating a new custom activity record called ‘Suggested Action’. The creation of an activity record is absolutely not a requirement of these cards and despite ‘activity’ being used in the terminology, activities, in general, are also not required. Even though you’ll see later it’s expecting an ‘activity ID’, you still don’t need to attach the card to an activity entity.

1. Create your setup for your Flow based on your trigger mechanism.

2. Select a new Action in Microsoft Flow. Search for ‘Card’ and select ‘Dynamics 365 Sales Insights’ and you’ll find the ‘Create Card for Assistant (Preview)’ action. Select this.

3. Select the action and ensure you expand out all the details.

Enter the following information:

  • Card Name: What will appear at the top of your card, displayed to the user
  • Title: What will appear below the Card Name on your card, displayed to the user
  • Description: What will appear below the title in standard font on your Card, displayed to the user
  • Action: Open URL or Open Entity (Record) – select one. To open the record, select Open Entity.
  • Action Input: Ensure you have entered the related URL or the entity GUID in here based on your selection in the ‘Action’.
  • Set Regarding: Set a regarding for your card. This is the entity form and record you will SEE the card (as remember, you can embed the relationship insights control on any form) See note below
  • Action Input Entity Type: This put be the same entity type to the GUID you put in the Action Input
  • Set Regarding Type: the same type you have entered in the Set Regarding. See note below

Some optional extras

  • Start Date: Now is the default to display a card from, you can use this field to override this and schedule future cards.
  • End Date: 24 hours is the default to display a card, this can be overridden if you enter a date in here.
  • OwnerID: The GUID of the user or team to specifically display this card to. A great way of filtering our and tailoring insight messages.

When you link the Set Regarding Type, what happens is it creates a relationship from the system entity ‘actioncardregarding’ and makes a lookup to your entity. So when you’re on the entity you specified in the ‘Set Regarding’ field, it makes a relationship link so you can see how many action cards have been linked to this particular entity and see this action card ON the entity. The relationship insights control needs to be part of the form for it to become visible.

4. Go ahead and test your flow, ensuring you have a model-driven app available. It is great to see the card both in a Dashboard and also within a Form (providing you set the regardingID and the form has the control on it). Click on the action (open) to open the entity or URL you specified, ensuring this has worked.

Any questions or issues, please leave them in the comments and i’ll do my best to help!