Comments
-
I know this is old but there is currently not an endpoint for directly updating a dataset from a custom app (DDX included). Please see https://developer.domo.com/docs/dev-studio-references/data-api for more information.
-
Unfortunately there currently is no way to drop the filter object into the queries and you would have to make a translation layer for them. The "automatic" way for filters to translate into the queries is the standard card behavior where the refresh happens.
-
The preview on the wiring screen doesn't take into account the app sizing in the manifest. It just tries to best fit the space. If the app isn't full page enabled it will appear as portrait and centered in that space.
-
Yeah sorry, I misspoke. So for the use case I was thinking of the filter app was just one card on a page of cards and in that case the other cards would filter. If you need the filtering in the same card it's a bit different. When you use onFilterUpdate() this will catch the filter event and that will prevent your card…
-
Yes, so what you want to do is use the onFilterUpdate to capture the filters on the page and then in the function you call from onFilterUpdate pass the filters and values you want into the filterContainer which will then filter your data without the refresh.
-
At the bottom of the filterContainer section it shows an example console log of what gets passed into the function you point to from onFilterUpdate. You can take the values you want from that object and put them into your array for the filterContainer.
-
Then have have your function do want you want instead of nothing. Have you reviewed the documentation for onFilterUpdate? https://developer.domo.com/docs/dev-studio-guides/domo-js#domo.onDataUpdate
-
It has to do with the frame the apps use. We are blocking certain things for security reasons and mailto has recently been included into one of the things being blocked.
-
Mailto links were blocked somewhat recently by the browsers and we have plans to allow for setting the frame rules to allow them in the future. Normal links are restricted by the whitelist for security purposes.
-
domo.onFiltersUpdate will run a function when the event happens. If you want nothing to happen then point it to a function that does nothing.
-
Looks like the Manage DataSet grant is currently needed for a user to be able to edit the collection used by this app.
-
I just did some more research into this and it looks like that specific DDX Brick has additional required authorities (aka grants) that more locked down users may not have. I am contacting the team that made the DDX Brick to have them update the documentation on what authorities are required for it.
-
Tyler on your example code you are running a domo.delete to set a permission? That should be a PUT to set a permission. I also see "Users" in your call. In the code example in the documentation that would be the collection name for the example but this may be different than what yours is. You also don't need to set the…
-
I also forgot about the wiring screen. When you edit the card you can set the access granted by the app instance. It should default to what you need already, then you just need to share the card with the users you want to have access.
-
AppDB and Datasets are separate things and the permissions are also handled separately. We have an upcoming feature to make it easier to deal with permissions on AppDB but you currently can make changes using endpoints detailed here - https://developer.domo.com/docs/dev-studio-references/appdb#Collection%20Level%20Security
-
Does this help with what you are looking to do? https://developer.domo.com/docs/dev-studio-guides/domo-js#domo.navigate There may also be a feature switch you need to have turned on for your customer to setup your whitelist and the Support team can help you with that.
