Understanding Automatic Promotion
Automatic promotion is a configuration option that enables entities to be automatically promoted when they are created or updated in Infor CloudSuite CRM.
For the automatic promotion logic to process new records successfully there must be:
- One Back Office enabled for outbound support of the Infor CloudSuite CRM Entity.
- One Accounting Entity defined for the Back Office for the Infor CloudSuite CRM Entity.
Any Infor CloudSuite CRM Entity can be configured for automatic promotion by modifying the BOD Mapping trigger condition settings. However, in most cases, bi-directional transactions such as Quote or Sales Order should not be set to automatic because multiple dependent records may be updated or created as part of a single transaction.
The following table shows typical BOD Pack settings for bi-directional entities:
| BOD | Outbound on Create | Outbound on Update | Outbound on Delete | Notes |
|---|---|---|---|---|
| ContactMaster | Automatic | Automatic | Automatic | Is dependent upon the corresponding Account being promoted. |
| CustomerPartyMaster | User triggered | Automatic | Disabled | Requires manual selection of the ‘Promote’ tasklet. |
| ShipToPartyMaster | Automatic | Automatic | Disabled | Is dependent upon the corresponding Account being promoted. |
| BillToPartyMaster | Automatic | Automatic | Disabled | Is dependent upon the corresponding Account being promoted. |
| PayFromPartyMaster | Automatic | Automatic | Disabled | Is dependent upon the corresponding Account being promoted. |
| Quote | User Triggered | User Triggered | Disabled | May be disabled in some BOD Packs. |
| SalesOrder | User Triggered | User Triggered | Disabled | May be disabled in some BOD Packs. |
What is a dependent entity?
A dependent entity has a specified parent entity The automatic promotion of Contacts, ErpBillTo, ErpShipTo or ErpPayFrom records are dependent upon the successful promotion of their related Account.