Gateway Sharing - Adding a Prefix to shared data to avoid conflict or for custom names
Related to Copied
In the event of a conflict between a shared probe and configured probe the configured probe will always have priority and the shared probe will not be imported.
An optional prefix can be applied to the names of all imported probes and managed entities to help resolve conflicts.
To do this: Go to the Advanced settings of your Import Data. There, you’ll find an option to enable a prefix. Adding a unique prefix helps prevent conflicts and ensures your imported data remains distinct.
Problem Copied
In the event of a conflict between a shared probe and a probe configured in the setup file of the importing Gateway, the shared probe will not be imported. There can also be a situation where you wanted to have a unique identifier to the name of your shared data.
e.g.:
I have a netprobe running as a configured netprobe on my gateway:
If I use Gateway Sharing on my gateway to import a connection (another netprobe and it has the same managed entity name as TradesFRA for example ) it will not appear on my gateway as there is a name conflict.
The Gateway-importedData plugin will flag this up
There will also be an error in the Gateway Setup Editor
Possible solution(s) Copied
To do this, add a prefix to your imported data.
In the Advanced tab of your import data:
On the Prefix Paramater, enter a unique string to use as a prefix. For example, you could use “Test-”. This will help you easily identify and organize your imported entries.
