Collection of Adobe I/O Runtime endpoint to perform CRUD operation, in bulk, in Microsoft Dynamics 365 CRM application. The serverless endpoint leverages Microsoft Dynamics 365 web-apis to interact with the application and perform requested operation.\nOperations like create/insert, update, delete are performed as batch of operations. The read operation immediate execution operation.
\nclientSecret. Instead of passing username and password, pass the Azure application clientSecret.entity: Microsoft dynamics entity like leads, contacts, accounts, tasks, emails, phonecalls etc. Find more entities and details visit Microsoft entities.
action: Use read for fetching/searching matching records.
response_attributes: Specify * to fetch all attributes with the entity or specify selected list of attributes as comma (,) separed string. Find more entities and details visit Microsoft entities.
data: Is an array of filter condition(s). Each array element works as OR condition. To find more details about OData filter queries, click here.
entity: Microsoft dynamics entity like leads, contacts, accounts, tasks, emails, phonecalls etc. Find more entities and details visit Microsoft entities.
action: Use insert for create / insert records.
response_attributes: Specify * to fetch all attributes with the entity or specify selected list of attributes as comma (,) separed string. Find more entities and details visit Microsoft entities.
data: Is an array of CRM entity attributes and corresponding values. Find more entities and details visit Microsoft entities
entity: Microsoft dynamics entity like leads, contacts, accounts, tasks, emails, phonecalls etc. Find more entities and details visit Microsoft entities.
action: Use update for create / insert records.
response_attributes: Specify * to fetch all attributes with the entity or specify selected list of attributes as comma (,) separed string. Find more entities and details visit Microsoft entities.
data: Is an array of CRM entity attributes and corresponding values. The key crm_id, uniquely identifies the record to be updated and it's a mandatory key. Find more entities and details visit Microsoft entities
entity: Microsoft dynamics entity like leads, contacts, accounts, tasks, emails, phonecalls etc. Find more entities and details visit Microsoft entities.
action: Use delete for create / insert records.
response_attributes: Specify na/NA/Not request, since post delete there is no specific attribute to return. The return value \"data\": [{\"crm_id\": \"8009df47-...\"},{\"crm_id\": \"8609df47-...\"}]
data: Is an array of crm_id, uniquely identifies the record to be removed and it's a mandatory key.
remap_data_key: Adobe Campaign Standard does not supports key attributes with some special character like regardingobjectid_lead@odata.bind; so, remap_data_key helps to remap the request payload to actual CRM entity attribute before performing any CRM operation.
params: The configuration part of the request i.e d365_config, entity, action, remap_data_key and response_attributes, which are specified under CUSTOMIZE PARAMTER in Adobe Campaign standard, are encapsulated within params key attribute in the payload.