Modern Model App designer (preview) – Dataverse (Dynamics 365)


A new Model App designer (preview) was added to the platform recently.

It follows a page-based authoring approach and resembles the new UCI.

Within the Maker Portal, while create an new Model-Driven App, we can select Modern App designer (preview)

Provide the name and description to the app and click Create.

Click on Play to see how the default app looks like

Now let us add the lead and contact entity and some dashboards to it.

Click on New Page

Select Table based view and form. The other option is Dashboard.

Search and select Lead and Contact and leave it checked – Show in navigation option

This adds the form(s) and view(s) for the table selected.


We can click on form and view and can either let all the forms and views selected by default or can specify specific views and forms.

“No forms have been explicitly selected. All forms will be available by default.”

Similarly, we can add a Dashboard

Here we have selected 2 dashboards and kept the option – Show in navigation checked.

We can update the title of the Dashboards added.

From the navigation menu, we can arrange the components added -i.e. move them up and down and as well remove them.

We can also add new Group and also the Subarea of type either Table or Dashboard.


Save and Publish the change and click on Play.

Our App is ready.

Similarly, we can edit an existing App in the new preview designer.

We can also Switch to classic 

Our Classic App Designer à

Lastly, the Data section in the new designer allows us to edit our entity/ table.

DataSection

Hope it helps..

Advertisements

How to – Enable Notification in Model-Driven App (Dynamics 365)


By making use of appsetting and settingdefinition table, we can enable notifications in the Model-Driven App. (not sure if it is documented somewhere / or supported way) – so try in a trial environment.

I think the supported way is through customization.xml 

https://docs.microsoft.com/en-us/powerapps/developer/model-driven-apps/clientapi/reference/events/form-onsave#enable-async-onsave-using-app-setting

Thanks to the below post and tweets by Mehdi EL Amri, which describes the steps to be followed.

https://xrmtricks.com/2021/05/26/a-glance-of-the-onload-event-on-a-model-driven-app-form-async-onload-event/

Basically, we need to add a new record inside appsetting table which will have reference to the settingdefinitionid of that particular setting (Alert notification early access) inside settingdefinition table along with id of the app to which we want it to be associated.

  • Let us get the settingdefinitionid for Allow notification early access.

  • App Id for the Sales Hub.

  • Here we are creating a new record through a console application

  • parentappmoduleid – appid of the model driven app
  • settingdefinitionid – id of the specific setting
  • uniquename – name
  • value – set as true

Now let us create a flow on the creation of contact which will send the notification. (create the notification record)

On creating the contact record, we can see the notification inside our Sales Hub.

Settings allow us to enable/disable toasts and set the toast duration as shown below

Hope it helps..

 

Advertisements

Retrieving security role privileges changes (audit) using KingswaySoft’s Dynamics 365 SSIS Integration Toolkit


We can specify Source Type as AuditLogs within the CDS Source Component Editor of KingswaySoft to fetch the Audit information.

Get the details :- https://nishantrana.me/2018/10/08/using-kingswaysofts-cds-crm-source-component-to-get-audit-information-in-dynamics-365-ce-ssis/

The Souce TypeAuditLogs includes Output type – Audit Details (Role Privileges), which can be used to fetch any audit information related to security roles.

Audit Details (Role Privileges) contains 4 columns, which we have mapped to columns in excel.

  • AuditId
  • OldRolePrivileges
  • NewRolePrivileges
  • InvalidRolePrivileges

Let us execute the package

The output à

Here, the 1st row is when a new security role was created, the 2nd row is when an existing security role was updated and 3rd row is when a security role was deleted.

To get the complete information we need to combine this information (id which is auditid – first column) with the Primary output.

The columns of the Primary Output

After mapping, let us run the package with the Primary Output type.

Here below we can see the complete details by combining both the output using the auditid column

Note – to get the Audit Details (Role Privileges), we need to use SOAP – Service End Point type.

Also refer –

http://mscrmshop.blogspot.com/2016/06/auditing-security-roles-in-crm.html

http://www.kingswaysoft.com/blog/2019/10/16/Extracting-Audit-Logs-for-Multiple-CRM-Entities

