A natural next step after building a query is to run it and examine the results.
Since join results are basically a list of trees, a Lightning Component could be built to execute the current query (simplest is just send to apex and use Database.query) and display the results graphically.
The UI could use the lightning:treegrid https://developer.salesforce.com/docs/component-library/bundle/lightning:treeGrid/example#lightningComponentDemo:exampleTreeGridBase
Not sure how easy it will be to map nested sobjects into a tree grid but it will need to support:
- top level from entity/attributes
- ancestor entity/attributes
- children entity/attributes
- ancestors of children entity/attributes
Results can be displayed in a new tab next to the download tab
A natural next step after building a query is to run it and examine the results.
Since join results are basically a list of trees, a Lightning Component could be built to execute the current query (simplest is just send to apex and use Database.query) and display the results graphically.
The UI could use the lightning:treegrid https://developer.salesforce.com/docs/component-library/bundle/lightning:treeGrid/example#lightningComponentDemo:exampleTreeGridBase
Not sure how easy it will be to map nested sobjects into a tree grid but it will need to support:
Results can be displayed in a new tab next to the download tab