DM502 – Simplifying the Inbound ASN V3 XML Process: Converting Excel Data to XML for Non-Technical Users (Part-2)

image-179 DM502 - Simplifying the Inbound ASN V3 XML Process: Converting Excel Data to XML for Non-Technical Users (Part-2)

Series Introduction

This article is Part 2 of 4 in the Automatic Inbound ASN Series, where we explore key Data Management operations in Dynamics 365 Finance & Operations (D365FO). You can find the complete series below:

πŸ“Œ DM501 – Using the Composite Inbound ASN V3 Entity in D365FO
πŸ“Œ DM502 – Converting Excel Data to XML for Inbound ASN V3 (Current Article)
πŸ“Œ DM503 – Securing Data Management Projects in D365FO
πŸ“Œ DM504 – Automating Inbound Load Creation in D365FO

πŸ‘‰ New to the series? Start from Part 1.


Introduction

This article focuses on helping end users who are unfamiliar with XML coding. I’ll demonstrate how to prepare an Excel template and convert the data into the Inbound ASN V3 XML format, enabling users to manage data without deep technical knowledge.


Step 1: Prepare and map xml schema in Excel file

image-149 DM502 - Simplifying the Inbound ASN V3 XML Process: Converting Excel Data to XML for Non-Technical Users (Part-2)
  • Save File
  • Customise excel ribbon and Enable Developer Tab in excel
image-150 DM502 - Simplifying the Inbound ASN V3 XML Process: Converting Excel Data to XML for Non-Technical Users (Part-2)
image-151 DM502 - Simplifying the Inbound ASN V3 XML Process: Converting Excel Data to XML for Non-Technical Users (Part-2)
  • Open XML Maps
image-152 DM502 - Simplifying the Inbound ASN V3 XML Process: Converting Excel Data to XML for Non-Technical Users (Part-2)
  • XML Template uploaded
<?xml version="1.0" encoding="UTF-8"?>
<Document>
    <WHSInboundLoadHeaderEntity LOADID="Load1234">
        <WHSInboundShipmentHeaderEntity DELIVERYTERMSCODE="">
            <WHSInboundLoadPackingStructureEntity LICENSEPLATENUMBER="LP1234">
                <WHSInboundLoadPackingStructureLineV3Entity ITEMNUMBER="ABC123" PURCHASEORDERLINENUMBER="1" PURCHASEORDERNUMBER="PO123" QUANTITY="1" UNITSYMBOL="ea"/>
            </WHSInboundLoadPackingStructureEntity>
        </WHSInboundShipmentHeaderEntity>
    </WHSInboundLoadHeaderEntity>
</Document>
  • Excel displays XML attributes
image-153 DM502 - Simplifying the Inbound ASN V3 XML Process: Converting Excel Data to XML for Non-Technical Users (Part-2)
  • We now need to map each element from XML source to field on excel sheet by Drag and Dropping XML source to excel cells directly.
image-154 DM502 - Simplifying the Inbound ASN V3 XML Process: Converting Excel Data to XML for Non-Technical Users (Part-2)
  • Map Elements
  • Once mapped, xml source attributes will turn BOLD fonts
image-155 DM502 - Simplifying the Inbound ASN V3 XML Process: Converting Excel Data to XML for Non-Technical Users (Part-2)
  • Save Template. Template is ready to use.

Step2 : Run and Test

  • Replace dummy data with real load data
image-156 DM502 - Simplifying the Inbound ASN V3 XML Process: Converting Excel Data to XML for Non-Technical Users (Part-2)
  • Export file
image-157 DM502 - Simplifying the Inbound ASN V3 XML Process: Converting Excel Data to XML for Non-Technical Users (Part-2)
  • Verify exported file content
image-158 DM502 - Simplifying the Inbound ASN V3 XML Process: Converting Excel Data to XML for Non-Technical Users (Part-2)
  • Upload file using data management Project created in previous article.
image-159 DM502 - Simplifying the Inbound ASN V3 XML Process: Converting Excel Data to XML for Non-Technical Users (Part-2)
image-160 DM502 - Simplifying the Inbound ASN V3 XML Process: Converting Excel Data to XML for Non-Technical Users (Part-2)
  • Verify load creation and Packing structure.
image-161 DM502 - Simplifying the Inbound ASN V3 XML Process: Converting Excel Data to XML for Non-Technical Users (Part-2)
image-162 DM502 - Simplifying the Inbound ASN V3 XML Process: Converting Excel Data to XML for Non-Technical Users (Part-2)
image-163 DM502 - Simplifying the Inbound ASN V3 XML Process: Converting Excel Data to XML for Non-Technical Users (Part-2)

Conclusion

In this article, we’ve walked through a step-by-step guide to simplify the process of creating XML files in the format required by the Inbound ASN V3 entity in Dynamics 365 Finance and Operations. By using Excel as the starting point, non-technical users can easily prepare shipment data, and then convert it into the necessary XML format without needing to understand XML coding. This approach empowers end users by making the process more accessible and user-friendly.

In the next article, we will explore how to grant access to data project using the Team Member License, the most cost-effective licensing option available in Dynamics. With this, businesses can provide users with the necessary permissions to handle the data without incurring high licensing costs, ensuring both efficiency and security in the process.

This method streamlines operations, reduces errors, and makes it easier for end users to manage inbound shipmentsβ€”contributing to a more efficient and productive warehouse management workflow.

Expand Your Knowledge: See More Data Management Blogs

Share this content:

I am Yogeshkumar Patel, a Microsoft Certified Solution Architect and ERP Systems Manager with expertise in Dynamics 365 Finance & Supply Chain, Power Platform, AI, and Azure solutions. With over six years of experience, I have successfully led enterprise-level ERP implementations, AI-driven automation projects, and cloud migrations to optimise business operations. Holding a Master’s degree from the University of Bedfordshire, I specialise in integrating AI with business processes, streamlining supply chains, and enhancing decision-making with Power BI and automation workflows. Passionate about knowledge sharing and innovation, I created AI-Powered365 to provide practical insights and solutions for businesses and professionals navigating digital transformation. πŸ“© Let’s Connect: LinkedIn | Email πŸš€

2 comments

Post Comment

Table of Content