However, `cast_params` seems to expect `{"group_names"=>"admins,moderators"}`
I tried to test this naive change, and the params worked.
```ruby
def self.params_to_hash(query_params)
params = JSON.parse(query_params)
params_hash = {}
params.each do |param|
key = param["key"]
value = param["value"]
params_hash[key] = value
end
params_hash
end
```
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [March 6, 2025, 10:03pm UTC](https://meta.discourse.org/t/syntax-for-data-explorer-params-in-automation/355916/3 "2025-03-06T22:03:37Z")
wow thanks for the debugging here 🤗 we will have a look at this in the upcoming week.
---
### Author:  [@ted](https://meta.discourse.org/u/ted)
#### Post date: [March 13, 2025, 7:47am UTC](https://meta.discourse.org/t/syntax-for-data-explorer-params-in-automation/355916/8 "2025-03-13T07:47:30Z")
That’s some fantastic spelunking, @Arkshine! 🙂
I’m looking into this now. When I read the original code I get the impression that it expects the parameters to be an array of arrays, so I’m a bit weary of just throwing the existing stuff out. Will try to figure out when this might happen.
Will post here when I find something.
---
### Author:  [@ted](https://meta.discourse.org/u/ted)
#### Post date: [March 13, 2025, 10:01am UTC](https://meta.discourse.org/t/syntax-for-data-explorer-params-in-automation/355916/9 "2025-03-13T10:01:01Z")
There was indeed a bug here, and partly thanks to the investigation of @Arkshine, it was relatively easy to fix:
[https://github.com/discourse/discourse-data-explorer/pull/363](https://github.com/discourse/discourse-data-explorer/pull/363)
This has been merged already, so once your site has been deployed you should be unblocked @ganncamp.
If I understand correctly, you want an automation that is a one-to-one mapping between a group and its report? (I.e. `group_a` receives a report with `group_a` data, etc.)
There is (currently) no connection between the recipient list and the report parameters, so to accomplish that you’d need to set up one automation per group. In this case you might want to change the parameter to `group_id`.
---
### Author:  [@ganncamp](https://meta.discourse.org/u/ganncamp)
#### Post date: [March 13, 2025, 11:51am UTC](https://meta.discourse.org/t/syntax-for-data-explorer-params-in-automation/355916/11 "2025-03-13T11:51:35Z")
Great news @ted!
> [@ted](#):
>
> to accomplish that you’d need to set up one automation per group
Yes, being able to `foreach` a set of groups was going to be my next request 😄
---
### Author:  [@ted](https://meta.discourse.org/u/ted)
#### Post date: [March 14, 2025, 2:19am UTC](https://meta.discourse.org/t/syntax-for-data-explorer-params-in-automation/355916/12 "2025-03-14T02:19:50Z")
> [@ganncamp](#):
>
> Yes, being able to `foreach` a set of groups was going to be my next request 😄
This does indeed seem like a convenient thing to have, especially for sites with lots and lots of groups. I’ll note down the request, but I can’t say when we’ll get to it. 🙏
---
### Author:  [@j.jaffeux](https://meta.discourse.org/u/j.jaffeux)
#### Post date: [March 17, 2025, 10:09am UTC](https://meta.discourse.org/t/syntax-for-data-explorer-params-in-automation/355916/14 "2025-03-17T10:09:47Z")
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.