1. Issue Overview
When a customer deletes and re-adds too many fields in a PAA module (especially across multiple PAA types), one of the following may occur:
The module becomes locked and no further fields can be added.
Users may receive “Access Denied” errors when attempting to open PAA records.
2. Root Cause
These issues are typically caused by excessive use of duplicate custom fields across multiple PAA types. Because each PAA module has a maximum field quota, creating separate copies of the same field (for example, “Employer”) in each PAA type consumes quota unnecessarily and increases risk of module lock-out.
3. Recommended Best Practice
To optimise form design and maintain system stability:
If you need a field (for example, Employer) that applies to multiple PAA types, create it once and then reuse that single field in all relevant PAA types.
Avoid creating separate “Employer” fields for each PAA type. Duplicating identical fields across types consumes quota much faster.
Leverage “Module Table Fields” (if available) for scenarios where you are repeating the same questions across PAA types. This helps reduce redundant fields and preserves field quota.
4. Training Tips for Customers
When training a customer on editing PAA forms:
Explain the field-quota concept and why duplication matters.
Show how to reuse a single custom field across multiple PAA types rather than recreating it.
Demonstrate how to use a Module Table Field when questions repeat across types.
Advise them to review existing fields before adding new ones — check if the needed field already exists and can be reused.
Encourage periodic cleanup: remove unused fields, archive obsolete PAA types, and check for redundancies.