Use case: Users belong to the same company and are members of the same Business Unit in Dynamics 365 CE, but they belong to different Sales Territories. By adding the Territory (lookup) field to the Opportunity entity (if you’re using Portal, it’s already available: adx_TerritoryId) we’re able to add a dynamic view that is based on the Territory of the Current User. In the Organization…
Continue Reading StefanS365’s Article on their blog
Add My Territory view to Opportunities based on Current User – There’s Something About Dynamics 365
Posted by Use case: Users belong to the same company and are members of the same Business Unit in Dynamics 365 CE, but they belong to different Sales Territories. By adding the Territory (lookup) field to the Opportunity entity (if you’re using Portal, it’s already available: adx_TerritoryId) we’re able to add a dynamic view that is based on the Territory of the Current User.
Blog Syndicated with StefanS365’s Permission
More About This Author
Array
- Dyn365CE2 February 2024Validate file input of manually triggered flow with trigger conditions
- Dyn365CE25 October 2023Bulk Delete assets in Microsoft Purview via the user interface
- Dyn365CE24 October 2023Bulk Delete assets in Microsoft Purview with Power Automate flow
- Dyn365CE26 March 2023Populate a dynamic Microsoft Word template in Power Automate flow