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
We want to make Ledger Account Field Mandatory in Purchase Order Lines based upon criteria that the Item is NON-INVENTORY. Can you please help me out in this.
For all other Items Ledger Account blank should be allowed.
I don't think that this is necessary.
That is because when you setup your non inventory items you can define the accounts that are used when posting the purchase order in the inventory postings matrix under inventory -setup-posting-posting.
making use of this inventory posting matrix is the better option because it ensures a consistent use of ledger accounts for the same item/transactions
Hello Ludwig, Thanks for your reply and inputs. But our requirement is to show a pop-up message to display user to enter Ledger Account in PO Lines. Because this ledger account may vary depending upon type of Item being procured.
my personal view is that this is a totally wrong approach.
if you have different types of items then classify them into an item group and use this group in the inventory posting profile.
only this ensures a consistent accounting.
otherwise you will end up with messy and wrong accounts selected.
Would it make sense in your case to create Service items = to GL account for example and create Inventory posting profiles to these items reffering to the correct GL ACCOUNT. Then you do not have to worry to populate the account on The purchase lines.
Hello Senthil Yadav,
As mentioned by other members; best approach is to set the inventory posting profile with appropriate main account for service type items or item groups so that every time you create a PO, system will automatically populate the main account from the posting profile itself.
Else; if you still want to set this "Ledger account" field mandatory, then customization is the only step to go with.
But still, setting up inventory posting profile will serve the purpose for this.
Kindly review and update in this forum.
Best regards,Sourav Dam
Kindly mark this thread 'Yes' if this is answered your query which may help other community members in this forum.
Or completely wipe-out Inventory posting profiles tab responsible for the expense accounts for Item type service (You need to see how they look like in your case - could be that all of them are in one item group).
If you do not have the profiles defined for the services the user will have to select a general ledger account in order to post as erorr will occure. - No mofications needed
Thanks for your reply/ suggestion. Will ask my concern team about this, in the mean time can you please let me know the Customization step to implement the same.
Hi Senthil Yadav,
I don't think it's a good idea to go for customization to set the "Ledger account" field mandatory.
And also I don't think, this is even possible to set any such condition whether the mandatory validation will only work when non-inventory type items are selected in PO line. Once you set this field as a mandatory one, then it will be always mandatory when you create a new PO in ERP.
Instead; better discuss internally with your team and go with the standard inventory posting profile approach which can serve your purpose better.
Kindly check and update us in this forum.
If I summarize the feedback provided then nobody in the community forum recommends following the idea suggested.
So, please double check whether you cannot apply the 'standard' approach instead of making an ill-constructed system modification that might cause more trouble than doing good.
Any conclusion on this case please?
Business Applications communities