You can now configure the P6 Connector to support multiple P6 instances. The default P6 Connector jobs are setup to support a single instance, but can be modified to support multiple instances.
Implementing a P6 integration with multiple P6 instances might have several challenges and it is necessary to be aware of the following issues for such type of implementation:
-
The primary issue with multiple P6 instances is that the internal ID's (ObjectId) of P6 records could clash. By default, P6 Connector imports store the P6 Object Id in the EcoSys External Key to maintain data mapping between EcoSys and P6.
The solution is to add a specific prefix to all External Key values that are imported from the P6 instance.
-
There could potentially also be clashing issues with the P6 Project ID's.
This can be addressed either by the client adopting consistent naming conventions for their P6 Projects, or configuring the P6 Connector to automatically add a prefix to all Project ID's.
-
Different P6 instances will likely have different enterprise data fields configured (Project Codes, Activity Codes, Cost Accounts, and so on). This would require setting up different sets of P6 Connector imports or exports depending on the enterprise data fields in use for each P6 instance.
If clients use the same fields across P6 instances, then a strategy must be adopted to avoid clashes in naming or P6 internal ID's.