Nishant Rana

How to – enable/disable the timeline highlights generated by generative AI – Dataverse / Model-drive Apps

With the Timeline highlights (Generative AI) feature, agents can quickly view the critical information (summary) about the different activities in the timelines, without the need for clicking/reading through each of the activities.

We can enable and disable it at both the form level, app level and environment level.

At the form level, we can check/uncheck the Enable Timeline Highlights checkbox for the timeline component.

A screenshot of a computer

Description automatically generated

A screenshot of a computer screen

Description automatically generated

At the App level, open the Settings >> Features for the corresponding App.

Here if we disable it at the App-level it won’t show up even if it is enabled for that particular form for that particular app.

For e.g. we see timeline highlights in the Sales Hub App but not in the Field Service app in which we had it disabled for the account form.

We can also specify it using the Setting Definitions and Environment values as shown below.

More details –

Use timeline highlights powered by generative AI

Timeline highlights help users quickly access actionable record updates

Hope it helps..

This password does not meet the length, complexity, age, or history requirements of your corporate password policy (Minimum Password Age)

We might get the below error even after specifying a new password having the appropriate length, complexity, age, etc.

If you are also facing the same, it could be because of the Minimum password age policy setting. It specifies the duration for which the password must be used before it can be changed. It could be a value between 1 and 998 days, also it can be set as 0, which means the password cannot be changed again immediately.

A screenshot of a computer error

Description automatically generated

In our case also, we had changed the password and within a few minutes we again wanted to change it for some testing, that is where we got that issue. Finally, after 24 hours, we were able to do so.

The below article explains in detail about different Password Requirements and how they apply in the case of Azure AD.

https://www.linkedin.com/pulse/what-active-directory-azure-ad-password-requirements-valentin/

Hope it helps..

Advertisements

This operation cannot be performed because there is an active lifecycle operation on the environment – Dataverse / Power Platform

While trying to enable Admin Mode for one of our Dataverse Environments,

we got the below error

“This operation cannot be performed because there is an active lifecycle operation on the environment”

A close-up of a message

Description automatically generated

This was because we had a copy operation going in the background, we were copying that particular environment to another environment.

After the copy operation was completed (around 1 hour, for the environment DB Usage – 45 GB, File Usage – 118 GB, and Log Usage – 21.63 GB), we were able to switch on the Admin mode.

Hope it helps..

Advertisements

Fixed – The system could not log you on. This could be because your user record has been disabled in Microsoft Dynamics 365 error when trying to create or save a record

Recently in one of our environments, we were getting the below error on trying to create/update a contact or account record.

Exception Message: The user with SystemUserId=xxx-8c8f-ee11-be36-0022489338d1 in OrganizationContext=xxx-8c8d-ee11-8174-0022489425ce is disabled. Disabled users cannot access the system. Consider enabling this user for the action to succeed.. User IsDisabled=True, IsLicensed=True.

As the error message specifies, the system user record SystemUserId=xxxx-8c8f-ee11-be36-0022489338d1 was inactive/disabled.

So we can run the below query to check all the real-time workflows owned by that user

Next, we updated the Owner for all these workflows from Advanced Find.

This then allowed us to save the record.

Next we updated the owner of the remaining processes owned by the disabled user. We can also check and update the remaining components like plugin steps / cloud flows etc.

Click here for more details.

select workflowid, name, primaryentityname, categoryname, modenameg, owneridname, * from workflow
where 
category  = 0  
and ownerid = 'abc-8c8f-ee11-be36-0022489338d1'
and mode = 1

Select * from sdkmessageprocessingstep 
where impersonatinguserid = 'abc-8c8f-ee11-be36-0022489338d1'

Hope it helps..

Advertisements

Dates and values are displayed in your time zone. Because the project could take place in a different time zone, the project schedule may appear incorrect message in the Project entity/table – Dynamics 365

We might get the below message/notification on opening the Project form –

Dates and values are displayed in your time zone. Because the project could take place in a different time zone, the project schedule may appear incorrect.

This message will appear if the Project’s timezone differs from the logged-in user’s timezone.

The project’s timezone is defined in the Calendar

For the user, it is defined in the user settings – Personalization Settings

Let us set it to be the same time zone as the project.

We will not get the notification now for that specific project.

If we check in detail, we can see below out-of-the-box method validateUserAndProjectTimezone getting fired on the onLoad of Project form, which fetches and compares the Timezone associated with the Project and Logged In User and shows the notification.

A screenshot of a computer program

Description automatically generated

Get more details about Work Hour / Calendar Template

Also, check – https://ntrajkovski.com/2021/03/08/projects-related-to-calendar-templates-project-for-the-web/

https://ntrajkovski.com/2021/02/15/project-and-resources-in-different-time-zones-with-project-for-the-web/

https://www.inogic.com/blog/2021/08/how-to-clear-hide-oob-form-level-notifications-in-dynamics-365-crm-using-client-api/

https://joshimandarblog.wordpress.com/2015/02/04/timezone-field-format-in-crm/

Hope it helps..

Advertisements

Bypass execution of specific plugin (step) using BypassBusinessLogicExecutionStepIds parameter – Dynamics 365 / Dataverse

The BypassBusinessLogicExecutionStepIds optional parameter or request header value allows us to bypass a specific plugin step by passing its GUID, irrespective of whether it is synchronous or asynchronous, unlike the other optional parameters – BypassCustomPluginExecution and BypassBusinessLogicExecution that will bypass all the custom synchronous and/ or asynchronous logic (plugins and workflows).

Using BypassCustomPluginExecution and BypassBusinessLogicExecution parameters – https://nishantrana.me/2024/05/21/using-bypassbusinesslogicexecution-parameter-preview-to-bypass-custom-sync-and-async-logic-plugin-and-workflow-dataverse-dynamics-365/

Below we have our plugin registered, that writes to the Plugin Trace log.

The plugin step is registered on the update of the lead record. We have got the StepId of the plugin step from the Properties window.

Below is our console app, which updates the lead, triggering the plugin. On running it without the BypassBusinessLogicExecutionStepIds, we can see the trace log parameter record created.

Upon adding the BypassBusinessLogicExecutionStepIds parameter in UpdateRequest, as shown below, the plugin is not triggered and no trace log is created.

A screen shot of a computer code

Description automatically generated

Also, we can pass multiple Step’s GUID to it

By default, we can maximum of 3 steps to it, which can be defined through BypassBusinessLogicExecutionStepIdsLimit Organization Settings value.