cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Highlighted
Helper III
Helper III

Dynamics Order entity - Date Shipped

I am trying to post an order to the Dynamics order entity using a create record flow.

The order has not yet been fulfilled so I am leaving the "Date Fulfilled" blank, however I get this error.

 

"message": "DateTime is less than minumum value supported by CrmDateTime. Actual value: 01/01/0001 00:00:00, Minimum value supported: 01/01/1753 00:00:00",

 

There are no other date fields in the post for this error to be related to.

 

Any help?

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted

Which version of Dynamics are you connecting to?

Can you post a screenshot of the Create Record details on how you have it set up?

 

Thanks!

View solution in original post

8 REPLIES 8
Super User II
Super User II

@MartinHutchcpa 

Hi there - Take a look at existing records in Dynamics.  I'd suspect there is a date value on that entity that is listed as "Required" and since your Flow isn't providing one, it's bombing out.

 

Keep us posted.

 

-Ed-

 

 

If this reply has answered your question or resolved your challenge, please consider marking it as a Solution. This helps other users find it more easily via search.

Highlighted

Thanks for your reply.

Unfortunately there are no date fields listed as required.

Highlighted

Which version of Dynamics are you connecting to?

Can you post a screenshot of the Create Record details on how you have it set up?

 

Thanks!

View solution in original post

Highlighted

Editing in Microsoft edge and deleting the field value allowed the record to be created.

Maybe Chrome was the problem?

 
 
Highlighted

Hi @MartinHutchcpa 

 

try setting the value to expression  null with Flow

 

Regards,

Reza Dorrani

 

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly

 

Highlighted

Hi There,

 

I am using powerapps dataflow to load data into Dynamics from Azure SQL DB.

My Data doesnt have data which is even older than 2019 still I am getting this error.

As an example, I have put the below example, which fall in the Error "Bad Request {"error":{"code":"0x80040239","message":"DateTime is less than minumum value supported by CrmDateTime. Actual value: 01/01/0001 00:00:00, Minimum value supported: 01/01/1753 00:00:00"":

Effected Record as below:

PATCH https://MyDomainName.dynamics.com/api/data/v8.2/cr208_allactivetripses(f689df3b-9e3a-ea11-a812-000d3...) {"cr208_accountname":"Sinos[Anton Hässler GmbH]","cr208_accountref":"Sinos[Anton Hässler GmbH]-Company1","cr208_assetcarrier":"Anton Hässler GmbH","cr208_assetid":"265539","cr208_customername":"Company1","cr208_devicecarrier":"Anton Hässler GmbH","cr208_deviceid":"309386","cr208_devicetype":"ExternalDevice","cr208_env":"Company1","cr208_licenseplate":"RH8819","cr208_licenseplatematch":"Correct","cr208_nativedeviceid":"SIN-359858025887595","cr208_outagesince":"4","cr208_plannedstartdate":"16-01-2020","cr208_reference":"60765609","cr208_reportedcarriername":"Dummy-Adresse fuer Company1-Bordero (TRP","cr208_reportedlicenseplate":"RH8819","cr208_rpl":"RH8819","cr208_statusdate":"DAY5","cr208_tripid":"3108090","cr208_tripstatus":"Scheduled","cr208_tsp":"Sinos","pub1_tripSummaryPerAcount@odata.bind":"/cr208_tripsummaryperaccounts(16bb707c-973a-ea11-a812-000d3abaa63a)","pub1_TripSummarPerStatus@odata.bind":"/cr208_tripsummaryperaccountstatuses(35f30760-973a-ea11-a812-000d3abaa4a9)"}

 

Regards,

Arpan

Highlighted

I am also getting this problem, doing the exact same thing as @ArpG which is moving from SQL server to CDS via powerapps --> DataFlow.

 

The two date columns contain only dates greater than 1900-01-01, and NULL values. I'm assuming the problem is NULL. However I didn't want to set them to anything because it would technically be incorrect. NULL is correct because the value is unknown.

 

Is there a way for the date field in the CDS entity to accept NULL values?

Highlighted

Dear @PAM-thrive ,

In the begining I thought the problem is with the null values but

I dont think null values are problem, becuase I didnt face it with null values after I applied a nasty workaround which works for me.

 

I formated the required date fields into Text ( FORMAT (d.LastMeasurementTime, 'MM/dd/yyyy, hh:mm:ss ') in a view in SQL then in Dataflow I am using that view to feed the data. Naturally Dataflow identifies that field as a text fiel but when I am doing the mapping, I have mapped it to a Data & Time field and it worked. If I have null value in SQL they are also successfully exported in Dynamics with null value in the datafield.

 

I didnt like that but it worked for me. hope it will also work for you too.

 

Cheers!!!

Arpan

Helpful resources

Announcements
Community Conference

Power Platform Community Conference

Check out the on demand sessions that are available now!

Power Platform ISV Studio

Power Platform ISV Studio

ISV Studio is designed to become the go-to Power Platform destination for ISV’s to monitor & manage published applications.

Top Solution Authors
Top Kudoed Authors
Users online (6,474)