Forum Discussion
We reached end of buffer Error
- Anonymous6 years ago
I figured this was probably a memory issue, so I removed columns I determined were unnecessary and was able to get the API URL to load. Loading so many custom fields through the API really seems to slow it down, but I got the ones I needed.
What step does the error occur in Power Query? The first place I'd be looking is your Text.Combine(List.Transform(_, Text.From), ";") statement. A list returning unexpected amounts, or an unexpectedly large amount of data, could cause an error. You'll need to click on each statement in Power Query and wait for it to resolve or error out to pinpoint the issue.
- Anonymous6 years agoNot applicable
It appears to be happening at the first step, "Source". It happens both when I refresh my current document or if I load the API URL in a new pbix file.
So this is likely a problem with the source I am getting my URL from?
- edhans6 years agoCommunity Champion
Yup. Something is so messed up, your feed cannot even supply the data properly.
- dax6 years agoCommunity Support
Hi Anonymous ,
I am not sure which factor cause this problem, you could try to remove the table.buffer() function to see whether it work or not. Or you also could try to refer to this post to see whether there is something wrong when you connect data.
Best Regards,
Zoe ZhiIf this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
- Anonymous6 years agoNot applicable
Hi dax ,
Thanks for your suggestions. I tried removed the table.buffer function and got the "We cannot reach the buffer" error again. I switched the file origin to 1200:Unicode as stated in the link you sent me. I then get a "We found extra characters at the end of JSON input" error. I get the same result when I add table.buffer back in the code. I've included screenshots here.
Researching this extra characters error now.