Hi @Zach_Jacobs ,
Unfortunately, yes, this is a bit more difficult to configure. However, I have created a Feature Request for this functionality and will follow up should it be implemented in the near future.
In the meantime, this question was also discussed in these forum posts, perhaps they can also provide some guidance on creating your tenancy logic:
The best way to do this at the moment is to render the list of devices in the page layout. Each item in the list is then a link to a dashboard page (which is inside that layout) that uses context to show the clicked device.
[device-dashboard]
Here’s a detailed breakdown of each step in that process:
0. Create the device dashboard
The first step is to create the dashboard you’d like to use to display your device data. Make sure it’s properly configured with a device ID context variable. We’ll …
Hi @Tim_Sahr ,
Thank you for the clarification, this is much more clear now! I took a look at your experience and I believe you are missing just one thing to limit the displayed devices by userGroup. Just as you did previously, you will have to set the dashboard context for your userGroup tag context variable:
[36%20AM]
Because this is not set, the userGroup equals *, which will display devices with a userGroup tag. I believe the Dashboard Context should look like so based on your use case:
…
Hi!
I’m working on an application that has several experience groups levels.
I’m trying to build a tree-based JSON structure that will contain the entire experience group hierarchy along with the devices that are associated with each group.
I built a workflow that uses the “Group: Summary” node for getting the group hierarchy structure.
And now, I’m trying to get the devices associated with each group using the Losant API (Experience Groups: get) node which should get a list of all the group…
Thanks so much,