Best Of
Re: Implementing Card Navigation Settings that already existed in Dashboards.
@khushboo_ This is not an intuitive solution. I would have to click details at the bottom left of the page, then click on the edit button on the top right of the page details and then I will be able to click on the card to get those settings. As you can see, that is still more clicking and moving the mouse around than simply adding a card option button on each card. There is no need for me to "edit the entire page" if I want to edit a singular card.
Your solution also doesn't cover the breadcrumb issue I have brought up. What I don't understand is why are dashboard cards equipped with these capabilities, but these app studio cards aren't if app studio is designed to be an upgrade from dashboards.
Re: More customization in text cards
Why do we have the option to bold or use italic but not underline?
Also, you can't change the color of the bullets or numbers, they don't match the text and you are also able to adjust the size, so when you select header, title, subtitle etc, the bullets or numbers don't match in size with the text.

Re: Can you help me understand why SQL Transform takes so long to run and how I can make it faster?
I agree with all of @ggenovese's recommendations for optimizing the SQL. If you're still not satisfied with the performance after implementing those suggestions, you could also consider replicating this in Magic ETL (still following the previous guidance). I've seen some significant performance improvements since migrating SQL dataflows to Magic ETL, most notably since Magic can process multiple steps concurrently, while the SQL transforms can only be run sequentially.
Re: Can you help me understand why SQL Transform takes so long to run and how I can make it faster?
I'd recommend that you break up some of the work into separate transforms. For example your B sub query could be a separate transform that's joined in to the main transform. You can also pre-filter A in it's own transform and then do your joins.
After you have parts segmented out into separate transforms you can review the execution times of each transform to see which parts are taking longest and make modifications.
Finally, I'd recommend leaving your dataset in a more granular state and letting analyzer do the aggregations instead. This may ultimately be a more flexible design, and I find that Analyzer can perform aggregations very quickly.
Re: Searching by Graph type in my instance
Sometimes I don't remember key words in the title of a card, but I remember what it looked like. Other times, there may be multiple cards with similar names and it would be helpful to further narrow down the search.
Re: Multi-line Chart - Looking for filtered AVGs with Overall AVGs
You would want to create a beast mode that calculates the overall average and put that value in your series. You would want to use the Fixed Functions feature to calculate the overall average. This KB article walks you through it.
https://domo-support.domo.com/s/article/4408174643607?language=en_US
Re: Allow manual refresh of Cloud Amplifier / Federated dataset schema
@Joseph_Peterson That sounds incredible. There are definitely some datasets where TTL/freshness could be set to days and others where I would need 10 min updates.
This would really uncork the potential of cloud amplifier. Manual refresh is mostly helpful when in the creation/iteration process of a new data model where columns are changing frequently.
Thank you for looking at this idea and providing feedback!
Re: 2 lines & 1 bar chart
@verytiredgirl Yes, you can specify how many lines to display under Chart properties > General > Series on left scale. The value entered here dictates how many lines to display. For example, if you enter "2" then the first two measures in analyzer (the Y-Axis value plus the first Series value) will both be displayed as lines.
Re: Integrating Microsoft Teams with Domo Alerts
I think this would be a great feature and enhance Domo's integration with other industry standard platforms.
Re: Controlling Page-Level access in App Studio
You'll need two different apps currently. I'd recommend logging an idea in the idea exchange to allow for more granular app page level access.