Auto-assign items based on a primary service rather than service category.

ChangePilot categorises all Message Centre items into one of 15 service categories. (For more information on ChangePilot service categories, see this article.) It might be the case that two or more Microsoft products and services within a service category are managed by two different people, or teams, in an organisation. In this instance, it might be necessary to assign items from one service category to two or more different people or teams.

For example, ChangePilot groups together SharePoint and OneDrive items into the 'SharePoint and OneDrive' service category. More often than not, one person or team in an organisation would be responsible for all these items. However, this is not always the case. Whilst not our default approach, it is possible to build a custom flow to assign Message Centre items based on the primary service (e.g SharePoint or OneDrive) rather than the service category. See here for the individual products and services within ChangePilot service categories.

If you are 'splitting' a service category, you are required to create one flow for each primary service re-assignment automation.

All custom flows and assets in your ChangePilot environment should be built and stored in a 'Configuration' solution in the unmanaged layer. You should have created this as part of the original ChangePilot deployment; however, some early versions of the ChangePilot deployment guide did not include this step.

Before you start: If you do not have a solution called 'Customisation' in the unmanaged layer of the ChangePilot environment, please follow the steps in this article.

Creating a flow to auto-assign by primary service 

Finding user ID/s

Before we start creating the flow, we need to find the User ID of the individual who will be auto-assigned the item:

1. Copy the URL below into a new browser tab/window, replacing the email address with the email address of the user you'd like to receive the re-assigned items, and the environment URL with the URL of your ChangePilot environment:
   
   https://environmentURL/api/data/v9.2/systemusers?$filter=internalemailaddress%20eq%20%27emailaddress%27&$select=systemuserid,fullname
2. The returned text string will end in an alpha-numeric value for the User ID. E.g:
   
   "systemuserid":"155063a4-2c5b-f011-bec2-6045bdf24615"
3. Make a note of the ID/s you would like to use in your flow/s.

Finding service ID/s

You then need to find the numeric ID for the primary service by which you want to auto-assign.

1. Navigate to make.powerapps.com and ensure you are in the environment in which you ChangePilot solution is located.
2. In the left-hand pane, select 'Solutions', and in your managed layer, choose the ChangePilot solution.
3. In the left-hand 'Objects' pane, select 'Choices' and open 'Services Choices'.
4. In the pane that opens, you will find the IDs for all service options. Make a note 

Creating the flow

1. Navigate to make.powerapps.com and ensure you are in the environment in which you ChangePilot solution is located.
2. In the left-hand pane, select 'Solutions', and in your unmanaged layer, choose the 'Configuration' solution.
3. Click '+ New' in the top ribbon > Automation > Cloud flow > Automated
   1. Provide a flow name
   2. Search and choose 'When a row is added, modified or deleted' Dataverse trigger.
   3. Click 'Create'.

Configure the flow

1. Trigger
   1. Change Type - Added
   2. Table Name - Message Center Items
   3. Scope - Organisation
   4. Filter Rows - cp_primaryservice eq serviceID
      1. Add the service ID e.g cp_primaryservice eq 121570023
2. Add 'Delay' action
   1. Set to 5 minutes
3. Add 'Update a row' (Dataverse) action
   1. Table Name - Message Center Items
   2. Row ID - Use dynamic content from trigger
      1. Message Center Item
   3. Owners - /systemusers(userID)
      1. Update GUID with user's ID e.g /systemusers(155063a4-2c5b-f011-bec2-6045bdf24615)
4. Click 'Save' to finish.