cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Highlighted
gunjan
Level: Powered On

Not able to save null value into date field(CRM DYNAMICS instance). Via Flow

Need to store the Date field , based on codition if it is modified new value and if no change in value keep the same value, but this is not happening, i have tried if(condition,'new value',null''), but if i am not putting the value into the field '' the json on save shows "field_questionduedate":null, please help. I believe this is a bug with the microsoft Flow for DateTime fields.

Null values not saved crashing the Flow (saving some hard coded value for date is not the solution.)

Even tried to pass the Null value through "JSON-OBJECT"

{

"DueDate":null

}

if no changes is made into the field it is saved as null, withount any issue.
saved_date.pngDefault no value and date is saveddateTime-issue2.png"message": "An error occurred while validating input parameters: Microsoft.OData.ODataException: Cannot convert the literal '' to the expected type 'Edm.DateTimeOffset'. ---> System.FormatException: The string '' is not a valid AllXsd value.\r\n at System.Xml.Schema.XsdDateTime..ctor(String text, XsdDateTimeFlags kinds)\r\n at System.Xml.XmlConvert.ToDateTimeOffset(String s)\r\n at Microsoft.OData.PlatformHelper.ConvertStringToDateTimeOffset(String text)\r\n at Microsoft.OData.ODataPayloadValueConverter.ConvertStringValue(String stringValue, Type targetType)\r\ndate-issue.png'' is not null for date.

1 ACCEPTED SOLUTION

Accepted Solutions
gunjan
Level: Powered On

Re: Not able to save null value into date field(CRM DYNAMICS instance). Via Flow

Thanks for the repsonse, 

One request can't you generate a Bug / Ticket for this issue as this is very genuine case. The field is optional Flow should also provide same interface as we get in CRM dynamics instance.

 

As you people can also see this is genuine reason.

Acknowledge this as a bug, as the output is going to crash the flow .

 

View solution in original post

4 REPLIES 4
Community Support Team
Community Support Team

Re: Not able to save null value into date field(CRM DYNAMICS instance). Via Flow

Hi @gunjan,

 

Does your problem still exists?

 

Could you please share a full screenshot of the configuation of your flow?

Could you please share a details about your scene?

Could you please share the details of your "If" expression?

The if "If" expression that you provided as below is n't a valid expression:

if(condition,'new value',null'')

 

I have made a test on my side to save null value into data field in sharepoint and don't have the issue that you mentioned.

 

Please share more details so we could provide a proper workaround for you.

 

 

Best regards,

Alice

gunjan
Level: Powered On

Re: Not able to save null value into date field(CRM DYNAMICS instance). Via Flow

Thanks for Your reply, sharing my schenario with you , one important thing i am not able to use null value into DATETIME field in the CRM Dyanmics instance.

I am not able to save a null value into the field of type DATETIME.

 

the if condition is  

if(equals(variables('QueDueDate'),''),null,variables('QueDueDate')) but this fails everytime.
 
Even some person from MS Community Support System Acknoledge the same issue...
 
if_condition.pngissue_is_same.png
Community Support Team
Community Support Team

Re: Not able to save null value into date field(CRM DYNAMICS instance). Via Flow

Hi @gunjan,

 

 

I have made a test on my side ,as @Anonymous said in the link that you provided,we could not save a null value into a Date column of Dynamics 365 entity.

 

There is no way to save a null value into a Date column of Dynamics 365 entity using Microsoft Flow currently.

If you would like this feature to be added in Microsoft Flow, please submit an idea to Flow Ideas Forum:

https://powerusers.microsoft.com/t5/Flow-Ideas/idb-p/FlowIdeas

 

 

Best regards,

Alice

gunjan
Level: Powered On

Re: Not able to save null value into date field(CRM DYNAMICS instance). Via Flow

Thanks for the repsonse, 

One request can't you generate a Bug / Ticket for this issue as this is very genuine case. The field is optional Flow should also provide same interface as we get in CRM dynamics instance.

 

As you people can also see this is genuine reason.

Acknowledge this as a bug, as the output is going to crash the flow .

 

View solution in original post

Helpful resources

Announcements
firstImage

New & Improved Power Automate Community Cookbook

We've updated and improved the layout and uploading format of the Power Automate Cookbook!

thirdimage

Power Automate Community User Group Member Badge

Fill out a quick form to claim your user group badge now!

firstImage

Incoming: New and improved badges!

We've given our badges an overhaul and also added some brand new ones!

fifthimage

Microsoft Learn

Learn how to build the business apps that you need.

sixthImage

Power Platform World Tour

Find out where you can attend!

seventhimage

Webinars & Video Gallery

Watch & learn from the Power Automate Community Video Gallery!

Top Solution Authors
Top Kudoed Authors (Last 30 Days)
Users online (6,695)