CRM Troubleshooting
Common issues encountered while configuring and operating a CRM module, along with their underlying cause and the recommended resolution. Ordered by the same sequence as the documentation, with each row's related topic marked on the left.
| Topic | Symptom | Likely Cause | Resolution |
|---|---|---|---|
| External Modules | An External module keeps showing "Primary Key Not Configured" after the endpoints are mapped. | No field on the Fields tab has been marked as the primary key. | On the Fields tab, mark the field holding the external system's unique identifier as primary. |
| How to Configure a CRM Module | A module's Source Type can't be changed from Internal to External, or the reverse. | Source Type is locked permanently the moment a module is first saved. | Recreate the module with the correct Source Type; the existing one cannot be converted in place. |
| How to Configure Fields | A new Relationship field appears to save but never shows up on the Fields tab. | Relationship Type was left unset; the save is silently rejected with no visible error. | Reopen the field, set Relationship Type explicitly, and save again. |
| How to Configure Fields | Unique Field can't be switched off on a Relationship field. | Relationship Type is set to One to One, which automatically enables and locks Unique Field to enforce the "exactly one" constraint at the data level. | If a non-unique link is actually needed, change Relationship Type to One to Many or Many to One instead. |
| How to Configure Fields | Related Module and Relationship Type appear greyed out when opening an existing Relationship field. | Both settings lock permanently once a Relationship field is first saved, including on built-in system fields. | Create a new Relationship field with the correct Related Module and Relationship Type instead of trying to edit the existing one. |
| How to Configure Fields | Unique and Required can't both be enabled on an existing field. | The module already contains records, and the field wasn't created with both settings from the start. | Choose one setting, or apply both only at field creation, before the module holds data. |
| How to Configure Layouts | A Form Layout's section groupings don't appear on the real create/edit form. | The live form does not automatically adopt a saved Form Layout's section structure. | Treat the builder's preview as a design reference, and confirm the actual behavior against the live form directly. |
| How to Configure Layouts | A Table, Thread, List, or Grid View block's Related Module dropdown comes back empty. | No other module yet has a Relationship field pointing back at the module being laid out. | Create that relationship on the other module first, or, for a Table block only, use Non-Related Module as a substitute. |
| How to Configure Layouts | Clicking a field in Available Fields on a Form Layout doesn't add it to a section. | Form Layout only accepts fields through drag-and-drop; a click alone has no effect. | Drag the field from Available Fields directly into the target section. |
| How to Configure Layouts | An Index Page Layout in Kanban mode has no board columns to configure. | Kanban mode requires a Group By Field, which must be an Enumeration field, and none exists on the module yet. | Add an Enumeration field to the module, then select it as the Group By Field. |
| How to Configure Dependencies | A Dropdown Dependency fills in the wrong field, or fills in the parent instead of the child. | The fields were checked in the wrong order in the Fields multi-select, reversing the chain direction. | Reopen the dependency and rebuild the field order so the controlling field is checked first. |
| How to Configure Dependencies | An entire saved dependency disappears after what was meant to be a small edit. | The top-level delete icon on a saved dependency removes it immediately, with no confirmation prompt. | Rebuild the dependency, and in future use the per-node delete inside edit mode to remove a single mapping. |
| How to Configure Dependencies | The Select Fields list under Dropdown Dependencies shows "No data." | Dropdown Dependencies only offers Enumeration-type fields, and the module has none configured. | Add at least two Enumeration fields to the module before setting up this dependency. |
| Records Management | Expected records are missing after a CSV import. | Ignore was selected under duplicate handling, skipping rows that matched existing records. | Re-run the import with Overwrite selected, if updating existing records was the intent. |
| Records Management | An exported CSV contains fewer records than the module actually holds. | An active list filter was still applied when Export was clicked, scoping the file to just that subset. | Click Clear Filters before exporting, to capture every record in the module. |
| Permissions | A role can manage module fields or layouts but users still can't be stopped from, or allowed to, work with actual records, or the reverse. | CRM Configuration permissions (schema access) and CRM Module permissions (record access) are independent of each other. | Review both permission categories on the role; granting one does not grant or restrict the other. |