ST_Superman Domo Employee

@jrtomici I have a question about your example. Wouldn't line 12 get rounded to a different minute then line 13? Line 12 should be rounded to 01:04 while lines 13-15 should be rounded to 01:05. Otherwise, I was able to use this formula to get to the nearest minute: "HH:MM" CONCAT(LPAD(trim(Trailing '.0' from…

Hi @jaeW_at_Onyx - I looked at REMOVE. The problem here is that when you utilize the interactive filter, it appears to override the REMOVE. The interactive filter actually prevents data from being available to the card altogether so even by removing a field from the FIXED calculation, if the card never "sees" the data that…

Hi @Jones01 - The "Managed Attributes" area of the admin section will allow you to select which attributes are being "managed". Any of these attributes that are checked will be available for use in PDP policies or dynamic groups. Hope that answers your question. I don't believe you are able to use a custom field, but you…

Setting the VALUE of setting the data label in the heatmap. This VALUE is designed to display the average value. Is it possible to display not only this average value, but also the number of data used to calculate the average value? @sho - You can use the Tooltip fields to accomplish this. First you need to turn on…

Thought I would add a google translate here: When moving the date with the date filter, move the month with ◁▷ in the upper left of the card It's easy to operate and you can do it even with scrolling.

I really don't enjoy the drop down arrow moving every time you try to click on it now either:

@Goodeman - You should be able to get something like this to work, assuming you have the card sorted by agent name and event time: round(TIME_TO_SEC(TIMEDIFF(lead(`EventTime`, 1) over (partition by `Agent Name` order by `EventTime` asc), `EventTime`))/3600, 1)

You could try using a beastmode, something like case when `SchoolType`='High School' then null else `TestScoreRank` end

@mHejl I think @jaeW_at_Onyx has a good suggestion for you. If that is not working out, it would be helpful if you showed some examples so that we can understand what your data looks like and what output you are trying to get to.

@chapman I think we can get this to work if you can add a running total column to your dataflow. If you are using ETL2.0 than you can copy and paste the code below to show you an example.…

@chapman - I'm not sure that I understand your sell-through table. For 2/21 you show that store A sold through 2% of its inventory (1/50) and Store B sold 0% (0/60). However, for All Stores you say 2%... shouldn't the calculation be (1/110)? 0.9%

I agree, this makes some of the date ranges on cards appear confusing. For example, to show the last "7 days" of sales data, we make a card titled "Sales: Last 7 Days" but have to select the date range for last 8 days and then write a filter that removes the current day. Calling out Last 7 Days in the title and then having…

Don't forget that you can use FIXED to allow the calculation to ignore filtered fields as well. I don't believe that is doable with partitioning. I do think we could all benefit from more understanding around what FIXED is compared to WINDOW functions and when/why to use one over the other.

I'm not sure that you could create a filter for Rolling 15, 30, and 60 days all using the same beastmode. The issue would be that if you selected "Rolling 60 Days" then nothing from the rolling 30 or rolling 15 days would get through the filter. I think @MichelleH is on the right track with recommending filter views.

That's correct, the file upload feature is a static datasource. You would need to manually update the file anytime new data was needed. If you are looking for regularly updating a shared file... we have used a sharepoint connector or onedrive connector in those scenarios.

I find that the Excel Plug in is not very flexible. My recommendation would be to use the file upload option from Domo instead.

If you are only looking to add YTD, you could add that as an extra field in your dataflow when you combine the fiscal calendar information. Something like: YTD CASE WHEN `FiscalYear`=2022 and `DateField`<=CURDATE() THEN 'TRUE' ELSE 'FALSE' END You would need to change the 2022 value when the year turned over. This would…

I'm not aware of anyway to change Hover Text based on the series or metric being pointed at. This sounds like a feature request to me.

@MarkSnodgrass - This is one of those times that I wish Domo's documentation kept up with Domo's updates. There is no SPLIT_PART() function listed in the beastmode function list, but it definitely works! I was just able to clean up some really nasty substring() beastmodes :)

@major_ace - the MOD() function is not the same as dividing two values. But, as long as you have the output you are looking for.

Is your data clean? Meaning do you have values for all of your rows of data and are those values all in number format? That error message might indicate that Domo is trying to run a calculation on a text field. If the data is clean, you could try MOD(sum(`ProdSales`),sum(`SvcsSales`))

Hi @LiliRestrepo You have to add the target="_blank" tag CONCAT('<a href="https://na132.salesforce.com/', `field_ID`, '" target="_blank"></a>')

Any updates for this?

I think you have to be careful with this. What happens if the same dataflow has multiple output datasets that might be tagged differently. For example, one dataset may be for Finance while the other is for the Sales org... even though both come from the same dataflow.

I would encourage you to explore some of the other transform tools that Domo offers. Not all problems can be solved with the same tool. In this case, if you join the data with either an ETL or SQL dataflow, you will have much more control over the join. The join mechanic for dataset views is meant for very simple joins.

@Jones01 - I believe that dataset views are also not materialized datasets. Meaning that for each card on your dashboard, Domo is first performing the joins and then rendering the visual. If you are noticing performance issues, I might suggest joining the data in an ETL or SQL dataflow first. Alternatively, you could reach…

I might also add that it would be nice if there were also a message before any changes to the card could be saved. Something like "The changes made will impact multiple locations where this card is used". If possible, even list the different pages that the card is on.

@GabrielaCortes You could probably also just use two filters. First bring the "column A" field into the filters and select "exclude" then select "False" or whatever value you want removed. Then bring "column B" into the filters section and select "include" then select "False". That would essentially mimic the beastmode…

I think that you can accomplish this by combining the sort field and the Limit Rows field. (note that the summary number will still include all of the data though). The trick is that you need to know how many rows of data are going to make up the 3 groups that you are looking for, in this case 9 rows.

I think that you would need to restructure your data. If you had something like this: Then you could create some filter cards for each of the ServiceNames. If you wanted only entities with both service A and C, then you would filter for `ServiceName A` = 'x' and `ServiceName C` = 'x'