Sean_Tully Contributor

I got this to work with a few beast modes. First, I had to convert your string into a timestamp, using the str_to_date function. It looks like this: STR_TO_DATE(Timestamp, '%d %b %Y %T'). Next, I used the lag function to get the the timestamps on the same row: lag(min(Timestamp), 1) over (order by Timestamp) Finally, I…

Sorry, I didn't save it, but it would be something like: case when category = 'A' then category else '' end The basic idea is to return the label for the series you want, and then a blank string ('') for the others.

I think you can do this by creating a beast mode that outputs only for the line you want, and outputs a blank string ('') for all the other lines in the series. You can drop the beast mode into the tooltip slot, and then choose the tooltip as your label in data label settings. This worked for me when I tested it on a chart…

Try something like this, replacing the field with your actual field name: SUBSTRING(SUBSTRING(`FIeld`, INSTR(`FIeld`, '_')+1), 1, INSTR(SUBSTRING(`FIeld`, INSTR(`FIeld`, '_')+1), '_')-1)

You could do this using variables and beast modes. You'd need four variables (period 1 start, period 1 end, period 2 start, period 2 end). Then you can create two beast mode to use those those variables to get your sales (eg, period 1 sales could be sum(case when date_field >= period_1_start and date_field < =…

A couple of solutions using Magic ETL - 1) Use a window function to rank the records in descending time, then look for rank 1 in your card; 2) Do a group by to find the max time, then cross join that back to your data so that you can find the most recent time in a beast mode, where the Time field equals the Max Time field.…

I just tested this, new values are excluded.

If you add the date fields as page filters and save them to the view, I think that would behave the same way as the quick filter. The filters would remain present on the page, and users can interact with them and choose the filter dates/criteria they want.

I don't think this is out-of-the-box functionality, but it's definitely doable with a custom app. I attended the custom app workshop at Domopalooza this year and the app we made had this specific functionality. Link to app dev page: https://www.domo.com/business-apps/app-dev-framework

Sorry, I may have misunderstood the request at first. I think this might work? It sums the on hand weight, and adds the farm weight variable once to that sum. It seemed to work in some mock data I threw together, but let me know if I got it wrong again :) (SUM(On Hand Weight)+min(Farm Weight)) / SUM(Daily Sales Average)

Maybe try wrapping farm weight into the first sum: SUM(On Hand Weight+Farm Weight) / SUM(Daily Sales Average)

I think there's a way to do this by figuring out the day of week of the created field, the day of week of date of response, and the datediff of the two. You should be able to calculate how many weeks turned over from those three points of data, and therefore how many 2-day weekends which you can subtract within your…

Awesome, thank you! Wasn't aware of that chart property.

Sorry If I've taken this too literally - this solution may not work if you have a lot of different products that you're trying to find attach rates for. I did get it to somewhat work with a couple of fixed function beast modes, though it's not an ideal solution. First, I made a beast mode that looked for orders that…

There might be a way to do this with a fixed function beast mode, but I'm not sure how at the moment. I'll give it a shot and update if I can figure something out. However, if I had to do this, I would probably do something in Magic ETL to unpivot the products so that I had one row per order and then a column for each…

It's hard to know what the issue might be without seeing screenshots of the flow. One thing that comes to mind, though, is to make sure that the fields you're joining on are of the same type. If they don't match, you can change a field's data type in the input tile's Configuration > Data Handling.

I believe you should be able to do something like this using a variable. You would build a slider control for the Margin Concern, then use that in a beast mode that you would use as a filter, so that when you interact with the control, it adjusts/filters the card for you. Here's Domo's documentation for variables:

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.