AS Coach

I think what you'd want to do there is set the card date range to something fairly inclusive, like last week or last month or all time, and have a beast mode that does that detailed filtering for you. case when DAYOFWEEK(CURRENT_DATE()) = 2 and `trx_date` = DATE_SUB(CURRENT_DATE(), interval 4 day) then 'Include' when…

Okta shouldn't be choosing the security setting. In the admin settings you can determine which role is set as the default. It sounds like yours is set to privileged. Like you, most Domo admins probably want that to be participant instead. The Roles page, top right, gives you the dropdown menu to select your default role.

You can do this with a beast mode that uses some date conditions to make the calculation how you want it. And set the card to all time, not yesterday, since that filter will supercede everything else. Trucks Running aggregation(CASE WHEN `DATE` = current_date() THEN... END), using SUM or COUNT or whatever aggregation you…

Not that I'm aware. All pages will include all cards for report scheduler. I guess an alternative would be to create a publication with only the cards you want. Or set up alerts for that person on all 4 cards,and set them to go out daily, like a "Changes by 0%", type of alert that will always trigger. You should get a…

You'll probably want to speak with Domo support. There aren't any tools available to users that allow us to resurrect deleted objects like that.

Does this happen every time? On the dataflow history tab, each run should have a record log for failure or success. Have you checked the run to see at what point it failed? When you click on the failure badge it should also show you on the next screen which transform failed. It it always failing in the same transform?

You might try turning off the time scale. In the properties menu, Category Scale (X) option, set Never Use Time Scale to True.

Unfortunately, no. Nested beast modes, or beast modes within beast modes, is a hotly requested feature. There should be several posts in the ideas exchange that you can search out and upvote for exposure. Domo's very aware of feature requests like this, but it wouldn't hurt to advocate through any channel you have…

Domo should have included a picture example in this section of the release notes. My guess is the formatting change shows up in the alert icon on the card page, much like an alert being in a triggered state and being colored in yellow.

When you create a workbench dataset, you can pick from the options like ODBC or Excel Spreadsheet or XML or JIRA, etc. DataSet Type is the field name, and it's a dropdown but you can also write whatever you want in there. This will be the name as it appears in Domo and also is the method by which Domo chooses the icon that…

I'm unaware of a way to do this. That HTML is really the data in that field, you're just kinda tricking the browser to display something different than the cell value. Aside from manually removing the extra, you could probably write a macro in Excel to remove the HTML and keep just the text.

Yes, historically existing rows will need a different solution. Perhaps you could start with the dates you wanted in the spreadsheet, then you could remove that date column and then insert the transform in the workbench job, and see if they append to each other.

In your workbench job, you can add a "Transform", a new column of a calculated field. This will insert a new column called 'Test Date', and if you set the workbench job to append, each new set of rows will have a new value in that 'Test Date' column.

You'd need, at the very minimum, a window function for that kind of math. I don't think these are officially supported by Domo for Beast Modes (they are in data flows), so your mileage may vary. To get your denominator it would be something like sum(`visitors`) over (partition by `category path`) Help link:…

Oh man, survey data in a relational database can be so difficult. I started having heart palpitations and sweaty palms while reading your problem description. When processing surveys for a client I had some of the same issues. Too many columns. Column names too long. Manual mapping. Vague errors. Etc. What worked for us…

I imagine that might look like an external application that utilizes the endpoints Domo provides. Then you can schedule that application with its procedures to run the transforms. The devil's in the details, for sure, but Domo does provide a pretty open pathway.

This is a great idea, and has been mentioned before (like in this thread) I'm not aware of a functionality that exists like this outside of using Domo's APIs to push and pull data. You could do it programatically, just not self-contained in Domo yet, is my thinking.

Yes, that's the way I understand it. These companies who offer cloud connectors have written webservices that receive parameters like dates, profile names, filters, etc, and Domo builds a front-end around that to submit those parameters to the company's API. The API will return a result dataset back to Domo. So Domo just…

Thanks. Unfortunately there isn't much public documentation in Domo about that connector. I didn't find anything on their website either, other than their ability to integrate with other platforms or to build to suit. You might inquire with Delacon themselves. They will have developed the endpoints that Domo is using in…

Yep, try http://knowledge.domo.com?cid=sqldataflows.

We'd have to look at the connector documentation. Which connector are you using?

Hi! When you have a process that will take multiple steps, each transform takes care of those steps, then you have an output dataset at the end which results in a new dataset in your data center. The transforms are only steps to get you to that final point. In theory, you could write a query with a bunch of subqueries…

I don't know if it's possible in the tool, but you can work with Domo directly to do this. Contact your customer success manager or account executive. Domo support might be able to help you as well.

Developer.domo.com is your central resource for all that special sauce. https://developer.domo.com/docs/workbench-plugins/workbench-plugins in particular is where you want to start with plugins.

This was released last year and is currently part of the product. I used it yesterday, in fact.

Yes, your beast modes don't have to be just aggregations. Like MONTH(`transaction_date`), which you can put on the X Axis. Or CASE WHEN DAYOFMONTH(`transaction_date`) <= DAYOFMONTH(CURDATE()) THEN 'YTD' ELSE 'Not YTD' END to get you a filter for values up to the current day of the month but nothing after. For example, with…

Hi @nitot I'm not aware of any default functionality that will accomplish this for you. However, you can definitely use Workbench and with a little coding you can create a plugin that can parse all those files and combine them into one. When I worked for Domo we had a Fortune 100 client who had distributed data gathering…

What I've done in your situation is create the dimensions and use them as filters and as series values, as you suggest. You might have a beast mode for year, month, and/or week. You could also create a beast mode for month to date for example, independent of your other new dimensions. Used in conjunction with the month…

What methods have you tried that you're having trouble with? Generally speaking, Domo doesn't care much how large files are. While you might not be able to open that file in a textpad or Excel type application, Domo should be able to grab that file either from Workbench or through the CSV connector.

Are you talking vertical or horizontal? You can't vertically crunch all those rows into one view. Horizontally there's a configuration option for setting column widths as a percentage of the whole. That's found in the General Chart Properties. It would be a comma separated list of percentages for each column, totalling…