Date Time Behavior and Format in Power Platform/Dynamics 365 CRM

Prashant Kumar Maurya

Date Time field in power apps has behaviors and formats which control how the data will be stored in CDS (Common Data Service) and how it will pe presented to different users from different time zone on retrieval. Here I will try to explain the same in a simple way with examples for each combination of behaviors and formats.

Behavior: User Local

  1. Format: Date Only
    • User’s provided date gets converted to UTC before it gets saved in CDS.
    • As there is no time part in user input system will take midnight as input time for conversion.
    • Stored data in CDS will have both date and time part.
    • System will convert UTC time to requesting user’s time zone while displaying data in UI.
  2. Format: Date and Time
    • User’s provided date and time gets converted to UTC before it gets saved in CDS.
    • Stored data in CDS will have both date and…

View original post 473 more words

Create Reports (Power BI embedded) using Dynamics 365 Customer Insights

Virendra Agrawal's Blog

Recently, there was a new featured launched into Dynamics 365 Customer Insights to build reports within Customer Insights using the interactive custom report builder (Power BI embedded).

With this enhancement, we’ll be able to combine available metrics/measures and dimensions to create reports with the CI data , using the visualizations we want directly within Customer Insights. It will provide another way of generating the reports and visualise the Customer Insights data (without using the Power BI connector).

In this post, we’ll talk about how we can use the built-in report feature within Customer Insights.

View original post 245 more words

Process Optimization – Dynamics 365 CE / CRM / CDS SSIS Integration toolkit – KingswaySoft

Process Optimizations is a new feature added in the CDS / CRM Destination Component of KingswaySoft’s SSIS Integration Toolkit as part of November 2020 Release.

Check other posts on SSIS and Dynamics 365

These options if enabled, will turn off or disable plugin, workflow, entity auditing during pre-execution temporarily, during the writing process, and will revert the changes to the original state after successful execution.

  • Tentatively Disable Relevant Plugins (if any)
  • Tentatively Disable Relevant Workflows (if any)
  • Tentatively Disable Relevant Auditing (if any)

Let us take a simple example to see it in action.

Here we have a simple data flow that creates contact records inside CDS using Data Spawner.

Let us run the package and see the status of the plugin, workflow, and audit with regards to the contact entity.

As expected, we do not see any Audit records created for contact records creation.

We see an event where Audit is disabled and then enabled later for the contact entity, during the duration of package running and after its successful completion.

We can also see our workflow in status – Draft

In the case of Plugin, we didn’t see the step being disabled and it was still being triggered

As per the documentation –

Get the toolkit here

Hope it helps..

Embedding Canvas App in an Iframe inside Dynamics 365

Canvas App can be easily embedded in a web site using the Iframe.

Say e.g. we have the following Canvas App to be embedded inside Dashboard in Dynamics 365

Save the app and navigate to Details

We can copy the Web link or App ID.

The URL Format –[appId]

The other parameter that can be used are

source, tenantid, screencolor and any additional parameters

e.g.[appId]?source=iframe&screenColor=rgba(120,110,55,1)&param1=value&param2=value 2

  • Here we have embedded it inside an Iframe component within the Dashboard

Publish the change and navigate to the Dashboard, we can see our Canvas App.

If the application is using Azure Active Directory-based authentication, the user will not be asked to sign-in again, else the user will be asked to Sign-in and will be able to access the app if it is shared with them.

Here we have embedded it inside an ASP.NET page, and we are asked to Sign-in.

After successful sign-in

Get all the details here –

Hope it help..

System.FormatException: Input string was not in a correct format exception while registering Plugin in Dynamics 365

We might get the below error while trying to register a plugin.


The plugin project was referring the .NET Framework 4.7.2

And the latest version of Microsoft.CrmSdk.CoreAssemblies – (Sept 29, 2020)


Resolution –

Changing it to 4.6.2 fixed it.


Unhandled Exception: System.ServiceModel.FaultException

An unexpected error occurred.

Server stack trace:

at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation, ProxyRpc& rpc)

at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)

at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)

at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

Exception rethrown at [0]:

