Best Of
Re: Dynamic Chart Height
If there are a couple of tables in the dashboard and they have quite a lot of rows and you need to filter the data it becomes really complicated to navigate around the dashboard due to a lot of whitespaces.
How can I remove items from a mega table using a beast mode?
I have a table with 5 columns: The first column (A) lists parts, the second (B) lists countries, the 3rd (C) is a concatenation of the first 2 columns, and the 4th (D) is a concatenation of the same list of parts but other related countries. There are many more countries in column D than in column C, so most of the values in column C are duplicated multiple times. The values in column D do not duplicate. Column E indicates if there is a match between columns C & D.
How can I write a beast mode that will remove all the rows in the mega table for the matching country from column B? (In the picture, yellow highlights the matching row and the red indicates the rows that need to be deleted)
charles
Re: How can I remove items from a mega table using a beast mode?
how do you know which row you want to exclude?
Re: Publishing to subscriber instances problem
Mystery solved. After some trial an error I have worked out that you can only publish changes once in every 5 minute period.
This is absolutely fine for us but when you are testing a feature and the interface doesn't indicate this and the docs state the below it can all get rather confusing and frustrating haha.
Edit: This is working for adding and removing content but updating a chart title doesn't seem to work now at all.
Jones01
Re: Publishing to subscriber instances problem
Thanks for everyone's input. I'll keep you posted when and how I get this resolved.
Jones01
Re: Is there a way to create a static temp table in Beast Modes?
@adeshon we have run into the exact same problem. We have the fiscal calendar enabled and while it is great for breaking charts into fiscal periods and for choosing fiscal periods on the date selector the logic on the period over period charts for prior periods doesn't match our clients.
Our clients take the date this year -364 days to get a comparable date. Domo matches based on the year and week number. This also causes a problem when looking at a 53 week in isolation or ytd including week 53 as it will never have anything to compare to.
For the time being we have an etl that allows us to grab last year and previous years from a beast mode.
https://dojo.domo.com/main/discussion/53481/a-more-flexible-way-to-do-period-over-period-comparisons
I'll add the idea to the dojo so make sure you give it a vote. 👍
Jones01