Overview
When managing form mappings in the myAvatar (Netsmart) integration, you have two options for stopping data from being sent: disabling the form or deleting the mappings. Understanding the difference between these two actions is important, because the mappings do more than power outbound pushes — they also control inbound data syncs into Dazos CRM.
This article explains how mappings are scoped, what inbound syncs are affected, and why disabling a form is generally the safer choice over deleting its mappings.
Key Concepts
Mappings are scoped per form: Each form in the myAvatar integration has its own set of mappings. Removing or changing mappings on one form (such as Financial Eligibility / PATIENT500) has no effect on any other form pushing data to myAvatar.
Mappings power both outbound and inbound syncs: The same mappings that send data to myAvatar also drive two inbound syncs back into Dazos CRM. Removing those mappings stops the inbound syncs as well.
Disabling a form vs. deleting its mappings: Both actions stop data from being sent, but they have very different implications for re-enablement.
How It Works
For the Financial Eligibility form (PATIENT500), the configured mappings control three data flows:
Outbound push: Financial eligibility data is sent from Dazos CRM to myAvatar.
Inbound sync — Guarantor list: The guarantor list is pulled from myAvatar into the Payer Code picklist in Dazos CRM.
Inbound sync — Financial eligibility pull: Financial eligibility data is pulled from myAvatar back into Dazos CRM.
If you delete the mappings, all three of these data flows stop. Re-enabling the integration at a later point would require remapping all fields from scratch.
If you disable the form, the same effect is achieved — nothing gets sent or received — but the mappings remain intact. Re-enabling is a single step and does not require any remapping.
Important Notes
Before disabling or deleting mappings, confirm the intended scope with your customer. Specifically, clarify whether they want the entire financial eligibility integration paused (both inbound and outbound), or only the outbound push to myAvatar. Because the inbound syncs depend on the same mappings, removing them affects more than just what is sent out.
⚠️ Recommendation: In most cases, disabling the form is the preferred approach rather than deleting mappings. It achieves the same immediate result while making it easy to re-enable the integration with a single action if needed — for example, after a billing issue is resolved. Deleting mappings should only be chosen when there is a confirmed, long-term intent to permanently remove the integration, as re-enabling it later will require all fields to be remapped from scratch.