brycec Contributor

I don't think so, but maybe someone else knows better than I do. Domo only allows one aggregation level, and two when using FIXED. You can try to change the options for that column at the top (where you normally format the value), and see if you can change the total option to SUM. But, I'd assume that would cause three…

Sounds like the Domo connector was probably built poorly and doesn't include it. I'd suggest using the JSON No Code OAuth connector and just using AirTable's API to build a request yourself. You can test the API in Domo or in a tool like Postman first to see if the URL field returns correctly.

Are you trying to drill from the table you shared? If so, it should be pretty simple. Just create a drill on that card, build out the view your looking for, then to drill click on the program in the table. Bonus, you can actually stay on the drill level but just x out the filter for program shown in blue, and it will…

You could use a YoY chart to show them like this on the same chart. Or, you can use a Beast Mode to filter to that date only, like: `(CASE WHEN DATE_FORMAT(Date, '%Y-%m) = DATE_FORMAT(DATE_SUB(CURRENT_DATE(), INTERVAL 13 MONTH), '%Y-%m') THEN 'Yes' ELSE 'No' END)

You could divide the number in the Beast Mode such that it is represented in millions or billions, then append in the concat a label like mil. or in billions.

Have you tried using the performance tiles that are provided in Magic? They should work perfectly for this. Here's the documentation for them:

Have you tried saving as and seeing if a new card would save correctly or trying to create the card from scratch? You're right, it should allow you to save the card with the subtotals collapsed or expanded. But sometimes cards get messed up and restarting from scratch fixes it.

Make sure you submit an idea in the ideas exchange, because this discussion board isn't for feature requests. I'm commenting here to remove this from the unanswered questions.

You should be able to achieve this using FIXED functions in the Beast Mode. Here is the documentation for them: You'd want to use the FILTER option of the FIXED function to make sure your monthly NPS isn't affected by the fields you specify.

This might be able to be achieved using a FIXED function in your Beast Mode. Here's the documentation for FIXED functions in Beast Modes: It would probably look something like this: AVG((sum(Sales in Jan 2023) FIXED (BY Shop) - sum(Sales in Jan 2022) FIXED (BY Shop)) / sum(Sales in Jan 2022) FIXED (BY Shop)) I haven't…

I find that Beast Modes often fail if the top-most level of the calculation is not an aggregation, but aggregation functions are used elsewhere in the Beast Mode. What I mean is, in your calculation, you are using SUM several times, but the top-level of the Beast Mode is a CASE statement and a divide operation. This may…

I have confirmed that this functionality is working as expected in my instance. Not to say that in your instance it isn't a bug, but hopefully not. You need to have the option "Show Subtotal Rows" checked under the Subtotals section in the card options for this to work. Do you have that checked already?

I believe the landing page is whichever page comes first in the navigation. Go to pages and navigation settings by clicking the copy icon in the left sidebar (looks like two rectangles on top of each other). Then, hover over the page you want to be the landing page, and using the 8 dots icon that appears left, drag and…

I've created a custom connector before, for Brex and Pleo, and published them to the Domo Appstore. Honestly not bad at all, only moderate JavaScript knowledge required. Domo has developer documentation for building custom connectors: https://developer.domo.com/portal/5d8f965eb3469-overview. To actually build the…

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…