https://nishantrana.me/2018/11/26/ssis-and-microsoft-dynamics-365/

https://community.dynamics.com/crm/b/mscrmcustomization/posts/ms-crm-audit-database-table-details

Hope it helps..

Advertisements

Now Maximum of 10 alternate keys can be defined for an entity/table – 2021 Release Wave 1 – Dynamics 365


Previously, a maximum of 5 alternate keys could be defined for an entity.

https://docs.microsoft.com/en-us/dynamics365/customerengagement/on-premises/developer/define-alternate-keys-entity#create-alternate-keys

With 2021 Release Wave 1, the limit has been increased to 10.

https://docs.microsoft.com/en-us/power-platform-release-plan/2021wave1/data-platform/increased-alternate-key-limits

While trying to create the 11th key we will get the below error message as shown below

The table could not be updated: Maximum 10 EntityKeys are supported per Entity.

Check other posts on 2021 Release Wave 1  –

Blog posts on 2021 Release Wave 1 – Dynamics 365

Hope it helps..

Advertisements
Advertisements

How to – Customize Quick Actions in Dynamics 365 CE / Model-driven Power Apps


As part of the enhanced Search Experience, contextual quick actions were introduced in the platform :- https://nishantrana.me/2021/02/09/improved-search-experience-now-adds-quick-actions-2021-release-wave-1-dynamics-365/

E.g. we have Assign, Share, Email quick actions available for Contact, Account, and other entities for the relevance search results.

There can be a maximum of 5 quick actions per entity/table.

The quick actions are a subset of commands available for an entity/table at the Home grid level.

Below are the new rules (Enable Rule) introduced through which these contextual quick actions/commands can be shown or hidden.

  • ShowOnQuickAction – Command will only appear as a Quick Action within Search and will be hidden from the home grid.
  • ShowOnGridAndQuickAction – Command will appear for both Grid and as a quick action.
  • ShowOnGrid – command will only appear for the grid.

To apply these rules, we can use our favorite Ribbon Workbench tool.

Select Customize Command option for the respective command/button within the Home.

Add a new Enable Rule for the command.

Select IsCore as true.

Apply the Enable Rule for the other commands as shown below.

Here we have used the Contact entity/table.

Assign

ShowOnQuickAction

Share

ShowOnGridAndQuickAction

Email a link

ShowOnGrid

Follow

ShowOnGridAndQuickAction

On successful publishing of the above rules, as expected we can see – Assign command hidden and Share, Email a Link and Follow available in the Home grid

And with the quick actions, we can see Assign, Share and Follow available and Email a link command hidden.

Get the details – https://powerapps.microsoft.com/en-us/blog/search-quick-actions-are-now-customizable-in-model-driven-power-apps/

Other posts on 2021 Release Wave 1

https://nishantrana.me/2021/04/21/blog-posts-on-2021-release-wave-1-dynamics-365/

Hope it helps..

 

Advertisements

Duplicate Detection limitations – Dynamics 365


Some time back, had reblogged about Duplicate detection limitations.

The original post – https://crmfunda.wordpress.com/2018/09/26/d365-limitations-of-duplicate-detection-rules/, talks about the below limitations

Let us check each one of them with the enhanced experience that we now have in the platform

  • Duplicate Detection works seamless for Dynamics 365 for Phone app also as shown in the screenshot below.

  • Duplicate detection check kicks in when we qualify the lead

Here, qualifying the lead, pops up Duplicate Detection dialog box listing both the matching Account and Contact record.

We can either choose ignore and save to create a new record or click on continue to merge the record with the selected record(s).

  • On activating a matching inactive contact record,

Duplicate Detection is not triggered.

Duplicate detection can be setup to run on the following events – 

dd

  • While trying to publish 6th Duplicate Detection rule for Account entity,

we get the below exception

System.Web.HttpUnhandledException: Exception of type ‘System.Web.HttpUnhandledException’ was thrown. —> Microsoft.Crm.CrmException: The selected record type already has the maximum number of published rules. Unpublish or delete existing rules for this record type, and then try again.

Thus maximum 5 duplicate detection rules can be published per entity.

More on Duplicate Detection

Hope it helps..

Advertisements