{"id":4555,"date":"2022-12-23T00:19:56","date_gmt":"2022-12-23T00:19:56","guid":{"rendered":"https:\/\/www.petecodes.co.uk\/?p=4555"},"modified":"2022-12-23T00:20:04","modified_gmt":"2022-12-23T00:20:04","slug":"understanding-the-power-bi-desktop-azure-data-explorer-error-we-reached-the-end-of-the-buffer","status":"publish","type":"post","link":"https:\/\/www.petecodes.co.uk\/understanding-the-power-bi-desktop-azure-data-explorer-error-we-reached-the-end-of-the-buffer\/","title":{"rendered":"Understanding the Power BI Desktop Azure Data Explorer error “We reached the end of the buffer”"},"content":{"rendered":"\n
Microsoft’s Power BI and Azure Data Explorer (ADX) play really nicely together. Power BI has a 1st party connector which allows us to use Kusto Query Language (KQL) to pull data directly into Power BI.<\/p>\n\n\n\n
However, there’s a gotcha I ran into recently while working on a project that took me a while to figure out.<\/p>\n\n\n\n
When configuring the Azure Data Explorer (Kusto) connector from Power BI Desktop’s “Get Data” dialog;<\/p>\n\n\n