What’s enforced
- A tag number cannot appear more than once within the same LUnit.
- The same tag number can exist in multiple LUnits, just not twice in one LUnit.
In Chateau
If you try to save a duplicate tag within a LUnit, Chateau shows a notice that it’s a duplicate and blocks the save.
In Chateau Mobile
Duplicate prevention works only if the original tag is loaded on the device. If the original isn’t on the device, Chateau Mobile can’t detect the duplicate at entry time.
A tag is considered “loaded” in Mobile if:
- It’s part of a tour assigned to the technician, or
- Non-Tour Tags is enabled (see Miscellaneous Settings for details).
Deactivated components and tag reuse
Even if a component is Deactivated, you still can’t reuse its tag number.
To free up the tag:
- Edit the Deactivated component’s tag (e.g., change 123 to 123-Deactivated).
- Once the original tag changes, you can reuse the number.
How Chateau helps catch duplicates that slip through Chateau Mobile
- Duplicate Tag Audit (Porches): If enabled, you’ll be notified the next morning about any duplicates created in Chateau Mobile so you can resolve them.
- MOC Porch & New Component Porch validation: When approving suggested new components or MOC edits (individually or in batch), Chateau checks for duplicate tags. Duplicates are blocked, identified in the prompt, and left on the porch until fixed; all other valid items can still be approved.
- ‘-duplicate’ suffix for Chateau Mobile Approver entries: If an Approver adds a duplicate tag in Chateau Mobile and it’s recognized as a duplicate during processing, Chateau appends -duplicate to the tag. This makes the issue obvious in tag lists and the item will also appear on the Duplicate Tag Audit.
Tip: To resolve a flagged duplicate, edit one of the conflicting tags (for example, correct the number or add a suffix), then reprocess/approve as needed.