Exporting a File from D365 Using Deque and Uploading It to Blob via Logic Apps

Exporting a File from D365 Using Deque and Uploading It to Blob via Logic Apps

Follow the below steps:

1. Create an export project in the Data Management(DMF).

2. Under Manage Recurring Data Jobs, create a new record and add the application ID.

3. Set the processing recurrence and enable the corresponding boolean.

4. Copy the value from the ID field.

5. Create an HTTP request, paste the URL provided below, and use the GET method.

     {{resource}}/api/connector/dequeue/{activity ID}?company=USMF

6. Instead of generating a token, assign the values in the Authentication tab.

7. Retrieve the Download Location from the previous step and assign it to a new HTTP trigger to get the file.

       body('Get_the_package_Download_URL')?['DownloadLocation']

8. Use the Upload to Blob action and provide the container name, blob name, and content.

Output:

1. The Get Package Download URL step will return the JSON response, from which we need to capture the DownloadLocation.

2. The Download Package step will return an octet-stream.

3. Since the response is a ZIP file, it is not possible to read the data directly.

4. The ZIP file will be stored in Blob Storage.

5. Below is the CSV file exported from D365.

D365:

• Once file is fetched from D365 status will change in manage messages.

Keep Daxing!!

Push Multiple Records in a Single Http Request Using Batch API in Logic Apps

 Pushing Multiple Records in a Single Request Using Batch API in Logic Apps:

        We can perform the multiple operations in single request by using Batch API. To know more Click Here

Please follow the below steps:

• I have added the HTTP request.
• I configured the following URL and headers.
  

  Content-Type: multipart/mixed; boundary=batch_CR

• I used the batch number as batch_CR and the change set number as changeset_EE.
  

• I am performing three operations:
• Creating a record in the vendgroup table.
• Updating a record in the custgroup table.
• Deleting a record in the vendgroup table
  

  --batch_CR
  Content-Type: multipart/mixed; boundary=changeset_EE
  
  --changeset_EE
  Content-Type: application/http
  Content-Transfer-Encoding: binary
  Content-ID: 1
  
  POST VendorGroups?cross-company=true HTTP/1.1
  Content-Type: application/json; type=entry
  
  {
      "dataAreaId": "USMF",
      "VendorGroupId": "Test04",
      "Description": "Test 4",
  }
  
  --changeset_EE
  Content-Type: application/http
  Content-Transfer-Encoding: binary
  Content-ID: 2
  
  PATCH CustomerGroups(dataAreaId='USMF',CustomerGroupId= 'TestC01')?Cross-company=true HTTP/1.1
  Content-Type: application/json; type=entry
  
  {
      "Description": "Test C1111"
  }
  --changeset_EE
  Content-Type: application/http
  Content-Transfer-Encoding: binary
  Content-ID: 3
  
  DELETE VendorGroups(dataAreaId='USMF',VendorGroupId= 'Test03')?Cross-company=true HTTP/1.1
  Content-Type: application/json; type=entry
  
  --changeset_EE--
  --batch_CR--

• I used OAuth authentication, providing the Client ID, Secret, and Tenant ID.

Output:

 

If the Batch API request Succeeds:

1. It returns a 201 status code for the create operation, along with the entire payload of the first request.
   
   
   
   
   
2. It returns a 204 status code for the update and delete operations, as no content is returned after an update and delete.

 

If the Batch API request Fails:

• The main status code is 200, but within the response body, it returns a 500 error.

• Below is the output of the Batch API request, with error message highlighted in a green box.

Fetching the Error Message:

• I added conditions to handle both success and failure cases.

• If the Batch API request fails, I retrieve the error message using the following expression.

• Fetch the error
  

  body('Batch_API')['$multipart'][0]['body']['$multipart'][0]['body']['$applicationHttp']['body']['error']

• Fetch the error status code
  

  body('Batch_API')['$multipart'][0]['body']['$multipart'][0]['body']['$applicationHttp']['statusCode']

 

• If the Batch API request succeeds, I extract the status code using the appropriate expression.
• Fetch the body
  

  body('Batch_API')['$multipart'][0]['body']['$multipart'][0]['body']['$applicationHttp']['body']

• Fetch the status code
  

  body('Batch_API')['$multipart'][0]['body']['$multipart'][0]['body']['$applicationHttp']['statusCode']

Keep Daxing!!