JohnMiller Contributor

Hey @tempus_jg ! The key attribute is related to the mapping of instances to users. This is used when embedding entire Domo instances in an app or portal and automatically routes users to the correct instance. We have some documentation here: It is also used for Dynamic PDP; automatically segregating large datasets when…

Thanks, @Jones01 ! Very helpful to get an idea of that. I've got it filed internally, but of course the Ideas Exchange is a good way to get some support behind it as well. Thanks, again!

Great question, @Jones01 ! As mentioned, the default behavior is to have that content hidden. We do not have a way to over-ride that default although can certainly look to add something if that's useful. Is that something you'd use regularly vs using filter cards, variables, etc? Thanks!

Thanks, @lbg3222 ! Looks like we may have a feature switch that needs to get enabled in that instance. The easiest path is to connect with your CSM to have them get that enabled. We have the feature switch but have not enabled it for all Subscribers because there are use cases that prefer it disabled (vs enabled). We can…

Hey team Great conversation. Domo uses federated datasets in publish primarily for scale/speed, and cost. The scale/speed comes into play when delivering large amounts of data out to subscriber instances. Copying it to each would just take that much longer, especially as the number of subscribers increases. And any updates…