[Feature] share or sync UDT data type between 2 realtime tag provider

Some times we don’t want to split an application with multiple realtime tag’s provider (for each site or zone) because we can’t share or sync UDT definition between 2 realtime tag provider.
I would like to be able to have some global UDT definition for mutliple local real time tags provider of one gateway.

3 Likes

Hi,

We’ve felt for a while that some sort of data model/type model that could be shared between providers would be useful. This won’t be available for 8.0, but it’s definitely something we’ve been thinking about.

Perhaps following from changes to the project system allowing for project inheritance, maybe something similar with inheritance of tag providers could be a way to pull this off.

3 Likes

The What’s New page implies that v8.0 will allow inheritance of data types. This post implies that is not the case. Could someone elaborate?

image

@Walt I would trust the developer who architected the new tag system over some marketing copy :slight_smile: But, in answer to your question - the new project inheritance system does not (yet) have any effect on tags/tag inheritance.

1 Like

Hey @Colby.Clegg, @PGriffith – is it possible to publish/synchronize datatypes to tag providers using the EAM?

Also wondering the same thing, if EAM can handle, or if its on the list with any expected release date? Multiple tag providers with the same UDT means either exporting and importing or trying to make the same edit multiple times to keep things in sync

Hello All,

Just checking in to see if there are any release dates for this functionality being rolled into the inheritance functionality current available for projects?

Thanks,

Frank

For a release date to be scheduled, IA would have to actually commit to this. There’s no indication in this topic to suggest that a workable way to do it exists yet, much less planned.

Tags aren’t in projects, so there’s no inheritance hierarchy at all.

1 Like

In addition to that, we don’t ‘waterfall’ features into specific versions that are targeted to specific dates.
We build features into the next minor version (which is released ~monthly, on our release train schedule), or roll specific significant features into the next major version (which is released ~whenever it’s ready).

1 Like

This feature would be much appreciated.

2 Likes

Tag provider inheritance sounds like a perfect solution. We’d have a “Standard” provider on central/master gateway with our standard UDT definitions and all other providers would inherit from this one so they always have current standard UDT definitions. EAM could sync tags from standard provider on central/master gateway to all agent gateways’ “Standard” providers where all local providers on those gateways would inherit from it.

Presently, it looks like EAM send tags is the best option to sync UDTs between gateways. Unfortunately this requires a task per provider per gateway if your providers are uniquely named to allow running the same projects on multiple gateways. If EAM task “Send Tags” allowed specifying all providers (instead of a specific named provider) on target gateway(s), this would work almost as well as tag provider inheritance. One task on master gateway could sync standard UDTs to all providers on all agent gateways.

A workaround for Send Tags requirement to specify a provider would be to copy UDT configs from a Standard provider on each gateway updated via EAM Send Tags to all other providers on the gateway via script using system.tag.configure. Unfortunately this hits a snag:

Is there currently any option better than a send tags task per provider per gateway to sync UDTs between gateways?