Sean_Tully Contributor

Not sure you can do all that in Domo without maybe building a custom app? However, I wonder if you could use the table link to fill out a Google Form, where the dispute manager could do the uploads and and the rest of the process. Just a thought, not sure if feasible.

Here's the KB article:

Looks like you're on the right screen to create your variable. You have to add the name, description, and choose what type of values/control it will use. Once that's all set up and you create/save it, it will be available for referencing when you create new beast modes.

The "Add Column" group by option for combining strings uses the comma as a separator, but the "Add Formula" option allows you to use the group_concat formula you've already written.

AFAIK dataset views do not have this functionality. I do believe you can do this in Magic ETL using a Group By formula, which might be fast enough for your needs depending on the size of your inputs.

Agree with @GrantSmith. Another calc that would count the transaction as 1 if there is no quantity would be sum(ifnull(`quantity`, 1)).

Domo has some out-of-the-box period-over-period charts that might be useful to you: However, I don't think they work with the stacked series like you're doing in your chart. One way to get the YOY variance in the chart would be to drop the beast mode into a tooltip field, then you could display it the data label.

Is your Target Value populated? If I don't add a field to Target Value, I see the min/max/avg, but if I add a Target they go away. If you don't need a Target Value, you could probably just use the regular vertical bar chart and remove the mix/max/avg there in that chart's settings.

I would do this by using a formula tab to get the week number for each row, WEEK(`Date Column`,22). The '22' in this formula makes Monday the start of the week. Then I would do a couple of filters in separate streams from the data - WEEK(`Date Column`,22) = WEEK(Current_date(),22) -1 and WEEK(`Date Column`,22) =…

Something like this MIGHT work, but it's hard to get it exactly correct without playing with the data directly. If the sales/days are consistent, I think you can look back at the previous month's counts to figure out the frequency. This is an example, not sure if it will exactly work, but what it's doing is counting up the…

Not sure if this will exactly help, but if you go into Edit Dashboard mode then go to the card on the left's Edit Content → Change interaction, you can deselect the right card from being affected by interactions with the left card. In that case, if you hover over Australia on the left card, the card on the right will not…

I'm not totally clear on what you're trying to do. Are you trying to create the "Frequency" field you circled, or do you want to translate it somehow? What are you hoping to display in your card?

I think @GrantSmith's suggestion is probably the best way to do this. If you only have a few country values in your dataset, though, you could also do this by building beast modes for the metric for each country one at a time, then a total beast mode, and plotting them all together.

Sorry, was playing around with it and couldn't make it work. I suspect the analyzer doesn't like the rank function for this purpose, but I'm not sure. Interestingly, if I put the phone number on the card as a series, the bars did stack and it looked more correct, but I'm sure you don't want to see them stacked like that.…

Do you have any sorting going on that might be making it deaggregate?

Is this to identify current state or would you need to know historically if the action was needed? If the former, I think you can use a fixed function in a beast mode to find the latest 6 week average and compare that to your current week count. If you need history, I think you'll need to use MagicETL to group by each…

The upper function just helps standardize the strings so that they'll match even if they have different cases within the data. For "matches field 3" you would just add another line to identify them: case when instr(upper(`field2`), upper(`field1`)) > 0 then 'matches field 2' when instr(upper(`field3`), upper(`field1`)) > 0…

I'd probably do something like case when instr(upper(`field2`), upper(`field1`)) > 0 then 'Looks good' else 'Looks bad' end

I had the same thing happen to me yesterday. Also some strangeness when typing in the beast mode text box, like characters lagging or missing after I typed them.

I think you can add 'filter=Fiscal Months = [current month]&' after the '?' in your query definition, but I don't know JS enough to know how to create that [current month] value. You can also do the filter via ETL/View before it hits the app like @ColemenWilson suggested, or I think you can just add the filter at the time…

I accepted @ArborRose's answer. We found a way to what we needed without using the fixed function, though not in the same way - we used case statements for each year and added those up rather than the nested fixed function.

Yeah, sorry, it was just the generic 'This calculation contained a syntax error' message in the beast mode, but we've had a few eyes on it and rewrote it piece by piece and we don't see any problems with the syntax, other than maybe nesting the fixed functions within each other throws the error. In the end it looks like…

It's something like this: sum(SUM(Total LTV) fixed (by Year, Dimension 2, Dimension 3)) / sum(SUM(Total Orders) fixed (by Year, Dimension 2, Dimension 3))

I think this would work conceptually: In ETL, filter out all the zeroes, so you only have the rows with the calculation values. Then, use a window function to lead the next date with a value, so that each row has the original date, the calc value, and the next date with a value. Join that back to the original input with…

How is the dataset you're using structured? And can you clarify your first sentence? I'm not sure what "and not update at" means.

Try just sum, not sum(DISTINCT), if you have 2+ rows with the same value sum(DISTINCT) would only use one of them in the calc.

I also usually Google "domo" plus whatever I'm trying to find/solve for, I generally end up here.

I think if you create the right PDP policies, you can prevent this type of sharing from happening:

Yes, that's my understanding based on the thread I linked to. We usually reach out to our account rep instead of support for these types of things, though.

Looks like it's something that can be turned on behind the scenes: