microsoft / studentambassadors

This repository is for Microsoft Learn Student Ambassadors.
MIT License
130 stars 47 forks source link

Error in Executing KQL Query: "Location" Table Not Found | Microsoft Fabric Bug Bash | Data Analyst #219

Open subhashis2204 opened 1 year ago

subhashis2204 commented 1 year ago

Describe the bug

When attempting to execute the provided Kusto Query Language (KQL) queries from the documentation, I encountered an issue where the queries failed to run successfully. The console displayed an error message indicating that the "Locations" table does not exist.

What happened?

Severity: Medium

Persona: Data Analyst

Link : https://learn.microsoft.com/en-us/fabric/real-time-analytics/tutorial-5-advanced-kql-query

While executing the given sample KQL queries in the documentation I got an error stating that the Locations table does not exist. This issue has been detected on the point 2 of the documentation.

image

I was able to resolve the issue. By replacing the (Locations) with ['Locations'] in the query

image

What did you expect to happen?

The KQL query should execute without any errors and should produce the desired results, as described in the documentation.

How would you reproduce the bug?

Did this happen via Desktop and/or Smartphone?

Desktop

Operating System

Windows 11

What browsers are you seeing the problem on?

Chrome

Version

115

Device

Laptop

What is your current role?

Student Ambassador

What technical topic is this bug related to?

AI/Data Science/Machine Learning

Relevant log output

Error 

Semantic error: 'lookup' operator: Failed to resolve table or column expression named 'Locations'

clientRequestId: KustoWebV2;460aa39f-fc68-4d0d-a323-c251b610d4ce
github-actions[bot] commented 1 year ago

Thank you for submitting this issue! The team will review your issue, tag with the appropriate tags, and comment with any additional questions on information needed. :sparkles:

subhashis2204 commented 1 year ago

Hello @vivsridh4 please note that this bug is present in quite some part of the documentation. Wherever the Location table has been referenced.