Skip to main content

MSDYN365BC - Lookup Not Working With Extension Development.

Hi Readers,

Last week Team was working on an Extension Development for a customer and one of my team member reported an issue.

What was the Issue Reported?

Developer added a field "Last Modified By" in Customer Table Extension with Table Related to User Setup Table.

Then he added that field in Customer Card using Page Extension.
#MSDYN365BC, #AL, #VsCode, #LookupTrigger



While testing he was unable to Lookup on Last Modified By Field in Page.

Below are screenshot of AL Code -


How to Resolve Issue?

Old NAV Developers will understand the issue resolution.

If you don't know when you use a Table Relation on a field please make sure that there is no code in OnLookup Trigger of the Table Field.

Even the commented code is not allowed in OnLookup Trigger.

To Resolve this Issue in AL please make sure that Either the Commented Code or Local Variable is removed or the Whole trigger is removed in AL.

To Resolve this Issue in CAL please make sure that the Commented Code or Local Variable are removed from Trigger.

Hope it helps to solve issue if you face same issue during extension or CAL development.

Regards,
Saurav Dhyani
www.sauravdhyani.com

Comments

Post a Comment

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.