Configuration changes and limitations affecting CONNECT integration

If you use the CONNECT integration feature, understand how Studio configuration changes and limitations affect published data in the CONNECT data services. Learn how to manage these impacts, if possible.

Important: Although there are ways to handle the impact of some Studio configuration changes, it's recommended to avoid them, especially if you have been curating data for a long time. Doing so may require reloading or resending the entire data to the CONNECT data services, or resetting your namespace.

Moving a reporting point without the parent asset to a different location in the project hierarchy

In CONNECT data services, events are linked directly to the asset under which the reporting point is parented in the Studio project hierarchy, rather than to the reporting point itself. This means that if you move a reporting point without the parent asset, all events that have already been published to CONNECT data services are still linked to the old asset, which could cause visualization widgets to stop working, as some rely on the event-to-asset link to retrieve data.

To fix the asset link issues:

• Run the history recovery tool to republish past events that are still linked to the old asset. This operation links the past events to the new asset. For detailed steps, see Recover on-premises historical data on the AVEVA Production Management Installation Guide.

Removing or updating UOM in a field

CONNECT data services platform only allows setting unit of measure (UOM) and changing it to the same unit type when data has already been published (upserted). Field data is curated for UOM only if its DisplayFormat property is set to "p" for percentage. After curation, the data is published to the CONNECT data services as decimal. When visualizing on the Events Visualization type widgets, it is displayed as a percentage.

If you have already published a UOM and then remove it or change it in Studio, CONNECT data services platform rejects the change. To resolve this issue, delete and recreate the field in Studio, or reset your namespace.

Changing data types

Changing a custom field's DataType property that's already been published is not allowed in CONNECT data services. For example, if you change an integer to string, this change is not permitted. To handle this, delete and recreate the field in Studio, or reset your namespace.

Deleting fields under a reporting point

If you delete a field under a reporting point, all historical data associated with the deleted field is no longer available. When you recreate the same field, it is assigned a different ID, so it does not retain its previous data association.

Curating calendar item fields is not supported

Calendar item fields are not curated. If you don't see calendar values in the CONNECT visualization, it’s because they are not curated and sent to the CONNECT data services as null.