The Mappings sections are where all configurations related to syncing information between the two integrated programs can be found. This includes defining how data flows, setting up filters, and ensuring values align correctly.
The Filters page, located under the Mappings dropdown, is specifically used for event-based filtering and pre-filter functionality. Events are triggered via the Connected Systems icon in OnePlan or by entering a plan-level ID when running a strategy in OneConnect.
Key Considerations:
- When filtering on a field, that field must first be mapped in the Field Mappings section.
- Filters are grouped based on data flow direction:
- For data moving from OnePlan to Azure DevOps, use the OnePlan -> Azure DevOps section. The event filters will apply to OnePlanPublish.
- Filters in the opposite direction or on the Scheduled Strategy will not apply unless the integration strategy explicitly supports it.
This section displays the tables mapped between the two programs. These mappings are automatically configured in the backend and cannot be modified.
Field Mapping defines which data is transferred between the two programs and whether the flow is one-way or bi-directional. Mappings are categorized by tables such as Resources, Plans, or Backlogs.
Key Points:
- Each table has its own field mapping section.
- Each column represents a program, with dropdowns displaying available field names for mapping.
- A single field from one program cannot be mapped to multiple fields from the other program in the same table.
- Data types and option values must match between both programs to ensure successful transfer. (e.g., date field to date field, number field to number field)
- Use the arrows between fields to set the data flow direction.
- Local plan fields in OnePlan cannot be mapped to another system as they are specific to individual plans.
- In some integrations, fields set to flow only to OnePlan may have their editability controlled within the Work Plan. Check your integration settings to determine if this applies.
The Items section displays the connections between plans in both programs. Depending on the integration, you may have the ability to:
- Manually connect items between the two programs.
- Delete a mapping to break an existing connection.
Some integrations display either the GUID ID of the plan or the user-friendly front-end name. However, for Backlog item mappings, only GUID IDs are currently shown.
Different programs may use different values for similar fields (e.g., "Not Started" vs. "New"). Value mapping ensures smooth data transfer by aligning these values - this process functions as data transformation between systems.
Note
- Always set up value mappings in both directions to prevent unexpected errors.
- Values being edited or modified must first be mapped in the Field Mappings section.
How to Implement Value Mappings
- Each column represents a program.
- Expand the relevant table and click the blue + button to add a mapping.
- In the Field dropdown, select the field where the data transformation should occur (typically a choice field).
- In Source Value(s), enter the original value(s) from the program that need to be changed (e.g., "Not Started"). These values are case-sensitive and multiple values can be entered, but each value must be placed on a separate line.
- In Destination Value, enter the corresponding value that should appear in the second program. This must be a valid option and case-sensitive. Only a single value can be entered.