Best Of
Re: Query in card building in DOMO.
@PRC Instead of placing Avg. Duration/Engaged/Transferred as columns or values, put them in the Rows section of the pivot table in Analyzer.
Re: Trigger Frequency Option - When All Datasets Updated
Thank Jae, this is awesome. I think this should be native DOMO functionality but appreciate the workaround.
Micah209
Removing Item when building a card & New Beast Mode window
Can you please return the feature that allows me to simply click the 'x' next to the item when building a card. In order to remove a dimension or metric I now need to select it and open up the properties and select "Remove". Half the time the configuration doesn't even open, or I have to wait an incredibly long time for it to open. This is very time consuming and has slowed down my ability to quickly iterate while building a card. Please revert this back to the way it was.
Also the new beast mode window is huge. I preferred the previous window size. It would be ideal to be able to resize the window, or move it around. Is it possible to make that an option
Re: Is there a way I can edit user's access to only see their locations data on my master card?
Have you looked into PDP? This will allow you to set specific conditions and rows the users are allowed to see.
You can read up on PDP here: https://domohelp.domo.com/hc/en-us/articles/360042935354-Best-Practices-for-Sharing-Content-in-Domo
Re: Is there a way I can edit user's access to only see their locations data on my master card?
@AshleySizemore If you want the users to always see there own data on the dataset and no other locations, then you can look into PDP's.
https://domohelp.domo.com/hc/en-us/sections/360007334593-Personalized-Data-Permissions-PDP-
Re: Card Analyzer - Date Filter Options
Agreed. It's also possible for a data consumer to come to an incorrect conclusion by changing the date range on a card from, say, "Month to Date" to "Last 7 Days" without knowing that the current day is one of the seven.
Re: How to append based on new IDs only - not upsert
Don't partition a table of customers. that is the perfect use case for UPSERT if you use the customer_id as the upsert key.
"UPSERT works well when you're uploading a massive Customer, Product (or similar) table where you have no idea when a particular Customer_ID or SKU might be updated."
Yes, the ideal case for partitioning is the assumption that history never changes (i.e. transactional records). if you have back posted activity (financial stuff) then yes, you may need to periodically reload history, or if you have two columns posting_date and last_modified_date, if you identify that you back post one day last month AND you are partitioning by month, then you'd have to re-upload the entire previous month.
what you don't want to do is UPSERT a (large) transactional dataset because that would be a massive strain on Domo as the dataset grows and eventually cause the data to perform inconsistently as volume increases. (low millions of rows will probably be fine but 10s or 100s of millions would probably be where upload starts to suffer.
Re: Is there a way to aggregate the output using a FIXED function used in a CASE statement?
you could materialize your FIXED function as a column on your dataset by implementing it in DatasetViews. It seems like you need MAX(MAX() ) because you're trying to ascertain "current_week_num" , that's static and probably doesn't have to respond to filter criteria, so just add it as a column.
Re: Put Legends back how they use to be
surely this is a bug. not an intentional design choice.