Forum Discussion
Dataset Refresh Error: 431 - "Request Header Fields Too Large."
. Based on the troubleshooting, Fiddler trace and the error, below are the points which will help you to resolve or reach out to Salesforce for your issue:
- On fiddler I have studied the request headers being sent from your Power Bi to Salesforce and the header has 16470 lines of request being passed to Salesforce.
- The limit set by Salesforce is 16,000 characters and 1000 for the API call to be received so that it can process the request
- The limit is 1000 for the number of calls being made and the character length limit is 16,000 characters for salesforce
- This can be seen on their post as well: apex - How to fix error 431 Request Header Fields Too Large . HTTP CODE[431] in Anonymous Window - Salesforce Stack Exchange
- The iDataReader interface connects your .Net framework to pass the request to the datasource and if the datasource doesn’t respond with the request then it will throw the error
- In summary, you would have to reduce the number of columns that you are writing or adding in your M-Query to resolve this issue
- Once the characters are less than 16,000 characters the issue would be resolved as Salesforce would be able to comprehend those many characters
. Based on the troubleshooting, Fiddler trace and the error, below are the points which will help you to resolve or reach out to Salesforce for your issue:
- On fiddler I have studied the request headers being sent from your Power Bi to Salesforce and the header has 16470 lines of request being passed to Salesforce.
- The limit set by Salesforce is 16,000 characters and 1000 for the API call to be received so that it can process the request
- The limit is 1000 for the number of calls being made and the character length limit is 16,000 characters for salesforce
- This can be seen on their post as well: apex - How to fix error 431 Request Header Fields Too Large . HTTP CODE[431] in Anonymous Window - Salesforce Stack Exchange
- The iDataReader interface connects your .Net framework to pass the request to the datasource and if the datasource doesn’t respond with the request then it will throw the error
- In summary, you would have to reduce the number of columns that you are writing or adding in your M-Query to resolve this issue
- Once the characters are less than 16,000 characters the issue would be resolved as Salesforce would be able to comprehend those many characters
v-nijakk thx so much for your research and coaching - we are importing a Salesforce object that has many columns so it makes sense that we eventually encountered Salesforce's limits on API calls - we're exploring several options but now understand the source of the error msg.
Hello, I know it's been a long timebut just sharing this in case others are hunting for an answer. We also had a salesforce obkect with 700+ fields and got the same error.. This worked for us as we could cherry pick the fields we wanted (and did not need 700+)
Import as normal and you will have a set of steps that fail at step 2.. Leave step 1 intact and change step two as below to "cherry pick" the fields you want. We found you can have up to 698 before this falls over but if you only need a subset of the fields then this works.
let
Source = Salesforce.Data("https://login.salesforce.com/", [ApiVersion=48]),
#"Removed Other Columns" = Table.SelectColumns(
Source{[Name="Name_of_table"[Data],
{
"Name",
"RecordTypeId"
})
in
#"Removed Other Columns"
