Transaction Group in Inheritable Project

I have an inheritable project where I want to keep shared/global resources for a series of projects that all pertain to a common department. It makes sense to put the transaction groups in this inherited project to make it easy to maintain/locate.

When I add the groups to the inheritable project, the gateway webpage shows all of the child projects running the transactions groups but not in the parent project. The parent project shows that the project is disabled even though it isn’t.

I guess transaction groups in an inheritable project is a bad idea?

Yes. Unless you want all child projects to run their own copy.

1 Like

And the only way this can be meaningful is if each child project has its own default database and own default tag provider and the groups use no OPC items. Otherwise all of the child projects will send to the same database tables to/from the same tags.

1 Like