at Microsoft.Xrm.Tooling.Connector.CrmServiceClient.Create(Entity entity)

at Xrm.Sdk.PluginRegistration.Forms.PluginRegistrationForm.btnRegister_Click(Object sender, EventArgs e)


<OrganizationServiceFault xmlns=”; xmlns:i=””&gt;



<ErrorDetails xmlns:a=””&gt;



<a:value i:type=”b:string” xmlns:b=””>Plugin/Microsoft.Crm.ObjectModel.PluginAssemblyService</a:value&gt;




<a:value i:type=”b:string” xmlns:b=””>Microsoft.Crm.CrmException: An unexpected error occurred. —&gt; System.FormatException: Input string was not in a correct format.

at System.Text.StringBuilder.FormatError()

at System.Text.StringBuilder.AppendFormatHelper(IFormatProvider provider, String format, ParamsArray args)

at System.String.FormatHelper(IFormatProvider provider, String format, ParamsArray args)

at System.String.Format(IFormatProvider provider, String format, Object arg0, Object arg1)

at Microsoft.Crm.ObjectModel.TargetFrameworkVersionValidator.ValidateInternal()

at Microsoft.Crm.ObjectModel.PluginValidatorBase.Validate()

at Microsoft.Crm.ObjectModel.PluginAssemblyServiceInternal`1.ValidateAssemblyMetadata(ExecutionContext context, IBusinessEntity pluginAssembly, CrmPluginAssemblyMetadata assemblyMetadata)

at Microsoft.Crm.ObjectModel.PluginAssemblyServiceInternal`1.VerifyRegistrationAbility(IBusinessEntity pluginAssembly, Boolean createCall, ExecutionContext context, CrmPluginAssemblyMetadata assemblyMetadata)

at Microsoft.Crm.ObjectModel.PluginAssemblyServiceInternal`1.ValidateOperation(String operationName, IBusinessEntity entity, ExecutionContext context)

at Microsoft.Crm.ObjectModel.SdkEntityServiceBase.CreateInternal(IBusinessEntity entity, ExecutionContext context, Boolean verifyAction)

— End of inner exception stack trace —

at Microsoft.Crm.Extensibility.VersionedPluginProxyStepBase.Execute(PipelineExecutionContext context)

at Microsoft.Crm.Extensibility.PipelineInstrumentationHelper.Execute(Boolean instrumentationEnabled, String stopwatchName, ExecuteWithInstrumentation action, PipelineExecutionContext context)

at Microsoft.Crm.Extensibility.Pipeline.&lt;&gt;c__DisplayClass5_0.&lt;RunStep&gt;b__0()</a:value>




<a:value i:type=”b:guid” xmlns:b=””>3ecabb1b-ea3e-db11-86a7-000a3a5473e8</a:value&gt;




<a:value i:type=”b:int” xmlns:b=””>1</a:value&gt;




<a:value i:type=”b:guid” xmlns:b=””>6906e911-4a07-487a-bdf0-ad52914b9f14</a:value&gt;




<a:value i:type=”b:string” xmlns:b=””>System</a:value&gt;




<a:value i:type=”b:string” xmlns:b=””>System</a:value&gt;




<a:value i:type=”b:string” xmlns:b=””>SystemFailure</a:value&gt;




<a:value i:type=”b:string” xmlns:b=””>UnExpected</a:value&gt;




<a:value i:type=”b:int” xmlns:b=””>400</a:value&gt;



Hope it helps..


Changes in CDS / CRM Destination Component – SSIS Integration Toolkit for Dynamics 365

With version 20.2 November 2020 release, there have few updates added to the KingwaySoft’s CDS/CRM Destination Component, few are changes in the label and others are metadata changes, that one should be aware of before updating.

Check Post on SSIS and Dynamics 365

  • Label changes.

Version 20.1 –

Version 20.2 –

  • CrmRecordId renamed to SavedRecordId

Version 20.1 –

Version 20.2 –

  • CrmErrorMessage renamed to ErrorMessage

Version 20.1 –

Version 20.2 –

Thus, any package saved with the new version will not work with the older version, and it is recommended to take full back up of the package before updating to the new version.

Hope it helps..