Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.

Reply
Anonymous
Not applicable

Date value changes betwen Power Query Editor and report screen

I hope someone can help with this. I was going nuts trying to figure out why a date filter was not picking up certain records until I noticed that in the Power Query Editor the date for one record is displayed as 1/16/2019 8:30:00 PM but when I returned to the Desktop report screen the date in the same record somehow changed to 10/21/2019 8:30:00 PM. The weird thing is that this happens to just a handfull of records, the rest that I checked match between Power Query and the report screen.


Any ideas on what is going in here?

 

PowerBI_DateChange.png

6 REPLIES 6
v-frfei-msft
Community Support
Community Support

Hi @Anonymous ,

 

Please close and apply in power query as below and check agian. Or you can refresh the data to have a try.

close.PNG

 

Community Support Team _ Frank
If this post helps, then please consider Accept it as the solution to help the others find it more quickly.
Anonymous
Not applicable

Hi Frank, I've been doing that, this is what I see for the record in Power Query Editor:

Before.png

And this is what I see when I get back to the Report screen after clicking either Close and Apply there or the Refresh button on the main screen.

The report is indended to show order due for the current date but if the due date is being increased by 5 days somehow on random records, it is useless.

 

After.png

 

Anonymous
Not applicable

Here are some further examples of what I'm getting with this report. I exported the data from both the query editor and the report screen into an Access database. The other 300+ records in the data set have no issues, just these 8 random records with random increases in their Due Date value.

QueryEditor.VAOQueryEditor.DueDatePowerBI_Report.VAOPowerBI_Report.DueDateDelta
245417310/16/19 8:30 PM245417310/21/19 8:30 PM5
247209910/16/19 8:30 PM247209910/25/19 8:30 PM9
247286210/17/19 8:00 PM247286212/17/19 9:00 PM61
247315310/17/19 9:00 PM247315310/24/19 9:00 PM7
247539810/17/19 9:00 PM247539810/23/19 9:00 PM6
247558510/16/19 7:00 PM247558510/18/19 7:00 PM2
247598910/16/19 5:35 PM247598910/21/19 5:35 PM5
247733510/16/19 9:00 PM247733510/25/19 9:00 PM9
Anonymous
Not applicable

can you check if there are multiple records for these VAOs?

Record 1:    2454173    10/16/19 8:30 PM    -- You are seeing this record in Power Query

Record 2:    2454173    10/21/19 8:30 PM   - seeing this record in Desktop may be

 

Another check:

try to refresh table from FIELDS section.

Anonymous
Not applicable

No that is not the case. When I imported the two sets of records into the Access database, I set the VAO field as the primary key for both. Since primary keys need to be unique, Access would have warned me if there were duplicate VAOs in the data - I had no such warnings.

 

Just to be safe I manually sorted the data on the VAO columns, no dupes showed up that way either.

Anonymous
Not applicable

One more twist to this strangeness. I compared the data from both the Power Query data and the data showing in the main report screen. It turns out that the main report's due dates are correct, it is the Power Query due dates which are incorrect.

 

This makes me feel better about trusting the report results, however I'd still like to know what is going on with this.

Helpful resources

Announcements
Microsoft Fabric Learn Together

Microsoft Fabric Learn Together

Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City

PBI_APRIL_CAROUSEL1

Power BI Monthly Update - April 2024

Check out the April 2024 Power BI update to learn about new features.

April Fabric Community Update

Fabric Community Update - April 2024

Find out what's new and trending in the Fabric Community.

Top Solution Authors