Record Displays Incorrect Date

[BrendonBrooksP1]

For some strange reason, PowerApps is displaying the incorrect date for a record that I have.  Here's the formula that I'm using to create a record. 

Patch('[dbo].[alseInspections]', Defaults('[dbo].[alseInspections]'),{ AlseCard: AlseCardSel.Selected.Value, AlseSn: Text(NextAlseNum), ItemType: ItemType.Selected.Value, Location: InspLocation.Selected.Value, Base: NewBase.Selected.Value, Unit: NewUnit.Selected.Value,  Status:Status.Selected.Value, TailNumber: NewTailNumb.Selected.Value,InspectInterval: Value(InspecIntvNew.Selected.Value), BuildUpDate: Now(), LastInspectionDate: Now(), NextInspect: DateValue(NextInspNew.Text), NextAnnual: DateValue(NextAnnNew.Text)});

This formula adds a new inspection record to the Inspections table in my SQL database. Upon creation of a new record, the BuildUpDate and LastInspection columns will record the current date and time using the Now() formula.  The NextInspect, adds the inspection interval to the date in order for the user to know when the next date is for an inspection.

The column value is set to datetime in SQL . The column in question is the LastInspectionDate. For some reason, it displays the date of the record a full 2 months behind from the date that is in SQL. This is not good because the record will display an incorrect date for when an item is due for inspection. 

I understand that there has been some issues with datetime but this one takes the cake. Any help would be appreciated.

My session ID is below.

Session ID: 599acc7e-9fa7-82d5-ccc6-a656f53e016b

Thanks,

Brendon

[AndyPennell · Accepted solution]

My guess is you are parsing dates in the wrong locale, for example "7/5/2017" vs "5/7/2017" which in this case are about two months apart.

When using DateValue, be sure to specify the locale you expect the date to be in. It will default to whatever locale you are running in, which may not be the same locale you saved it in.

[BrendonBrooksP1]

Not so much....

It turns out that there was a foreign key issue that I had in my dB.  That issue has been resolved, but thanks for the heads up.