Incorrect display of date after implementing the code in query editor

[Jack_Reacher]

I'm fairly new to Power BI, and I'm encountering an issue with the display of the "Action Date/Time" column in my Power BI report and seeking any helpful suggestions on how to resolve it.

Please find below a sample BI file and sample data attached:
https://drive.google.com/drive/folders/15OSktBbdm8rnZnSjzNilRWuz4tFpC3Pv?usp=drive_link

or https://app.nihaoconsult.com/u/d/5d8b0fe3fd9b4d5cb601/

Here's a breakdown of the problem and the relevant data:

The table is related to tickets assigned by two people to different technicians. The "Action Date/Time" column is displaying the date and time when the ticket was returned by the technician to the person who can then either send it back to the technician or close it. In my Power BI report is not displaying the correct dates for occurrences of actions taken on tickets. Despite having the correct raw data, the displayed dates in the report after implementing the query editor are inaccurate.

Problem Details:
Consider the ticket with ID 17920818. Here's a summary of the correct action dates and their corresponding durations:
1. **First Occurrence:** Meryem responded to Salma on 12/03/2024 18:13:20 (duration: 1.01)
2. **Second Occurrence:** Meryem responded to Salma on 25/03/2024 16:48:43 (duration: 1.18)
3. **Third Occurrence:** Meryem responded to Salma on 03/04/2024 17:47:20 (duration: 7.64)

Results in Power BI (Incorrect): 

Any insights or suggestions on how to correct this issue would be greatly appreciated

[v-rongtiep-msft]

Hi @Jack_Reacher ,

I can not download the pbix file. 

Are you doing the right thing in the power query? Is the data displayed correctly in the power query?

Ensure that the "Action Date/Time" column in your Power BI model is set to the correct data type. Power BI should recognize it as a data type.Set and use date tables in Power BI Desktop - Power BI | Microsoft Learn

If you've applied transformations in the Query Editor, ensure there's no data type mismatch that could be causing the issue. Sometimes, date and time columns imported as strings can lead to incorrect interpretations.

Best practices to optimize Q&A - Power BI | Microsoft Learn

Best Regards
Community Support Team _ Rongtie

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