Skip to main content

Replicating Work Descriptions in Purchase Documents | #MSDyn365BC

Hi Readers,

This video demonstrates how to replicate the work description functionality from sales orders to purchase orders in Dynamics 365 Business Central.

The speaker starts by explaining that the work description field is not available in purchase orders by default. 

They then proceed to create a table extension for the purchase header table to add the work description field and copy the necessary methods from the sales order table.

Next, the speaker creates table extensions for the purchase receipt header and purchase invoice header tables to include the work description field and the get work description method. 

They then create page extensions for the purchase order, posted purchase receipt, and posted purchase invoice pages to display the work description field.

Finally, the speaker creates a codeunit to subscribe to the insert purchase receipt header and insert purchase invoice header events and transfer the work description value from the purchase header to the respective posted document.

The speaker emphasizes that this approach can be applied to other areas of the application where similar functionality is required.



Comments

Popular posts from this blog

Microsoft Dynamics NAV 2016 - How to Configure Phone Client.

Hi All, In this article we will discuss how we can connect Microsoft Dynamics NAV 2016 with New Client Launched i.e. Phone Client. This Article Contain Steps for a Android Phone as I have Only Android Phone. I am doing it having all tiers on my windows 8 machine, steps remain same for multiple servers but issues might be different. What we Need (Other what we discuss in this article) -  The Service Tier should be on Public IP . Some of the Data-card does not Provide you Public IP. check it for sure.

MSDYN365BC - Data Upgrade To Microsoft Dynamics 365 Business Central on premises.

Hi Readers, We have already talked about the number of steps for upgrading to Business Central on Premises from different NAV versions. After that article, I received multiple requests for an article which list down steps for Data Migration. In this article, we will discuss steps of data migration to MSDYN365BC (on-Prem) from NAV 2017. For this article, I am considering a Cronus Demo Database without any customization. For an actual upgrade project, we will have to complete object merge using compare and Merge process. After the Merge Process, the next step is data migration. Let's discuss those steps. Direct Upgrade to Microsoft Dynamics 365 Business Central (on-Prem) is from following versions - 1. NAV 2015. 2. NAV 2016. 3. NAV 2017. 4. NAV 2018.

🚀 Exploring Vibe Coding with GitHub Copilot for Business Central.

Hi All, In a recent #BCOpenDiscussion session, we delved into the fascinating concept of Vibe Coding —a new way of building software where developers collaborate with AI (like GitHub Copilot) to co-create solutions.  The session covered practical setup, how AI understands context, and even touched on Microsoft's new Model Context Protocol (MCP) integration for enhanced learning. Let’s break down the journey, step by step.