Modernize Business Units / Matrix data access structure -Record ownership across business units (Preview) in Dynamics 365 / Dataverse


To enable this preview feature, log in to the Power Platform admin center, switch on the

Environment >> Settings >> Features >> Record ownership across business units (Preview)

It took around 5 minutes to enable.

Now let us say we have a BU structure like below.

And custom security roles with BU level access to Contact – BU Contact Role.

Both user 2 and user 3 have only the BU Contact Role of BU 1 and BU 2 business unit respectively assigned.

Below is the Contact record created by User 2.

As expected User 3 does not have access to the above record.


Now let us provide the same BU Contact role to User 3 but this time from BU 1.

Select the User 3 in Settings >> Users >> Manage Security Roles

The user has already has BU Contact Role in BU 2. Let us change the Business Unit and assign the same role for BU 1.

Click on Save.

On refreshing the All Contacts view for user 3 now we can see both the records, showing the corresponding owner and the owning business unit the records belong to.

This makes it easy to provide required access to the users across the business unit, without the need of sharing the record or using team access or teams ownership concept here.

With this preview, we can also update the Owning Business Unit field.

Below the User 2 is creating a new contact record and setting Business Unit as BU 2.

Here it fails because User 2 only has BU level access for Contact Create Rights, and he is trying to create at BU 2.

Let us update one of the existing contact records, by setting Owning Business Unit as BU 2, this time through System Administrator user which belongs to the root Business Unit.

As expected the record is available to User 3, as we have set BU 2 as the owing business unit.

Get all the details here

https://docs.microsoft.com/en-gb/power-platform/admin/wp-security-cds#matrix-data-access-structure-modernize-business-units—preview

Hope it helps..

Advertisements

Queues in Case Management: Part 1


Vrushali's Techno Blog

Customer service management may require different type of attentions and monitoring depending on parameters such as the different types of customer, priority, different products or services, different subscription levels (regular, premium customers), various activity categories, different geography etc.

Defining Queues is helpful to organize, monitor and prioritize the work by having a centralized list of pending work that needs attention and sorting tasks by type or by the people assigned to complete them

A queue is created by default for each and every user in D365 customer service, we can define additional queues based on our requirements as mentioned above. Let us define a queue and check further details. we have to define paramers for the queue

  • Name: Name of the queue
  • Type – Private or Public : Private queue is having access to limited members and we have to add the members to it. Where as public queues are…

View original post 476 more words

How to – Invoke Power Automate from Dynamics 365 Or Model Driven Apps using Form Scripts


Clavin's Blog

In this blog post, we will Invoke a Power Automate from Dynamics 365 Or Model-Driven Apps using Form Scripts.

Scenario

A person fills up the Form and saves it in the Model-Driven app. The Script captures the items(column) values, passes the values to Power Automate which generates a PDF, and sends it as an Email Attachment.

This article is broadly devide into two main part

  • Configuring Form Scripts in model-driven apps.
  • Invoking a Power Automate from Form Scri

Basics of Client API object modelfor Model-Criven apps

The Client API object model for model-driven apps provides you objects and methods that you can use to apply custom business logic in model-driven apps using JavaScript, such as Get or set column values, show and hide user interface elements, etc. For details on the Client API, object model see the link.

We will Trigger our code whenever a Form is saved(OnSave). We…

View original post 592 more words

Modern link sharing UI, co-presence, online status (preview) in the model-driven app (Dynamics 365)


To enable the Collaboration preview feature, log in to the Power Platform Administration Center, select the Environment >> Settings >> Features >> Collaboration


Currently, the following entities are supported – Case, Contact, Account, and Opportunity.

Enabling this feature adds a new section in the command bar for the records, that allows us to see the other users working on the same record.

Here we can see 2 other users working on the same contact record.

We can select the user’s picture to see their status, send an email, start teams chat, and open the contact card.

Send Email opens the default mail app with To populated.

Teams chat opens the team for a chat.

Open contact card opens the contact’s card.

Share allows emailing the link of the current record and sharing the record.

Email link

Clicking on Manage access opens the share records dialog.

Get all the details here –

https://docs.microsoft.com/en-us/powerapps/user/collaboration

Also check – Collaborate using comments –https://nishantrana.me/2021/12/16/collaborate-using-comments-preview-in-modern-app-designer-power-apps-dynamics-365/

Hope it helps.. 

Advertisements

Quickly visualize the VIEW data using Power BI quick report (preview) in Dynamics 365 / Power Apps


With a recent update to the platform, now we can use Power BI quick report (preview) on the view page in a model-driven app, to visualize the data.

To enable the feature, open the model-driven app in the modern app designer.

Here we are opening the Customer Service Hub app in the modern app designer.

Click on Settings.

Navigate to Features and enable the Power BI quick report visualization on a table option.

Publish and Play the app.

We can see the Visualize this view option added in the command bar for all the views within the app.

It asks for getting a power bi license if we do not have one.

Click on Get a free license and set up the Power BI Account.

Now Visualize this view option will open the Power BI report.

The visuals will run under the context of the view selected – All Contacts in this case.

The visuals will use some of the fields and add additional fields to the table in the report.

Here we are running it against the My Cases view.

The Power BI quick report –

The report gets updated based on the fields selected in the data pane. Power BI adds or removes charts based on the selected fields as shown below.

We can also further Personalize the visual

Visualize this view doesn’t run on selected records for a view.

The option is also available for the Activities view.

The option also works on a Custom table/entity.

Get all the details here –

https://docs.microsoft.com/en-us/power-bi/create-reports/dynamics-quick-create-report

Hope it helps..

Advertisements

Dynamics 365 For Sales: How to merge Accounts if the subordinate record is associated with one or more active quotes?


XRM Tricks (Power Platform & Dynamics CRM )

Merging records on Dynamics 365 CRM is a very powerful feature that prevents duplicate records. I was asked to study this feature for a client who wanted to clean up his customer records, and we reached a point where we had to merge accounts that were related to active quotes. If you didn’t know it, Dynamics 365 For Sales disallows this operation by showing this error message:

After some investigations, I realized that an internal plugin of the Sales module prevents this operation. Actually, it is about the “Microsoft.Dynamics.Sales.Plugins.PreOperationAccountMerge” plugin.

This plugin is internal to Dynamics 365. I could not find out more from the default solution or from the Plugin registration tool. But it’s ok, everything can be shown on the “sdkmessageprocessingstep” table. I used the following fetchXml to see more details:

<fetch> <entity name="sdkmessageprocessingstep" > <link-entity name="plugintype" from="plugintypeid" to="eventhandler" > <filter> <condition attribute="name" operator="eq" value="Microsoft.Dynamics.Sales.Plugins.PreOperationAccountMerge" /> </filter> </link-entity>…

View original post 956 more words

%d bloggers like this: