Dataverse – Page 30 – Nishant Rana's Weblog

Date Time Fields (Date Only and User Local – Behaviour) in Power Automate (Dataverse)

Recently we faced an issue in our flow that was showing a different date that the date entered by the user for a date time field.

Let us look at the below scenario to understand it.

Say we have the below field Date and Time with Time Zone Adjustment as User Local created in CRM / Dataverse.

Now user enters the below value in in the field and saves the record which triggers the flow.

The user’s time zone is set as below

Now in our Power Automate flow, we can see the UTC date for it.

2023-08-27T20:00:00Z

Now to convert to the user’s New Zealand Time Zone we can make use convertTimeZone function here

convertTimeZone(triggerOutputs()?[‘body/cr0e8_mydatetimefield’],’UTC’, ‘New Zealand Standard Time’, ‘MM/dd/yyyy’)

We get the date as expected i.e. 28^th

Now let us change the Format of the field to Date Only, and we keep the Time zone adjustment as User Local only.

Let us trigger the flow again. (now we don’t have the time part)

We get the date without time part as expected.

But this time the convertTimeZone
function doesn’t work, as we only have the Date part and it is not in the UTC format.

convertTimeZone(triggerOutputs()?[‘body/cr0e8_mydatetimefield’],’UTC’, ‘New Zealand Standard Time’, ‘MM/dd/yyyy’)

Check this thread that talks about it –

https://powerusers.microsoft.com/t5/Building-Flows/Dataverse-Date-only-field-is-set-1-day-off-from-original-value/td-p/805859

Here one quick fix could be to change the Time zone adjustment to Date Only or Time zone independent for that field(i.e. no time zone conversion).

https://learn.microsoft.com/en-us/power-apps/maker/data-platform/behavior-format-date-time-field#date-and-time-column-behavior-and-format

Now triggering the flow again, we get the below values –

as now there is no time zone conversion for that field.

Hope it helps..

Advertisements

Fixed – The ‘CreateMultiple’ method does not support entities of type ‘none’. MessageProcessorCache returned MessageProcessor.Empty in Dataverse / Dynamics 365

Recently while trying to use the new CreateMutipleRequest message we got the below error –

“The ‘CreateMultiple’ method does not support entities of type ‘none’. MessageProcessorCache returned MessageProcessor.Empty”

It was because we were not populating the EntityName property of EntityCollection class. Specifying it fixed the issue.

Hope it helps..

Advertisements

Fixed – URL was not parsed due to an ODataUnrecognizedPathException or Bad Request – Error in query syntax (Power Automate)

We got the below error while trying to set a lookup field because of the incorrect syntax.

The incorrect syntax / formula –

It should be either logicalcollectionname(GUID)

Or logicalcollectionname/GUID

https://nishantrana.me/2022/06/20/fixed-resource-not-found-for-the-segment-in-power-automate/

After setting it correctly, the flow ran successfully.

Hope it helps..

Advertisements

Getting Started – Installation and Setup Kupp Code Analytics

In the previous post, we covered key features and capabilities of Kupp Code Analytics – the powerful Visual Studio Extension for Power Platform and Dynamics 365 Developers.

You can refer to it here

In this blog post, we’d cover the installation and setup of the Kupp Code Analytics extension.

To get the extension, inside Visual Studio Marketplace, we can search for it and download the appropriate extension.

Below we can see that there are 2 versions of the extension available, one for Visual Studio 2022 and the other for Visual Studio 2019.

Visual Studio 2022 – https://marketplace.visualstudio.com/items?itemName=KuppSoftware.kca2022

Visual Studio 2019 – https://marketplace.visualstudio.com/items?itemName=KuppSoftware.KuppCodeAnalytics2019

We can also install it from inside Visual Studio, navigate to Extension, search for Kupp Code Analytics, and download the extension.

Click on Install / Modify (if already existing) to start/modify the installation.

Below we have successfully installed the extension for Visual Studio 2019.

Next, we need to specify and activate the License

We have 2 types of licenses available for the extension.

Community License (free)– Select type Single, enter the contact details and click on Activate to apply for the community license. Clicking on Activate activates the license instantly.

Enterprise License – This is paid license for the enterprise, that comes with additional features and capabilities not available in the Community license.

We can contact the sales team of Kupp for it – https://kuppsoft.com/contact/

Once added, we can see and manage the license information in Tools >> Options >> Kupp Code Analytics >> License

With Extension Installed, and the license activated, the next step is to configure the tool to connect to our Power Platform / Dynamics 365 Environment.

Navigate to Extensions >> Kupp Code Analytics >> Connection >> Configure

Select the appropriate connection or deployment type

Here to connect to Dynamics 365 Online, we keep the Deployment type as O365 and click on Load Organization

This opens the sign-in dialog where we can provide the appropriate account details.

After successful sign-in, we see all the environments populated to which the user has access. Select the environment, we want to connect to.

After selecting the environment, we can click on the Test D365 button and test the connection.

On a successful connection, we will get the success message as shown below.

Clicking on OK will close the connection dialog box, and the tool will start the process of downloading the metadata for the environment connected. The download should be complete in a matter of a few seconds.

This completes the installation and configuration part of the extension. In the next blog post, we’d cover the key features of the extension in detail.

Also don’t forget to check out the other intuitive products developed by Kupp Software GmbH –https://kuppsoft.com/our-products/

Hope it helps..

Advertisements

Fixed – Power Automate flow not getting triggered

We had one flow on the creation of an account record, our flow was running fine, and then we made a few changes to it and saved it, after which it stopped getting triggered.

We could not figure out why it was not getting triggered so eventually we tried changing the Trigger Type to Added or Modified or Deleted, just to see if that will trigger it.

It ran this time on create of account record.

After which we changed it back to Added, the original definition.

And from that point onwards it was getting triggered as expected.

Also make sure if the Admin mode is turned off.

https://learn.microsoft.com/en-us/power-automate/triggers-troubleshoot#verify-if-admin-mode-is-turned-on

Hope it helps..

Advertisements

How to – Create an Automated low-code plug-in (Dataverse) (experimental)

In the previous post, where we installed the Dataverse Accelerator app and saw how to write basic low-code Instant Plugins.

How to – Create an Instant low-code plug-in (Dataverse) (experimental)

Here we’d look at the Automated low-code Plugins.

Select the New Plugin option in the Dataverse Accelerator app to create Automate Plugins.

We get the option to select the table, the event, define the behavior of the plugin using Power FX, specify pre or post-operation, and the solution as shown below.

To keep it simple, we have created a plugin on pre-operation that checks for null, the email address field in the Contact record on Create, and if blank throws an error.

On trying to create a contact record without an email address, we get the exception as specified in the plugin.

That’s all we are done with our plugin.

Now interestingly if we check our solution specified, we will not find our plugin there. We need to add them to the solution manually right now, here we need to look for FxExpression.