JosephMeyers Domo Employee

The Form and DataSet Brick uses a form inside of the app to write to AppDB. AppDB is a document based data system that is separate from the standard DataSets found in Domo. This AppDB data can be synced to a standard Domo DataSet. The DataSet it syncs to is automatically generated with a name using the format…

The workflow Brick only supports mapping a single workflow currently. If your custom app needs to map datasets and workflows you can use the Brick as an example and then create a normal custom app where you can set the manifest to have all the mappings that you need.

Sorry for such a late response but onFiltersUpdate is used to suppress the filter change from refreshing the app and then you will have to code what those filters will do in your app. If you just want the app to reflect the standard page filters and if the dataset being filtered is wired to the app it should reflect any…

As far as links are concerned you will want to use domo.navigate in custom apps

If an AppDB collection is set to sync this will happen automatically every 15 minutes. There is the endpoint to force a sync but if that 15 minute sync or any other sync is in progress the dataset will be locked until that other sync completes. I'm not sure I'm following the issue in the original post. Is the data not…

If there is a sync issue where that dataset isn't syncing it's usually one of a couple things. First you want to make sure the Owner of the collection has access to the dataset the collection is syncing to. Second you want to verify the data in the collection matches the schema. Lastly, you can force a full replace by…

The dataset AppDB syncs to is a new dataset created on the first sync and is usually not the one wired to the app unless you created it and then later wired it to the app. The naming convention by default is {appName}_{appInstanceId}_APP_DB and the description will include "Auto generated from appdb service. datastore:…

If there is a sync issue it's usually one of a couple things. First you want to make sure the Owner of the collection has access to the dataset the collection is syncing to. Second you want to verify the data in the collection matches the schema. Lastly, you can force a full replace by adding a new document and then…

Are the datasets you are querying wired to the app?

Are you referring to the quick filter drop down in the top right? That does not support custom apps you will want to use the standard page filters.

Are we talking workflows or dataflows here? Workflows have a service task to start another workflow called START WORKFLOW. You can find this in function library when you go to select a service task.

The Global Date filter does not currently support custom apps. Standard page filters would need to be used.

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.