When working with third-party integrations, NX gives you the option to enter a Numeric ID for a record (such as a menu item, tender, or category). This can be useful if your outside system requires a specific identifier. However, it’s important to understand how NX treats these IDs.
What the Numeric ID Does
- The Numeric ID field is for third-party use only.
- You can enter or edit the value when creating or updating a record in NX.
- This value will be available to connected systems that need it, such as accounting tools, reporting services, or external databases.
What the Numeric ID Does Not Do
- NX does not use the Numeric ID internally for record management.
- NX relies on its own system-generated identifiers to keep track of records.
- NX does not enforce uniqueness in this field. That means:
- You can enter the same Numeric ID on multiple records.
- NX will not prevent duplicates.
- NX does not validate whether the ID matches any specific external requirements.
Why This Matters
Because NX does not enforce uniqueness, it’s up to you to make sure that the Numeric IDs you assign meet the needs of your third-party system. If two records share the same Numeric ID:
- NX will still allow them to exist side by side.
- Your third-party integration may treat them as the same item, which could cause confusion in reporting or syncing.
Best Practices
- Check your integration requirements: Make sure you know whether your third-party system needs unique IDs.
- Establish internal rules: Decide how your team will assign IDs to avoid duplication.
- Audit regularly: Periodically review your records to confirm that IDs are consistent and aligned with your external systems.
Key Takeaway
The Numeric ID field in NX is purely for third-party reference.
NX will not enforce uniqueness, so it’s up to your business to manage these values carefully if your integrations rely on them.
✅ With this knowledge, you can confidently set up third-party integrations while understanding how NX handles Numeric IDs behind the scenes.