jaeW_at_Onyx Coach

while @GrantSmith 's statement that you can't divide by 0 is true, that's not the root cause of your problem. (i suspect). you can't write this. even if you ignore the divide by 0 issue, it's still logically wrong because your beast mode will only ever return either 0 or NULL. Because after aggregation has been applied,…

as @GrantSmith when you apply filters it sets the context for what data is available as you calculate the denominator in the percent of total calculation. there is a new beta feature in development that will allow one visualization to support 'filter groups'. the title of the feature may have changed, but the gist of the…

Just JOIN the CLIENT_ID and the CLIENT_LegibleText to your dataset ... then build a filter using CLIENT_LegibleText. Am i not understanding something?

you really should consider implementing a date dimension that contains one row for every day since the dawn of time and calculates your fiscal calendar weeks etc. to assist you could create a webform that indicates the start of each fiscal year and then just use SQL to derive the rest. The risk of embedding it in beast…

... i don't know your data, but i'm not sure why you'd do it in a GROUP BY instead of a FORMULA tile. Also, instead of managing crazy math with a CASE statement, create an Interval column that says how many months to go back (i.e. 1 or 2) and then use your Formula (or GROUP BY) tile to pass the interval (number of months)…

InStr and CHARINDEX are common SQL functions that can get the job done. you can use Regex expressions in Magic (Replace Text)

@user32470 , i'll tell you what i tell everyone. ANYTHING (almost ? is possible in Domo if your data is structured the right way. For this use case, it'd help us if we had a sample of your data and a mockup of your screenshot. Given what i understand about your data, assuming you haven't gone out of your way to restructure…

yes the problem is as you described. but also ... avoid making one dashboard for each region or group of hospitals. you're going to create a nightmare where you have to manipulate 10 dashboards just because everyone wanted one change... instead use a filter card to define the hospital groups if some hospital groups have…

send a ticket to support@domo.com

Definitely ping support@domo.com

you're trying to export ... a table card into a powerpoint? not to state the obvious, but might there be better ways of displaying the data to make it more ... visual... if you absolutely need a table card, consider exporting the data using the Excel plugin, and then linking Excel to PowerPoint.

Couple points here. it is possible to run a job in the Domo Utility CLI (Java CL)I that will remove rows from an UPSERT enabled dataset if you have a CSV with the UPSERT KEY of the removed rows. So ... this will solve your hard delete problem. Alternatively, you can look at data processing models that handle incremental…

this is defo the sort of thing that should be a support ticket. just curious, if you try applying filters (like top 50) does the query still fail?

What you could do is create a Fusion or a Dataset View between a Webform and a Dataset that's JOIN'ed on the email column. Then just maintain your list of users in the Webform and the INNER JOIN takes care of it for you. Seems like hack, but the nice thing is that you can apply that webform + fusion method to a variety of…

@eporama so the Users API does not accept filters, that sucks. agreed. but what you can do is create a users Domo governance dataset in domo then use a dataset apis which do accept filters to get 'the correct user' https://developer.domo.com/docs/dev-studio-references/data-api…

@PhilD is there a way you could avoid having 20 of the same card by maybe using filter cards in your dashboard?

use the bullet chart?

it sounds like you have a dataset with one row per day per project. if you can transform your data I would 1) add a column that flags 'newState_Boolean': such that CASE WHEN YesterdayState = TodayState then 0 else 1 end. You can use the RANK() function in Magic to acchieve this or LAG (equivalent) in Redshift / MySQL. 2)…

so what is the gap between what you're getting and what you want? "it's not doing what i need it to do..."

I know this wasn't your question, but you should really investigate WHY you would want to hide beast modes from people. If it's b/c there are certain calculations you don't want the rest of the business to know about, you should probably ask yourself if that dataset should be available to the rest of the org .. (pdp).…

@kacy i'm assuming you've created a dataset with 'current day' and average 5 day usage' as columns. you can do that, but I'm not sure I'd recommend this approach because you'll have tons of limited use datasets that only work for one visualization, and eventually it'll become a nightmare to maintain. but setting that…

i don't understand your question. can you include a screenshot annotated with the desired behavior? -- how filtering in analyzer works -- one thing to keep in mind is that when filters in cards (in the filter section) they will show values based on available data WITH OTHER FILTERS APPLIED. So if you apply a filter that…

i think @swagner did something in this vein. https://www.youtube.com/watch?v=oEpkHeGOsr0

could you use a Multi Line Chart? and just use your define your limits as metrics in the dataset / series in then chart?

ooh @GrantSmith thanks for the recognition! just be advised the LAG function will always show the last N rows. it doesn't know if the previous row was yesterday or three weeks ago, LAG just pulls the previous row in the window. So be careful if you know you have gaps in your data.

.. it's not that Preview isn't showing your preview accurately, it shows a max of 100 rows by design. That's just ... how it works. What you can do is FILTER some of your data before you get to the APPEND tile. If you know you're interested in a specific date, customer, or amount, apply the filter and then look. Also, an…

I would bet a year's salary that the problem is in your JOIN clause. There are two possibilities, 1) you're JOINING on a column that sometimes contains NULL. You should never JOIN on a NULL because it creates a cartesian product. in other words, you ultimately multiple each row on both sides of the JOIN by any row that…

@PhilD instead of JOINING the aggregated values to your transactional data, make your dataset TALLER instead of wider. Create a section of data where ActivityType = Actual. Then UNION your aggregation where ActivityType = GroupByResponseGroup (or whatever your appropriate group by clause is). In your beast mode use --…

If you have Magic 1.0 you split your data into 2 parts. Where where Col B is NULL and Col B IS NOT NULL (use FILTER tiles) then you can use SET COLUMN tile or I use SELECT and just choose the column I want to keep. If you're on the Magic 2.0 beta you can use a Formula tile and use IFNULL as Mark recommended. In MySQL you…

Also if you have Magic 2.0 (beta, talk to your CSM) you can use INSTR() in the Formula tile.