Foreign Key Administration
Foreign key fields shared across Group Members and/or Views must validate from the same table and field to ensure that queries retrieve correct data. You can use the Foreign Key Administrator to automatically configure all shared foreign keys in your system.
If shared foreign key fields are not configured correctly, you receive validation warnings when you edit a foreign key field in a Blueprint or when you run the Foreign Key Configuration Health Check rule.
An example validation warning is:
Good to Know
- You can use the Foreign Key Configuration Health Check rule to return a list of all shared foreign key fields that are not configured correctly. See About Performance Health Check.
- You can manually configure shared foreign keys in a Blueprint or mApp Solution. See Configuring Shared Foreign Key Fields.
- Standard foreign key rules also apply: shared foreign key fields must be validated from a table and validation must be enforced.
- Constraints for shared foreign key fields can differ between Group Members and Views
To automatically configure share foreign key fields:
- Create a Blueprint.
- Open the Foreign Key Administration dialog (Tools > Foreign Key Administration).
- Select these options as they apply:
Option Description Enforce table validation for all shared foreign key field definitions Select this check box to automatically configure table validation for all shared foreign key fields in your system. After you publish your Blueprint, the Validate from table check box is selected on the Validation/Auto-populate Page for all shared foreign keys fields in your system. Replicate table validation across shared foreign key field definitions Select this check box to replicate the validation table selection for all foreign key fields that share Views and Groups in the same Business Object. The Foreign Key Administrator attempts to match shared foreign key fields to validation tables based on these rules:
- If at least one single table match is found for a set of shared foreign key fields, the table is applied to those that do not have a validation table set. For example, if one shared foreign key field in a Group Member has validation set for Table A but a validation table is not specified for the shared foreign key fields in other Group Members, Table A is set as the validation for all Group Members.
- If two different validation tables are detected for shared foreign key fields in the same Group or View, no change is made.
- If no validation tables are set for any shared foreign key fields, no change is made.
I have read the following statement... You are required to acknowledge that you understand the implications of changing table validation on all shared foreign key fields.
- Select OK.
- Publish the Blueprint.
Verify changes before publishing the Blueprint to a production environment.