Troubleshooting: Related Module Field Displaying Internal ID Instead of Display Name in Reports (CRM)
This guide explains why a related module field in a report may show a raw internal database ID instead of readable text, and how to permanently resolve it by correcting the field's module configuration.
Symptom / Error
A related module field in a report — such as "Related To – Referral Source" — displays a numeric internal ID (e.g., 00042) instead of the expected readable name (e.g., UnityPoint or St. Anthony Regional Hospital).
This issue occurs in the report view and is caused by a misconfiguration in the record layout, not in the report itself.
Cause
This happens when a custom related module field in the record layout is configured to point to the wrong module.
A common example: in the Event record layout, both the "Related To – Referral Source" field and the "Referral Contact" field are both configured to link to the Referral Contacts module. Because both fields point to the same module, the system cannot correctly resolve the organizational display name for the Referral Source field and falls back to showing the raw internal database ID.
Each field must point to its own distinct module:
Referral Contact field → should link to the Referral Contacts module
Related To – Referral Source field → should link to the Referral Sources module
Solution
Because the field was created with the wrong module mapping, it cannot simply be edited — it must be deleted and recreated with the correct configuration.
Navigate to Settings → CRM Settings → Module Management → Module Layout & Fields and open the layout for the affected module (e.g., Events).
Identify the misconfigured related module field (e.g., "Related To – Referral Source") that is incorrectly pointing to Referral Contacts.
Delete the misconfigured field from the layout.
Create a new custom related module field in the same location, and this time configure it to link to the correct module — in this case, Referral Sources.
Save the layout.
Return to the report and confirm the field now displays readable names instead of internal IDs.
Verification / Expected Result
After recreating the field with the correct module mapping, the related module field in the report should display the readable display name (e.g., UnityPoint, St. Anthony Regional Hospital) rather than a numeric internal ID.
If the field still displays an ID after recreation, verify that the new field is correctly added to the report column configuration and that it is mapped to the Referral Sources module — not Referral Contacts.
Escalation
Contact Dazos Support if:
You are unsure which field in the layout is misconfigured
Deleting and recreating the field does not resolve the ID display issue
You need assistance identifying all affected reports or layout fields across your instance
When submitting a support ticket, please include:
The name of the field displaying the internal ID
The module where the layout is configured (e.g., Events)
A screenshot of the report showing the numeric IDs
Confirmation that both fields were previously pointing to the same module
Tips & Notes
⚠️ Warning: This issue is caused by layout configuration, not a bug in the report itself. Editing the report columns alone will not fix the problem — the field must be deleted and recreated at the layout level.
💡 Tip: If a related module field in any report is showing a numeric ID, always check whether two or more related fields in the same record layout are pointing to the same module. Duplicate module mappings are the most common cause.
✅ Best Practice: When creating multiple related module fields in a layout, verify each field is configured to its own unique target module before saving.