Applies to: Any PACS integration using custom field / User Defined Field (UDF) mapping in Data Manager
Symptom: A custom field or UDF that was previously syncing correctly silently stops saving or populating on the PACS side after being added or edited.
Root Cause #
Custom field/UDF mappings are matched by exact field name against the corresponding column or field on your PACS. This match is both case-sensitive and typo-sensitive. A field name typed as EmplyeeNumber instead of EmployeeNumber, for example, will fail silently in some PACS integrations rather than throwing an obvious error — the sync completes, but that one field never populates.
A confirmed error you may see in the Data Manager log when this happens (AMAG example):
Failed to set Custom field for user: 0. EmplyeeNumber field may not exist...
Not every PACS surfaces this as a visible error — some simply drop the field silently.
Fix #
- Open Data Manager → Settings → Custom Field / UDF Mapping.
- For each mapped field that isn’t saving, compare the exact spelling and casing against the corresponding field name on your PACS (check your PACS’s own field/column list directly rather than relying on memory).
- Correct any mismatch.
- Save and re-run a sync for a single test user to confirm the field now populates.
If This Doesn’t Fix It #
If spelling and casing are confirmed correct and the field still doesn’t save:
- Confirm the field exists and is writable on the PACS side (some fields are read-only or restricted by PACS-side permissions).
- Check the full sync log for any other error text near the field-mapping section.
- Contact the Telaeris Helpdesk with the exact field name, your PACS vendor, and the sync log excerpt.
