Skip to main content

Understanding Custom Field Limitations in the SA/MH Coverage Block PDF Export (CRM)

The Full VOB PDF export is designed to pull only specific fields from the SA/MH Coverage block. If you have added a custom field — such as an "Admission Co-pay" column — to this block, it will save correctly in the CRM but will not appear in the exported

This is an intentional constraint in how the VOB summary document is generated, not a bug or configuration error.

When This Affects You

You may encounter this limitation if you are:

  • Trying to add a new column (e.g., "Admission Co-pay") to the SA/MH Coverage section of the Full VOB

  • Noticing that a custom field you added to the SA/MH Coverage block appears in the CRM layout but is missing from the exported PDF

  • Attempting to document co-pay or other custom benefit details within the SA/MH Coverage block for PDF reporting purposes

How the SA/MH Coverage Block PDF Export Works

The Full VOB PDF export for the SA/MH Coverage block is built to render only two specific fields:

  • Limitations

  • Details

Any custom fields added to the SA/MH Coverage block — regardless of how they are configured in the CRM layout — will not be included in the generated PDF. The data entered into those fields is saved in the CRM, but the PDF template does not support rendering them.

⚠️ Important: This is a design constraint of the VOB PDF export, not a bug. Requesting a custom field in this section of the PDF would require a fundamental change to the VOB export structure.

Workarounds

If you need custom information (such as co-pay details) to appear in the Full VOB PDF export, you have two options:

Option 1: Use the 'Details' or 'Limitations' Field

Log co-pay or other custom benefit information directly in the Details or Limitations field within the SA/MH Coverage block. Since these are the only fields pulled into the PDF, your information will be captured in the export.

Option 2: Move the Field to a Different Block

If you need the field to appear as its own column in the PDF, consider moving it to a block outside of the SA/MH Coverage section. Fields in other blocks may render correctly in the exported PDF depending on how those blocks are configured.

💡 Tip: Contact Dazos Support if you need help identifying which blocks support custom field rendering in the Full VOB PDF export, or if you need assistance moving a field to a different block.

Tips & Notes

  • Best Practice: Before adding custom fields to the SA/MH Coverage block, confirm whether you need that data to appear in PDF exports. If so, use the Details or Limitations field, or place the field in a supported block.

  • ⚠️ Note: Custom fields saved in the SA/MH Coverage block are not lost — the data remains accessible in the CRM record. Only the PDF export is affected.

Related Resources

  • Understanding Empty Financial Fields in VOB Responses Despite Active Coverage (CRM)

  • Understanding Instant VOB Field Mapping Limitations for CRM Reports (CRM)

  • Troubleshooting Hidden Fields Appearing in PAA PDF Exports

Did this answer your question?