Omitted instances due to ID collisions
During an application connection fetch, you may get a warning such as "Omitted 2 instances of ticket_field due to Salto ID collisions.". This message indicates that some instances were not fetched due to Tulip ID or name collisions.
Tulip IDs are individually generated for each security application element type, according to its own adapter logic. For example, Okta User Fields' Tulip IDs are generated according to their unique Okta "field key". To view elements' Tulip IDs, click "Copy Element ID" when viewing a Tulip element.
The "omitted instances" message indicates multiple security application elements have the same calculated Tulip ID, and therefore were not fetched, as Tulip could not generate a unique identifier for each one.
The message will include:
The calculated colliding IDs
For each ID, the message may also indicate the exact instances that were omitted and their application-side URL
When this error occurs, the colliding elements will not be fetched. You will not be able to deploy them or document related changes, and they will not appear in any searches or as dependencies of other objects.
Possible Solutions
Remove or edit colliding instances in the Security Application
The best solution in these cases is to resolve the collision on the security application side: go to the colliding objects, and change their name (or any other field that participates in the ID calculation for that type).
After changing this on the security application side, re-fetch the application connection and observe that new instances were fetched and the previous error message does not appear again.
Excluding colliding items
If the colliding instances are simply not needed in Tulip, you can exclude them in your NACL configuration file, in order to stop getting these errors.
After excluding them in the configuration file, re-fetch the application connection to dismiss the original warnings.
Changing the ID Key criteria
If fixing this problem on the security application side isn't possible, but there is a different set of instance fields that is unique, sometimes you can change the key calculation settings in the application connection configuration. After changing these settings, re-fetch the application connection to get the new instances. Note that previous instances of the same type that were already successfully fetched (as they did not collide with each other) will have the previously calculated ID.
In order to change this key, you'll need to change your application connection NACL configuration, by using the fetch->elemID configuration, as detailed for example in the Okta documentation page
You can always contact Tulip Support with the "Help" button, or at support@tulipsecurity.com, to get assistance with setting this up.
Make sure you change this setting in all the relevant application connection configuration files, so that deployments between them will work reliably. After making these changes in the configuration file, re-fetch the application connection.