Sean_Tully Contributor

Comments

  • Try this: (sum(Oil Usage) / sum(Run TIme Hours)) * 24 I think the aggregation in the beast mode will make it work correctly. Right now it's totaling the column for you instead of doing the calc for the full oil usage and run time hours.
  • Yes, each card was from a different dataset, not joined. By "shared field" I meant they both contained a field with the same name and values.
  • If I understand right, you want to build one card with the ability to choose your series instead of building separate cards? That sounds like a job for variables: Basically, you'll build a variable that lists your different series, then build a beast mode to reference the variable, and use the beast mode as your series.
  • Is "Projected Loads" itself a sum? The grand total might be deduping the values that give you the monthly totals.
  • I'm not sure of the how, but I just tested it with two cards using two different datasets that have a shared field, and the filter worked on both. Maybe the field names aren't exactly the same? Or the value you're filtering on is only in one of the datasets?
  • Yes, the field names have to be the same.
  • If the field you want to filter on exists on both datasets and has the same values, one filter should work on both.
  • You might have to modify your dataset first, as you'll need to have all of the dates in your data if you want to calculate before the end of the month. I would probably start in Magic ETL with the Domo calendar dataset, via the Domo Dimensions connector, filtering it down to the appropriate date frame, and then left…
  • I noticed that the 'Any row is added' option is still available on datasets that aren't views, so maybe you can get the same results you had by doing this in Magic ETL instead of a view. Also, it may be worth opening a ticket with Domo support re: the email, since that just doesn't seem right.
  • Can you use one of the columns as a count instead? It would have to be a row that doesn't contain nulls. So, the Metric would be Total Count of [field], and meeting the condition of a really small change like Changes by .01%. That might mimic the 'any row is added' option?
  • If the number is always the last character of the asset value, I would create a beast mode: right(asset, 1).
  • The output tile in Magic ETL has an append option, which may be the easiest option for you. If not, you can do what you proposed, which is called a recursive dataflow. There's some documentation here:
  • You'll have to set up a separate import for each tab in your document. There is an "Excel Sheet Tab Number" parameter when you set up the connector. If they all have the same data structure, you can then use a dataset view or Magic ETL to union them together.
  • 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…