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

Join the Fabric FabCon Global Hackathon—running virtually through Nov 3. Open to all skill levels. $10,000 in prizes! Register now.

Reply
Antboc8506
Frequent Visitor

DataFormat.Error: We couldn't parse the input provided as a Date value.

Dear all,

it's the first message i'm writing in the community. If some detail will be missing just sorry me and let me know how i can improve the communication.

 

I've prepared a Dataset some months ago coming from the merging of three separate SQL table.

 

The dataset is the same with no change since months, until today when i've got the following error message:

 

DataFormat.Error: We couldn't parse the input provided as a Date value.
Details:
/

 

let
    Source = Table.Combine({DS_ORDER_BACKLOG, DS_PERIOD_REVENUE}),
    #"Appended Query" = Table.Combine({Source, DS_BUDGET_REVENUE}),
    #"Appended Query1" = Table.Combine({#"Appended Query", DS_HOT_OFFER}),
    #"Appended Query2" = Table.Combine({#"Appended Query1", DS_HOT_OPPORTUNITY}),
    #"Pivoted Column" = Table.Pivot(#"Appended Query2", List.Distinct(#"Appended Query2"[Type]), "Type", "Value", List.Sum),
    #"Replaced Value" = Table.ReplaceValue(#"Pivoted Column",null,0,Replacer.ReplaceValue,{"BACKLOG","REVENUE", "BUDGET", "Hot-Offer", "Hot-Opp"}),
    #"Renamed Columns" = Table.RenameColumns(#"Replaced Value",{{"CUSTOMER_NAME", "Customer"}, {"COMPANY_CODE", "Platform"}, {"CUSTOMER_COUNTRY_DESC", "Custom. Country"}, {"AREA_DESC", "Area"}, {"MATERIAL_GROUP", "Material Group"}, {"HIERARCHY_III", "Product"}, {"REVENUE", "ACTUAL"}}),
    #"Filtered Rows" = Table.SelectRows(#"Renamed Columns", each ([Customer] <> "GmbH" and [Customer] <> "bH" and [Customer] <> "O GmbH" and [Customer] <> "THPatz"))
in
    #"Filtered Rows"

The red line is the one that now is not working anymore.

 

No changes happened in SQL and no changes have been made on the Dataset for months.

 

Is there anything i can do to solve this matter or to check what to do?

 

Thanks for the help

1 ACCEPTED SOLUTION

Dear @v-yuta-msft ,

thank you for your kindness.

 

Today the scheduled refresh and the desktop files are working fine without issues. I confirm no modifications have been done so far.

 

Lukily is self-solved even if it's weird.

 

Thank you again

View solution in original post

2 REPLIES 2
v-yuta-msft
Community Support
Community Support

@Antboc8506 ,

 

This issue should be caused by the imported date type can't be recoginized by power bi. Please make sure power bi desktop is the latest version. 

 

In addtion, if this issue still occurs, could you share some sample data so that I can test on my side?

 

Regards,

Jimmy Tao

Dear @v-yuta-msft ,

thank you for your kindness.

 

Today the scheduled refresh and the desktop files are working fine without issues. I confirm no modifications have been done so far.

 

Lukily is self-solved even if it's weird.

 

Thank you again

Helpful resources

Announcements
September Power BI Update Carousel

Power BI Monthly Update - September 2025

Check out the September 2025 Power BI update to learn about new features.

FabCon Atlanta 2026 carousel

FabCon Atlanta 2026

Join us at FabCon Atlanta, March 16-20, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.

Top Solution Authors
Top Kudoed Authors