Using Focused view in Dynamics 365


Focused view in Dynamics 365 that allows users to view and manage all their records in one place, allowing them to be more productive, as they can stay on track and avoid getting sidetracked by switching between multiple screens to find the information they need.

We can enable and disable it for all the records from the Power Platform Admin Center

A screenshot of a computer

Description automatically generated

Let us select the Focused View for the Cases.

A screenshot of a computer

Description automatically generated

Focused View lists all the records of the view, from where we can select the record, and see its details, within the same screen.

A screenshot of a computer

Description automatically generated

We can search, filter, sort, select multiple records, and further customize it.

A screenshot of a computer

Description automatically generated

Search –

A screenshot of a computer

Description automatically generated

Filter –

A screenshot of a computer

Description automatically generated

Select multiple records and perform bulk operations –

A screenshot of a computer

Description automatically generated

From Settings, we can customize the appearance of it –

A screenshot of a computer

Description automatically generated

Here we can specify maximum 4 rows and each row can have a maximum of 3 columns added to it, it can be from the same record or the related record.

A screenshot of a computer

Description automatically generated

Here we have updated it as follows

A screenshot of a computer

Description automatically generated

Next, we have admin mode, where we can lock the customization so that users won’t be able to change it.

A screenshot of a computer

Description automatically generated

From the Default View settings, we can specify the tables on which we want focused view as default.

A screenshot of a computer

Description automatically generated

Below we can see the Focused View updated to show Case Title, Case type, Created by, and associated customer’s email address.

A screenshot of a computer

Description automatically generated

Get all the details here

Hope it helps..

Advertisements

Geofencing unit ‘Mile’ with id: ” cannot be removed – Dynamics 365 Field Service


While trying to delete the Unit records related to the “Distance Units of Measure for Resource and Asset Location Management” unit group, we will get the below error

Geofencing unit ‘Mile’ with id: ‘<GUID>’ cannot be removed

Below is the out of the box plugin that restricts the deletion of the unit

The code for the plugin –

UOM GUIDs –

And the GUIDs within the environment –

To know more about Geofencing.

Hope it helps..

Advertisements

Use Sales Copilot to see the leads and opportunities assigned (Dynamics 365)


Using the “Sales Copilot” we can get the list of leads and opportunities assigned to us in the last 15 days.

For this, we can use the “What’s newly assigned to me” prompt

To enable Sales Copilot, Inside Sales Hub, navigate to App Settings >> Copilot (General Settings) and specify the Sales Apps in which we want the Sales Copilot to be enabled.

To see it in action, open the Sales Copilot Help Pane, select the Sparke Icon to open the Prompt Guide, then Ask questions >> What’s newly assigned to me



The result shows the list of leads and opportunities assigned to you in the last 15 days.

We can than select the record and click on Summarize to get the summary or can open the record to see the details.


Hope it helps..

Advertisements

Use Sales Copilot to see the pipeline (Dynamics 365)


Using the “Sales Copilot” we can get the list of opportunities assigned to us.

For this, we can use the “Show my pipeline” prompt

To enable Sales Copilot, Inside Sales Hub, navigate to App Settings >> Copilot (General Settings) and specify the Sales Apps in which we want the Sales Copilot to be enabled.

To see it in action, open the Sales Copilot Help Pane, select the Sparke Icon to open the Prompt Guide, then Get Info >> Show my pipeline

The result shows the opportunities sorted based on the estimated close date.

Clicking on “Show all” opens the corresponding opportunity view.

Hope it helps..

Advertisements

Use Solution Health Hub to troubleshoot issues in Dynamics 365 Apps (Sales, Marketing, Field Service, Customer Service..)


Using Solution Health Hub we can validate the environment’s configuration, which might get modified over time, to get an idea about the state of that environment and detect and resolve any issues. Solution Health Hub enables rules-based validations, which we can run periodically or manually if we encounter any issues. The rules also get triggered automatically when solutions are installed or updated by Microsoft. The rules check if some of the required processes are disabled or owned by a disabled user, if some of the required web resources are missing, if certain plugin steps are not active etc.

Let us open the Solution Health Hub app and see it in action.

We can see the Rule Sets created specific to different areas (app) like Sales, Marketing, Customer Service, etc.

For an environment where Field Service is configured, we can see the following rule sets.

Let us open the Field Service Rule Set and see the rules defined for it.

We can see around 31 rules defined for Field Service

For Sales, we can see around 6 rules.

Around 22 rules for Customer Service.

And around 5 rules for Marketing

To run the Rules, we need to create a new Analysis Job record and select the corresponding Rule Set.

A summary of rule-set executions will be shown in a few seconds. (runs asynchronously)

We can see one of the rules failed.

Opening the record, we can see the details.

Back in our solution, we can see the steps in the disabled state.

Back in our Analysis Job, let us select the failed rule and click on Resolve.

We can see the message “Resolution is completed.” and the rule passed.

Back inside our solution, we can also see the status as On for those steps.

Now let us run an analysis job for Field Service

On opening the record, we can see the user for which the roles are missing.

For Field Service, we can see an out-of-the-box cloud flow that runs at midnight on Saturdays to trigger the analysis job for the Field Service Rule Set.

And sends the In-app notifications.

Now if a rule fails, we can get the in-app notifications, e.g. we had set the Service Account field as optional on the Work Order form.

That caused the below rule to fail.

This also sent the notification in the app.

More details on it – https://powerusers.microsoft.com/t5/Power-Apps-Community-Blog/In-App-Notifications-on-concerns-related-to-Solution-Health-and/ba-p/1287680

Also, for each of the rules, we can see a corresponding Action that holds the logic.

Hope it helps..

Advertisements

The user cannot write data to this table, only the integration users may write data to this table – Dynamics 365 Project Operations


We configured the Project Operations app in one of our Dataverse Environments, and while creating a Company record we got the below error.

Exception Message: OrganizationServiceFault Microsoft.Xrm.Sdk.InvalidPluginExecutionException: “The user be60d0fd-778e-ee11-be36-00224893a88b cannot write data to this table, only the integration users may write data to this table.” At Mcrosoft.Dynamics.FOCommon.Plugins.Services.ReadonlyEntityService.PreModify(LocalPluginContext localcontext) at Microsoft.Dynamics.FOCommon.Plugins.PluginBase.Execute(IServiceProvider serviceProvider)

Plugin: ExceptionFromPluginExecute: Microsoft.Dynamics.FOCommon.Plugins.ReadonlyEntityPreModify


The error is because the system doesn’t allow creating a Company in the Dataverse / Dynamics 365 Project Operations App. Ideally, it has to be created at the F&O end and integrated with the Dataverse Environment.

Company Concept in Dataverse

The steps to setup / initialize the company data

https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/data-entities/dual-write/bootstrap-company-data

This was because we had unintentionally installed the dual-write application orchestration package that installs multiple solutions in their Microsoft Dataverse environment, which added the company table.

https://learn.microsoft.com/en-us/dynamics365/project-operations/environment/resource-manual-deploy-dataverse-dualwrite

So one option is to remove the Dual Write solutions installed in that environment.

https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/data-entities/dual-write/uninstall-solutions

As mentioned, for Dynamics 365 Notes we got the below error, for which we need to raise a Support Ticket.

Luckily in our case, we had just created the environment a few days back, so had the option to Reset it. So we eventually took the path of resetting the environment with the Project Operations app selected.

Hope it helps..

Advertisements