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

The ultimate Microsoft Fabric, Power BI, Azure AI & SQL learning event! Join us in Las Vegas from March 26-28, 2024. Use code MSCUST for a $100 discount. Register Now

Reply
akasthan
Employee
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
Fabric Community Conference

Microsoft Fabric Community Conference

Join us at our first-ever Microsoft Fabric Community Conference, March 26-28, 2024 in Las Vegas with 100+ sessions by community experts and Microsoft engineering.

February 2024 Update Carousel

Power BI Monthly Update - February 2024

Check out the February 2024 Power BI update to learn about new features.

Fabric Career Hub

Microsoft Fabric Career Hub

Explore career paths and learn resources in Fabric.

Fabric Partner Community

Microsoft Fabric Partner Community

Engage with the Fabric engineering team, hear of product updates, business opportunities, and resources in the Fabric Partner Community.