What is the difference between the Include in Push and Send to CRM fields in Veeva Align?
The Send to CRM field is located on all standard Align assignment related objects whose CRM counterparts are pushed to CRM:
- Roster Member Territory -> UserTerritory2Association
- Account Territory -> ObjectTerritory2Association
- Territory Product -> My Setup Products
- Territory -> Territory2
The purpose of this field is to decide whether or not push a certain record to CRM. The value of this field may be adjusted by the customer as a daily task.
The Include in Push field is located on two objects: Roster Member and MC Cycle. This is a special field and its value should not be controlled by the customer as a daily routine. Align handles its field value automatically.
The Include in Push field is deprecated on the Roster Member object.
Once an MC Cycle record or a related record gets created, the value of the Include in Push field is set to true automatically for each MC Cycle related objects including the child objects. Once the MC Cycle, MCCPs are in the published Lifecycle State, pushed to CRM, the value of the field is automatically set to no. This is to prevent the MC Cycle and its data from being pushed again which could potentially overwrite the CRM counterparts of the data (For example, Goals). Once the MC Cycle or the related data is modified in Align, the value of the Include in Push field is set to yes once more. The change will be pushed out into CRM, in the event the MC Cycle and MCCPs are still in the Published Lifecycle State.
Align Help Documentation:
- How to Push a Published MC Cycle and its Related Data Multiple Times into Veeva CRM from Veeva Align?