A list of all entities held within CRM (filtered according to user security) are displayed in the Entities to Process drop down on the SmartConnect destination screens.
Entities that are selected in the entities to process drop down list are displayed in the mapping grid below the destination form as entity display name (entity technical name).
Entities selected in the Entities to process drop down and mapped using the node mapping screen are processed as follows:
Processing creates:
| 1. | If update blank data was not selected on the mapping screen, any fields that are blank are removed from the record to be processed. |
| 2. | SmartConnect will attempt to check CRM to see if the data to be created already exists. Fields that were grouped in the mapping screen will be used to determine existence of records. |
| 3. | If the record exists, and update if exists is not checked, an error is returned to the user. If update if exists is checked see processing updates. |
| 4. | The record is checked for state code and status code fields. If these fields exist in the record to be created they are saved for later processing and then removed from the record to be created. |
| 5. | The record is checked for owning user, owner id, owning business unit and owning team fields. If these fields exist, and they are not set to the current user accessing CRM they are set aside for later processing. |
| 6. | A CRM create request is passed to CRM with the record details. |
| 7. | If the any of the owner fields were set (see step 5) an assign request is created then processed, assigning the newly created record to the required user / team / business unit. |
| 8. | If the state or status code were set (see step 4) a set state request is created then processed, changing the state and status code of the newly created record. |
Processing updates:
| 1. | If update blank data was not selected on the mapping screen, any fields that are blank are removed from the record to be processed. |
| 2. | SmartConnect will attempt to check CRM to see if the data to be created already exists. Fields that were grouped in the mapping screen will be used to determine existence of records. |
| 3. | If a record or records are not found an error is returned to the user. |
| 4. | The record is checked for owning user, owner id, owning business unit and owning team fields. If these fields exist, and they are not set to the current user accessing CRM they are set aside for later processing. |
| 5. | The record is checked for the state code field. If the state code field exists, and the state code is different from the current record state code, and the state code is set to active, a set state request is created then processed to change the status of the record back to active. If the state code in the record to be updated is not active it is recorded and removed from the record to be updated. It will be processed after the update. |
| 6. | Fields in the record to be processed are copied across to the fields on the current record. An update request is then created and processed. |
| 7. | If owner fields were detected in step 4 an assign request is created and processed to assign the record to the defined user. |
| 8. | If the state code field was recorded and removed in step 5, a set state request is created and processed to assign the new status to the updated record. |
Processing deletes:
| 1. | If update blank data was not selected on the mapping screen, any fields that are blank are removed from the record to be processed. |
| 2. | SmartConnect will attempt to check CRM to see if the data to be created already exists. Fields that were grouped in the mapping screen will be used to determine existence of records. |
| 3. | If a record or records are not found no further processing occurs for the passed in record. |
| 4. | A delete request is created and processed for each record returned in step 3. |