The discussion revolves around challenges in automating Data Explorer results, particularly when sending reports via email. ganncamp describes successfully crafting a query to track group activity and extract Jira tickets, but encounters issues when automating the report: links break in email previews, and topic URLs are lost, requiring manual URL recreation. They express frustration that automation forces them to maintain duplicate reports, undermining the purpose of automation. pfaffman suggests using separate queries for exploration and emailing, but ganncamp highlights the impracticality of managing multiple reports, especially for groups with restricted access. tobiaseigen notes a broader need for consistency between the Data Explorer UI and automated outputs, suggesting a feature request for unified, interactive results in both contexts.
You can’t email a report to a group that doesn’t have access to the report. So having two reports means exposing the group(s) to two reports. And maintaining two reports. And it’s more than I want to (or should have to IMO) do.
The promise of the automation was emailing a Data Explorer query, so that’s what I expected to happen
ETA: I’m currently scheduling a third (different) report. We have too many reports that I want to send out to maintain duplicates
I think there’s a feature request in here. I’ve had the same experience using data explorer queries to moderate this community. I like the idea of having query results PM’ed to me on a weekly basis via automation so I can work through them and then have a record of how I am whittling away at a long todo list, but then the results from the exact same query are more interactive via the data explorer UI.
