Unanswered

Importing Data from Excel to Dataverse Table: Date if off by four years

(0) Share

Report

Posted on by bdcmanager

Hello,

Each month I use a template to upload sales data from an Excel sheet to a custom dataverse table. The MM and DD are correct with the import, but the YYYY is off by 4 years, no matter what year is in the date. I've got use 1904 date in the options screen. i've attempted to use UTZ time zones with the dates, and each time it's off by 4 years exactly. The only way I'm able to get around it is add 4 years to the excel sheet before importing.

For example:

Excel Date	Dataverse Date After Import
7/1/2023	7/1/2019

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (4)

Answers (0)

bdcmanager 9 on at

Like (0)

Report

*Removed comment*

Was this reply helpful? Yes No
Drew Poggemann 9,287 Most Valuable Professional on at

Like (0)

Report
Hi @bdcmanager ,

How are you importing this data from Excel? I have seen issues with timezones but this looks to be something completely different of course.

Do you have any workflows, flows, plugins that could be in effect that "On Create" are setting the value of this field?

If you create the record from within the maker portal, this sets the date accurately without adding the 4 years?

Was this reply helpful? Yes No
bdcmanager 9 on at

Like (0)

Report

Hello,

I use an Excel sheet to log the MTD sales data and performance reports. And at the end of each month, I upload the excel sheet via the Data Import under Advanced Settings for PowerApps.

When I do an import via Excel sheet, whether it's in the table itself OR advanced settings with field mappings, it does it.

When I paste the information directly into the PowerApps table, the date is correct. Or when I manually add it as a new row, it's correct. The issue with this method is I have a lot of data coming in and I don't want to upload it until the end of the month. I use the table for MoM and YoY data. And pasting it directly into the table is extremely slow and buggy and often times gets stuck on a saving loop that doesn't end up saving the table. So I find the import is the best way and map the fields accordingly, but constantly have to go back and change the date.

2023 imports as 2019. And my worry is next year it's going to import as 2020 and I have sales data with 2020 in there.

Was this reply helpful? Yes No
Drew Poggemann 9,287 Most Valuable Professional on at

Like (0)

Report

Hi @bdcmanager

I have never seen anything behave like this... If. you would like another set of eyes to walk through with you I would be happy to jump on a Teams call and you could walk through the process and maybe I will see what is happening? Send me a direct message if that is of interest.

Was this reply helpful? Yes No