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

Win a FREE 3 Day Ticket to FabCon Vienna. Apply now

Reply
Anonymous
Not applicable

Dataflow refresh error - (400) Bad Request

Hi Community,

I need some help with debugging an dataflow error, please help.

 

I have a dataflow that was refreshing okay as per schedule until 17th April. It gave error on 18th April and then again refreshed okay 19th and 20th. Again, it started giving error for refresh since 21st. Below is the error details.

 

18th April - Error: Data Source Error : DataSource.Error: SharePoint: Request failed: The remote server returned an error: (400) Bad Request. (Bad Request) DataSourceKind = SharePoint DataSourcePath = https://XXXX.sharepoint.com/XXXX SPRequestGuid = XXXX Url = https://XXXX.sharepoint.com/XXXX/_api/Web/Lists(guid'XXXX')/Items(6255)/Scribe_Name0.. RootActivityId = XXXX.Param1 = DataSource.Error: SharePoint: Request failed: The remote server returned an error: (400) Bad Request. (Bad Request) DataSourceKind = SharePoint DataSourcePath = https://XXXX.sharepoint.com/XX SPRequestGuid = XXXX Url = https://XXXX.sharepoint.com/XXXX/_api/Web/Lists(guid'XXXX')/Items(6255)/Scribe_Name0 Request ID: XXXX

 

21st April - Error: Data Source Error : DataSource.Error: SharePoint: Request failed: The remote server returned an error: (400) Bad Request. (Bad Request) DataSourceKind = SharePoint DataSourcePath = https://XXXX.sharepoint.com/XXXX SPRequestGuid = XXXX Url = https://XXXX.sharepoint.com/XXXX/_api/Web/Lists(guid'XXXX')/Items(7667)/Author.. RootActivityId = XXXX.Param1 = DataSource.Error: SharePoint: Request failed: The remote server returned an error: (400) Bad Request. (Bad Request) DataSourceKind = SharePoint DataSourcePath = https://XXXX.sharepoint.com/XXXX SPRequestGuid = XXXX Url = https://XXXX.sharepoint.com/XXXX/_api/Web/Lists(guid'XXXX')/Items(7667)/Author Request ID: XXXX.

The differences between error codes of two dates are as follows: SPRequestGuid, RootActivityId, SPRequestGuid, and Request ID.


18th April - SPRequestGuid = AAAA1111
/Items(6255)/Scribe_Name0.. RootActivityId = BBBB1111.SPRequestGuid = CCCC1111
/Items(6255)/Scribe_Name0 Request ID: DDDD1111

 

21st April - SPRequestGuid = AAAA2222
/Items(7667)/Author.. RootActivityId = BBBB2222.SPRequestGuid = CCCC2222
/Items(7667)/Author Request ID: DDDD2222


I have exported the data to excel and checked the data, especially for two columns Scribe_Name0 and Author, but unable to find any discrepancy.

 

Can we debug this IDs in anyway to find the root cause?

5 REPLIES 5
v-henryk-mstf
Community Support
Community Support

Hi @Anonymous ,

 

According to your bug report, I haven't reproduced your problem for the time being. You might as well try to delete the data source (File->Options and Settings->Data Source Settings->Clear Permission) and reconnect to see if it works. If it still doesn’t work, please provide a screenshot of the error message and I will answer you as soon as possible.

 

Let me know the result immediately, looking forward to your reply.

Best Regards,
Henry

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

Anonymous
Not applicable

@v-henryk-mstf 

 

It is at the service level, giving failure on scheduled refresh.  There was some discrepancy at the data level in a date column, which we have corrected.  Now, we are getting the error as

 

 

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

Details
2019-09-18T18:30:00Z

"

 

The dates are coming from a calculated column in a SharePoint list, which is a calculated column and type is "Date Only."

 

I am currently examining the formula.  

 

Can you provide some input for the date error please? 

Hi @Anonymous ,

 

Check if the solutions to similar problems below can help you, if these still don’t solve your problem, please let me know in time. Looking forward to your reply.

 

Here is the reference link:
Solved: DataFormat.Error: We couldn't parse the input prov... - Microsoft Power BI Community

Power BI Error - Correcting the error: We couldn't parse the input provided as a Date value. - YouTube

 

Best Regards,
Henry

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

Anonymous
Not applicable

Hi @v-henryk-mstf , Thank you for looking into this.

 

I have tried to follow the video, not getting the desired result.  I am getting this error in the dataflow at the service.  Though my sharepoint column shows the dates correctly, I am getting all the dates here as a unique value, i.e., "2019-09-18T18:30:00Z", even before the data type change.

 

Anonymous
Not applicable

@v-henryk-mstf We corrected the date by converting it first to datetime and then date and it is giving the correct dates, but still we are having the 400 error on dataflow refresh.

 

Helpful resources

Announcements
August Power BI Update Carousel

Power BI Monthly Update - August 2025

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

August 2025 community update carousel

Fabric Community Update - August 2025

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

Top Kudoed Authors