Data Flow Directions
Standard Fields: Bidirectional
Standard fields in Alleva support bidirectional data flow, meaning data can move in both directions:
From Alleva EMR → Dazos CRM
From Dazos CRM → Alleva EMR
Custom Fields: One-Way Only
Custom fields in Alleva have a one-way data flow limitation:
Supported: Data can be pulled FROM Alleva INTO Dazos CRM
Not Supported: Data cannot be pushed from Dazos CRM to Alleva custom fields
When This Matters
This limitation becomes important when you want to:
Transfer notes from Intake Opportunity accounts in Dazos to custom fields in Alleva (like Communication Log)
Push CRM data to any custom field created in Alleva
Synchronize information that exists in non-standard Alleva fields
⚠️ Important: If the Communication Log in Alleva is configured as a custom field, you cannot transfer notes from Dazos CRM to that field, regardless of mapping configuration.
How to Identify Field Types
To determine if a field supports bidirectional data flow:
Check if the field is part of Alleva's standard field set
Review the Alleva API documentation to confirm field availability
Test the mapping in a controlled environment if uncertain
Alternative Solutions
When you cannot push data to custom fields in Alleva, consider:
Using standard Alleva fields that support bidirectional sync
Maintaining notes in Dazos CRM while pulling other data from Alleva
Working with Alleva administrators to map critical information to standard fields