brycec Contributor

After creating the template, did you run npm install to install all the necessary dependencies contained in the package.json file?

You can disable filtering entirely on a card by card basis on design/story dashboards. Edit the dashboard > edit content on a card > change filter exceptions > uncheck allow filtering. This unfortunately disables any kind of filtering for that card, not just your slicer. There is no way to allow filtering from one filter…

Currently, filtering in webform edit mode is not supported. You can create a new idea in the ideas exchange if one does not already exist.

You could call the API to get all the PDP policies on the DataSet via this URL: https://api.domo.com/v1/datasets/{dataset_id}/policies Then you could loop through those policies and delete them via this URL: https://api.domo.com/v1/datasets/{dataset_id}/policies/{pdp_id} More information here:

This is a duplicate idea:

I've achieved this by calling the Domo API. Request URL: https://<company>.domo.com/api/query/v1/functions/search Authentication: Header called X-DOMO-Developer-Token with a value of an access token from Admin > Access Tokens. You can then view a Beast Modes dependencies in the activeLinks column, which can be aggregated…

This can be achieved via a DDX brick currently.

You can get this information via the Domo API. Request URL: https://<company>.domo.com/api/dataprocessing/v1/dataflows/<DataFlow ID>/versions, where the DataFlow ID is a couple of digit number from DomoStats, not the DAP DataFlow ID that is a GUID in the URL. Authentication: Header named X-DOMO-Developer-Token with the…

We name all our DataFlows with the prefix DF: and all our DataSets with the prefix Output:, Input:, or View: so that we can tell the difference.

You can get this information via the Domo API. Request URL: https://<company>.domo.com/api/dataprocessing/v1/dataflows/<DataFlow ID>/versions, where the DataFlow ID is a couple of digit number from DomoStats, not the DAP DataFlow ID that is a GUID in the URL. Authentication: Header named X-DOMO-Developer-Token with the…

I've so far found no way around this other than using the multi select quick filter instead of the contains quick filter. I have found this to be annoying as well. I would suggest creating a new idea if one doesn't already exist: , or reaching out to Domo Support if you feel this is a bug and not a feature request.

Could you make the job delete all other policies by selecting "Delete" for the "How would you like to handle orphaned PDP policies?" option in the toolkit, then running an automation that assigns a single policy to the DataSet, then manually deleting that one left over policy?

Have you looked into using variables to achieve this?

To those reading this thread years later: When I looked into this, it is because the version of MySQL that Domo is running does not support WITH. You can check the version by running this command: SELECT VERSION(). That command outputs 5.6.37-82.2-82.2, however WITH and Common Table Expressions weren't added to MySQL until…