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
2020 release wave 1Discover the latest updates and new features to Dynamics 365 planned through September 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 TimelineWatch the 2020 Release Wave 1 virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
As a business analyst, I have had some exposure to Dynamics NAV. Within one particular client's company they had NAV not only managing warehousing, inventory, retail sales and automated B2B purchasing. I was not present during the implementation of this instance of NAV but certainly while I was with this company I was not aware of any issues with NAV,
However, with a new client and a relatively new NAV implementation there seems to be a few headaches.
I've learned about one issue with Inventory management and it just seems strange to me. And so my question is - do all NAV implementations require this or has the developer taken the product in a non-standard direction?
The client has customer sales packages setup. So one customer may be on sales Package A and Item Z is charged at $10, another Package B and Item Z is charged at $12, another Package C and Item Z is charged at $9.
During a particular month you may have customers that have purchased:
* 3x Item Z on Package A
* 2x Item Z on Package B
* 5x Item Z on Package C
I'm not sure whether the process of reduction of inventory of Item Z is through their association with Invoices throughout the month - or through small warehouses performing a stock take. I think it is through invoicing and the following issue arises during the stock take process.
So instead, at the end of the month NAV showing a deduction of 10 from the total of Item Z - the client found that NAV was representing:
* -3 in some inventory item representing Item Z AND Package A
* -2 in some inventory item representing Item Z AND Package B
* -5 in some inventory item representing Item Z AND Package C
When this was raised with the Vendor-Developer their solution has been to develop a solution that takes the -3,-2,-5 amounts and apply them to the more generic Item Z total.
So my question is - is it normal for NAV to have to be customised to do what seems like bread and butter inventors and sales management?
It also seemed odd to me that this issue was left for the user of NAV to discover. If it was standard implementation practice to configure/customise the relationship between sales packages and inventory management - then all the holes would be plugged before the user set out to use the system.
Also it looks like you need simple assembly orders to package A, B, C and standard nav will work without any modification.
Are you suggesting that this system must not have been setup using 'simple assembly orders'? Can you theorise what may have been implemented instead?
Sounds like a bad setup for me.
"Item Z in Package A", "Item Z in Package B" and "Item Z in Package C" are seem to be individual Items with a corresponding inventory.
It doesn't make sense to create an Item only because of prices.
You could handle different prices per Product using a Campaign- or Customer Price Group.
Business Applications communities