Best Practices

Parents/Nodes

P2MAP requires the parent to set for each project. The parents are set using the "node" concept in P2MAP. In order to create projects, you must map the Node field.  

In OnePlan create a custom field that is choice type. Map that to the Node field in P2MAP. You can specify the parent using that.

If you don't map the field, you will receive this error message:

ERROR: Unable to create the project, a parent project must be specified through the tree node hierarchy. Please ensure the appropriate field is mapped and has a valid value.

Project ID

Every project in P2MAP must have a unique project ID. The field called Project ID must be mapped in order to specify this value.

You can create a custom field in OnePlan for this mapping or use the built in "Id" field. The built in Id field will provide you with the unique identifier of a plan in OnePlan.

If you don't map the field, you will receive this error message:

ERROR: Unable to create the project, a valid project code must be specified. Please ensure the appropriate field is mapped and has a valid value.

Filters

By default there are no filters configured for the OnePlanPublish strategy. This means that all plans in OnePlan will be in scope for the integration and they will be created and/or updated in P2MAP. 

It is recommended to add a filter to your strategy.

Financials

P2MAP uses time phased attributes to track costs for a project. Only 2 cost types are supported, “Budget” and “Actuals/Forecast” and the data is tracked for either years or months. (see a sample configuration below)

OnePlan supports cost types and cost attributes.

If a plan in OnePlan has a “Budget” cost type, then the values will be exported to P2MAP to the appropriate attributes' budget value.

If a plan in OnePlan has a “Actuals/Forecast” cost type, then the values will be exported to P2MAP to the appropriate attributes' Actuals/Forecast value.

Considering this sample below:

The integration will look to match external ID to the name of an attribute in P2MAP.

In the example above, there are 3 attributes. Attributes 1, 2 and 3 have budget lines. They all have their external Ids set to the same as their name. Using the setup above in OnePlan, Attribute 1, 2 and 3 would be populated from the cost category named "Budget" in P2MAP.

Syncing P2MAP Nodes with OnePlan

There is a special field called “Nodes” which can be used to sync over the tree node hierarchy list from P2MAP. This field is important and needs to be defined for a project before it can be created in P2MAP, because project creation requires a parent tree node.

After mapping this field in the LookupTables, the SynchLookups strategy can be triggered to populate the values in OnePlan.