Preventing duplicate navigation jumps
From version L120 onwards, navigation jumps have a Code field that acts as the technical key for cross-environment transfers (Configuration transfer and Configuration labeling).
When importing a configuration label, the system uses this Code to decide whether a navigation jump in the target environment must be updated or created:
• If a navigation jump with the same code exists in the target environment, it is updated.
• If no navigation jump with that code exists in the target environment, a new navigation jump is created.
If two environments contain navigation jumps that are functionally the same (same layout, same name, same configuration) but have different codes, importing a configuration label will create an additional jump instead of updating the existing one. This may result in duplicate navigation jumps after import.
How to prevent?
Before exporting and importing a configuration label that includes navigation jumps:
1. Verify Codes in source and target environments
◦ For each navigation jump that should be considered the same across environments, ensure the Code value is identical in both source and target.
◦ If the same jump exists in multiple environments with different codes:
- Either manually align the codes, or
- Delete the navigation jumps in the target and re-import them from the source so that the codes match.
2. Use a single master environment for jump creation
◦ Prefer to create and maintain navigation jumps in one environment (for example, TEST) and distribute them to other environments (ACC/PROD) using Configuration labels or Configuration transfer.
◦ Avoid recreating the same jump manually in multiple environments with different codes.
By ensuring that navigation jump Codes are aligned between source and target environments before running a Configuration label or Configuration transfer, you prevent unintended duplicate navigation jumps during import.