Forum Discussion
Eventstream and Azure Event Grid - how to get record/array instead of
Hello,
I created an evenstream (enhanced) and connected to Azure Event Grid.
My JSON payload looks like this:
Schema:
I managed to parse string into json record
But now I would like to get separate columns based on that payload
I expected to see a dropdown list with columns to select. But unfortunately it doesn't work. How I can handle this?
Hi foks,
maybe you can solve this by adding a step with a KQL query transformation. There you could parse the json e.g. with the function here:
https://learn.microsoft.com/en-us/kusto/query/parse-json-function?view=microsoft-fabric
Hope this helps!
Best regards!
4 Replies
- v-sshirivoluCommunity Support
Hi foks ,
I would take a moment to thank svelde , for actively participating in the community forum and for the solutions you’ve been sharing in the community forum. Your contributions make a real difference.
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions
- v-sshirivoluCommunity Support
Hi foks ,
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions.
- sveldeSuper User
Hello foks,
welcome to this community forum.
The text in the nested data field is not recognized as JSON so the UI cannot support it directly.
Getting to the separate fields is possible when you use the SQL operator. Using this low-code approach, you can 'program' to get to the values.
As Mauro89 mentioned, the alternative is just passing the Data field on as-is to an Eventhouse and using KQL to get to the separate fields. This can be done both using 'event processing before processing' (the table columns are created for you) and 'direct ingest' (an additional step is offered for mapping the message to a table format of your choice).
If this answer helps you, a thumbs-up or marking it as accepted answer is appreaciated.
- Mauro89Super User
Hi foks,
maybe you can solve this by adding a step with a KQL query transformation. There you could parse the json e.g. with the function here:
https://learn.microsoft.com/en-us/kusto/query/parse-json-function?view=microsoft-fabric
Hope this helps!
Best regards!