Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2022 Release Wave 2Check out the latest updates and new features of Dynamics 365 released from October 2022 through March 2023
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
We have three different categories nodes under our procurement categories hierarchy. I want to prevent using one of the category nodes for example Category A for one of our legal entities so that users do not use those categories for any type of purchases. On inactivating that node on the procurement category form, it inactivates the category A for all of our legal entities instead. Is there any other possible way to prevent this category displaying in one of our legal entities?
I have worked on similar requirements, but it was difficult to provide this on the same tree structure. In my point view your need
1. Setup where you can define which category needs to be available for which Legal entity.
2. Have a separate table to capture this linking.
3. Based on this linking create a new tree hirerchy.
It would be interesting you achieve this on standard lookup, as this requirement came from many clients recently. I would love to see the code.
Is it not possible to achieve this requirement out of the box?
Out of the box, its not feasible (to my best understanding)
Hello Bell. D,
If the users you refer to are the employees adding items to Purchase Requisition using the Proccurement Categories, then you can configure Purchasing Policies with different catalogs (basically creating 3 catalogs A,B,C where the unwanted nodes are hidden so employees cannot select from the unwanted categories).
If the users you refer to are the Purchasing agent, then the agents can normally only used the items in their Legal Entity so you would have to managed their access using their security roles (assigning only the wanted Legal Entity not the others).
Like Danny mentioned, Purchasing Policies only at catalog level, so you would need to split categories in different catalogs.
Business Applications communities