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

Microsoft is giving away 50,000 FREE Microsoft Certification exam vouchers. Get Fabric certified for FREE! Learn more

Reply
akasthan
Microsoft Employee
Microsoft Employee

Append query not working and give stack overflow error

Hello

I am try to append two datesets obtained from Kusto into one and facing an stack overflow error.

Just to test this, kept only 1 entry in data set and kept the columns same but still getting the same error.

Dataset Query1: 

akasthan_1-1642681918415.png

 

Query2:

akasthan_2-1642681943522.png

 

Append Error:

akasthan_3-1642681971588.png


Copied the same data in 2 excels and append query works there. Looks like the issue occurs when the dataset is pulled from Kusto. 




Sample Kusto query
ClientEventLog
| where env_time >= ago(1d)
| where ClientPage has "somepage"
| project TenantId, Page
| take 10


Does anyone knows what could be the reason behind it?

 

1 ACCEPTED SOLUTION
v-kkf-msft
Community Support
Community Support

Hi @akasthan ,

 

There is a known issue about appending data from Kusto into power bi based on my search(ICM: 219724212).

 

From the information collected by PG, the best workaround for this is probably to call Table.AddIndexColumn on the Kusto data before using Table.Combine.

The main advantage of Table.AddIndexColumn is that it can be used by someone through the UI without any typing.

 

 

If the problem is still not resolved, please provide detailed error information or the expected result you expect. Let me know immediately, looking forward to your reply.
Best Regards,
Winniz
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

View solution in original post

2 REPLIES 2
v-kkf-msft
Community Support
Community Support

Hi @akasthan ,

 

There is a known issue about appending data from Kusto into power bi based on my search(ICM: 219724212).

 

From the information collected by PG, the best workaround for this is probably to call Table.AddIndexColumn on the Kusto data before using Table.Combine.

The main advantage of Table.AddIndexColumn is that it can be used by someone through the UI without any typing.

 

 

If the problem is still not resolved, please provide detailed error information or the expected result you expect. Let me know immediately, looking forward to your reply.
Best Regards,
Winniz
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Thanks a lot @v-kkf-msft, this works.

Although I went ahead with the alternative approach of taking union in Kusto itself before pulling the data in PowerBI.

let query1 = ClientEventLog
| where env_time >= ago(1d)
| where ClientPage has "somepage"
| project TenantId, Page
| take 10;
let query2 = ClientEventLog
| where env_time >= ago(1d)
| where ClientPage has "somepage2"
| project TenantId, Page
| take 10;
query1 | union query2;


Helpful resources

Announcements
PBIApril_Carousel

Power BI Monthly Update - April 2025

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

Notebook Gallery Carousel1

NEW! Community Notebooks Gallery

Explore and share Fabric Notebooks to boost Power BI insights in the new community notebooks gallery.

April2025 Carousel

Fabric Community Update - April 2025

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

Top Solution Authors