1. To-Increase Dynamics 365 for Finance & Operations
  2. RapidValue
  3. Activities

Set up Azure DevOps mapping
RapidValue task

Before you can use the Azure DevOps integration, you must set up the DevOps mapping. This includes:

  • Which RapidValue records map to which DevOps work item types.
  • If you use work packages, to which DevOps work item types the work package groups and work packages are mapped.
  • Which fields of these RapidValue records map to which fields of the DevOps work item.
  • The synchronization direction of the mapping, which defines whether RapidValue (Out) or DevOps (In) owns the data.
  • In case of an enum type field, which RapidValue field value maps to which DevOps work item field value.


Standard procedure

1. Click Business process management.
2. In the Links section, click DevOps mapping.
3. In the list, click the link of the desired mapping.
4. Click the Mapping tab.
5. Sub-task: Set up entity mapping.
  5.1 Set up which RapidValue records map to which work item types.
  In the Entity mapping section, click Add.
 

Note: You can also copy an existing entity mapping to create a new entity mapping. To do so, select the entity mapping that you want to copy, and in the Entity mapping section, click Copy, fill in the fields as desired, and click OK.
  5.2 In the RapidValue table name field, select an option.
  5.3 You can define a condition to only synchronize records with a specific field value. To do so, select a field in the RapidValue field name field and a value in the RapidValue value field.
  In the RapidValue field name field, enter or select a value.
  5.4 In the RapidValue value field, enter or select a value.
  5.5 You can map a RapidValue entity to any DevOps work item type.
  In the Work item type field, enter or select a value.
  5.6 If you want to use work packages to synchronize with DevOps, you must indicate this in the mapping.
To do so, for the business process mapping, select the Parent work package check box. As a result, on synchronize, in DevOps:
- The business process work item gets the work package work item as the parent.
- The work package work item gets the work package group work item as the parent.
This is only applied if on the business process the work package group and work package are assigned that are needed to create the hierarchy in DevOps.
  Select the Parent work package check box.
  5.7 You can apply a task template on creation of a requirement in Azure DevOps.
A task template has a predefined set of tasks to be created for a requirement in DevOps. In DevOps, these tasks are added as work item with the requirement as parent work item.
  In the Task template field, enter or select a value.
 

Note: Only apply a task template to a mapping record if the RapidValue table name is 'Requirement'.
6. Sub-task: Set default parent for mapped entity.
  6.1 In the Entity mapping section, click Set default parent.
  6.2 For the RapidValue entities which do not have a parent in the business process hierarchy, define a default parent work item. Otherwise no DevOps work item is available to which the created work item can be linked.
Use this, for example, to synchronize requirements only.
  In the Work item ID field, type a value.
 

Note: Copy the work item ID in DevOps and paste it in this field.
  6.3 Before you can proceed, check the entered work item ID. If it is valid, the name and description are filled from the work item.
  Click Check.
  6.4 Click OK.
 

Note: As a result, the Default parent for the selected entity mapping record is filled.
7. Sub-task: Define additional conditions.
  7.1 You can add additional conditions on top of the condition as defined in the RapidValue field name field and RapidValue value field in the Entities pane.
Use these conditions to only synchronize records with specific field values. To do so, in the Conditions pane, select a field in the RapidValue field name field and a value in the RapidValue value field.
  In the Entity mapping section, in the Conditions pane, click Add.
  7.2 In the RapidValue field name field, enter or select a value.
  7.3 In the RapidValue value field, enter or select a value.
8. Sub-task: Set up entity field mapping.
  8.1 Set up which fields of the RapidValue record map to which fields of the DevOps work item. Also define the synchronization direction.
  In the Entity details section, click Add.
 

Note: You can also copy an existing entity field mapping to create a new entity field mapping. To do so, select the entity field mapping that you want to copy, and in the Entity details section, click Copy, fill in the fields as desired, and click OK.
  8.2 In the Name field, type a value.
  8.3 The direction of the field mapping defines whether RapidValue (Out) or DevOps (In) owns the data.
  In the Sync direction field, select an option.
  8.4 In the RV field name field, enter or select a value.
 

Note: Fewer fields are allowed for the synchronization direction 'In' than for the direction 'Out'.
  8.5 In the 'DevOps field' field, enter or select a value.
9. Sub-task: Set up entity field value mapping.
  9.1 If you set up a field mapping for an enum type field, define which RapidValue field value maps to which DevOps work item field value.
Example: You can use the field value mapping to link requirement statuses to work item statuses.
  In the Entity details section, in the Values pane, click Add.
  9.2 In the RapidValue value field, enter or select a value.
 

Note: Do not define a field mapping for the RapidValue field that you defined in the entity mapping.
  9.3 In the DevOps value field, enter or select a value.
10. Close the page.
11. Close the page.
Related to Notes

Set up Azure DevOps integration

 		 

Provide feedback