Personalized Community is here!
Quickly customize your community to find the content you seek.
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2022 Release Wave 1 PlanDynamics 365 release plan for the 2022 release wave 1 describes all new features releasing from April 2022 through September 2022.
2022 release wave 1 plan
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
I checked the behavior in "Cumulative Update 29 for Microsoft Dynamics NAV 2018 (Build 42633)" version. Goto a customer, and enable the boolean field Disable Search by name. Then create a Sales Order for the customer, and add items to sales line.
Then Goto the Shipping & Billing fasttab. Change the Bill to Customer to Another customer, and select another customer, and post the Sales order.
1. The Name field of Bill to customer is not taking the names, it takes the Customer No.
2. Posted Sales Invoice is not created for Bill to customer, and created for Ship to customer
3.Account Receivable entries in Customer Ledger Entries are created for Ship to customer, instead of Bill to customer.
This Behaviour is not observed in BC version CU19, So Anybody knows, if the CU fix is available for the above bug in Nav 2018 version.
I ran the scenario on build 11.0.47405.0 and the behavior is not observed in that CU. Unfortunately, I do not know if there was a bug number created for this release.
Hope it helps.
Thanks for your reply. To be more precise, I found the above bug in Environment – NAV 2018 Cumulative Update 46
Application Version - NAVW111.00.00.47915
If the issue is not observed in build 11.0.47405.0 but observed in build 11.0.47915.0, then feel free to raise it so we can verify it and hopefully fix it if approved by PG.
That remembers me to always verify in latest build. I am waiting for December CU's for all my own installed releases that should soon be published.
Business Applications communities