How to setup Referential Integrity on Owned Foreign-Key Tables

Nextworld Platform
1

A customer has created a New Owned Table (nsXXTable), and created a Table Lookup to that table (nsXXTableReference) in the ReceivablesDetail table. They want to prevent deletion of records in the nsXXTable if it is used in a ReceivableDetails table record. I believe we do this in Nextworld Platform via a new Owned record in the Referential Integrity application. How is this record setup and activated? And what are the User Defined Field Mappings (do I need one for this use case)?

Add

2

Also, are these Referential Integrity records “Cloud Metadata” in that they are shared across all Customer Tenant Environments, or are they unique to each Environment?

3

Referential Integrity records are unique to each environment, and can be moved around by adding them to metadata manifests directly or indirectly moved on migration scripts by selecting the Referential Integrity checkbox for Table transfers.

To prevent deletion of records in nsXXTable, you should:

  • launch Referential Integrity and execute the Reload Data list action
  • locate the record where foreign table = nsXXTable and base table = nsXXTableReference and execute the Enable row action

This will update the Integrity Mode for that row to Enforced and thereafter, users will be prevented from deleting rows in nsXXTable if there are references to those rows in nsXXTableReference