AS Coach

The first two things I would check are connection to Domo and then connection to your source system. Confirm that your workbench installation is connected to Domo. Is your Domo instance listed in your Accounts section of workbench? Is the token for that workbench install still valid? Second, if your account is up to date…

Try something like this: CONCAT('<a href="',`Link`,'">',`Link`,'</a>')

`Link` and `Title` refer to the columns in the data with the symbols being the column identifiers. Like `NAME` or `COLOR`. All beast mode column references require the symbols. Example: CONCAT('<a href="', 'https://en.wikipedia.org/wiki/Blue', `Name`, '</a>') The name Bob will show up with the underlying link to the Blue…

That's a really great question. I understand some organizations want to be very structured in their approach. So far, we have leaned more informal, but every request typically involves questions like: 1) What business problem are you trying to solve? 2) What metric(s) will you use to attend to that problem? 3) Who is the…

Drill paths can go to any card you want. You can definitely go from state to county to a table card, withlist of customers in that county, or something else. You're just stacking filters with drill paths, but visualization style is open.

Have both the dataflow itself and the dataflow output dataset been transferred to you, or just the dataflow output dataset? It sounds like the latter to me.

You might have to tinker with that. It's not a fully supported function at this time. Magic ETL does not have a SQL edit formula transform, but that's long been asked for. You'll have to use the Rank & Window transform, which is excellent and closely follows the function outlined above. 1) Sum your amount with unbounded…

In the drill path you can click on the box "Prevent drilling to final data grid view". Would that help?

You'd use a window function for that either in beast mode or in dataflow. We have one that looks like this in a dataflow: sum(usd_amount) OVER (partition by customer_group rows unbounded preceding) Which is to say, for every row, broken out by customer group, sum up the amount of all preceding rows in the data. So on the…

For context, what's the business question here? For the recursion to work, you create an output dataset that becomes an input dataset to the dataflow. Something like this: Input: Historical transactions dataset, static Input: Daily transactions, replaced every day Process: Select everything from this historical…

Google is definitely your friend here, and there is no shortage of information on the web. That said, here's what I've used. GA: https://ga-dev-tools.appspot.com/query-explorer/ This is a front-end helper for developing the correct parameters. RegEx: https://regexr.com/ This is an intuitive interface that lets you test…

Have you changed your new input to be the last output of your dataflow (append_new_data_to_historical)? That's key to the recursive nature of this method. The output has to be the new input.

This doesn't sound like something beast mode would be good for. You could potentially do this in a dataflow with declarign a local variable and looping on the repeats, but you'd be creating a new dataset that lives alongside your original data since you can't overwrite the original data (that I'm aware). Would that be…

If you go in the data center to the data warehouse link, you should be able to see some summary data, including number of rows. It doesn't tell you what it is in terms of gigabytes. In fact, Domo doesn't really mention that in many places. It's usually expressed in terms of rows. The dataflow history tab displays input and…

There are a couple things you can do to test, one of which you've already done (creating a dummy, non-corporate user). Looks like that didn't work. It's possible that both gmail and your corporation have filtered out what might look like spam. Maybe try a third domain. Try also researching in the activity logs. Re there…

I think you just have to go to the dataset(s) where that tag is stored and remove the tag from there. Then it will hopefully drop from the available tags list. I tried that in my instance and it worked out well.

Looks like you might have to do two types of formatting in a beast mode to get the two date string variants aligned. Something like case when `dia` like '%/%' then str_to_date(`dia`,'%d/%m/%Y') else str_to_date(`dia`,'%Y-%m-%d') end That might not be totally correct syntax, but should be something to try.

Do you have any sorting in place? Sometimes having a sort in place that isn't one of the dimensions or measures can break aggregations.

All default connection parameters I'm familiar with only accept one file upload per job. That said, Domo's workbench does have an open plugin library where users can build their own. I once had the Domo ETL guys create a plugin that transferred dozens of files into one single source in Domo. So, I think you can do it,…

I had the same thought as @ST_-Superman-_ but it actually works for me as-is. SUM(CASE WHEN DATE_FORMAT(`Date`,'%d') = 1 AND DATE_FORMAT(`Date`,'%m') IN (1,4,7,10) THEN `Value1` END) See attached table sum file. Also from this site the other attachment with format explanation.

You're just trying to sum up Total_HC_Opening for the first day of certain months? I think you could really simplify this: SUM(CASE WHEN DATE_FORMAT(`Date`,'%d') = 1 AND DATE_FORMAT(`Date`,'%m') IN (1,4,7,10) THEN `Total_HC_Opening` END) Does this work?

Is that a drill path card or a top level card? I've seen this behavior when it's a drill down, and we had to start that card from scratch in order to get it to work. If it's a drill down, what date grain does the top level card have?

You'll have to provide more detail for us on this problem before we can assist. Please reply wtih a description of the issue and what you need.

Not that I'm aware of, given the correct configuration of the join. You may encounter a "10,000 duplicates" error. If that's the case, simply swap the inputs and the direction of the join. There are a few posts about that here.

I'm surprised about Safari. IE is typically terrible. Most of Domo employees use Chrome on their Macs, from my experience. I did, too. For anyone perusing this, the supported browser link is at http://knowledge.domo.com?cid=sysreq

This definitely still works for me using Google Chrome. I just tested it using some fake data:

This sounds to me like Domo encountered a problem after the data was loaded and during the table indexing phase. If that's true, it's an error on Domo's part, not yours, and you'd likely just have to rerun the data. Did this happen to multiple datasets? Did it happen multiple times? Hopefully it's isolated and easily…

To echo the first comment, I'd recommend PDPs or Publication Groups, unless you want them to at least have the option of seeing other brands. Do they need to have this same data filtered to brand everywhere else in Domo? Use PDPs. Do they need just this page filtered, and on every data set on the page (if there are…

Good question. I've spoken with probably hundreds of Domo customers and nobody has ever asked me! I'm not sure Domo publishes that information, to be honest. You would probably have to inquire with customer support or your account representatives.

I would do something like: CASE WHEN DATEDIFF(CURDATE(),`trx_date`) <= 30 THEN 'Yes' ELSE 'No' END Then bring that value into your filters, choosing only the "Yes" rows. That would give you all transactions within 30 days. Do you have transactions forward-looking, or just in the past? That may affect how you implement…