ST_Superman Coach and Domo Employee

Hi @Utz I think the delayed load times could be due to the way that you have your filter cards set up. Try editing the filter cards and adding the optional group by field. I tend to use the same field as my Items value and just aggregate by COUNT:

Hi @art_in_sky - could you provide some more information about your data structure? Maybe provide a few rows of data (feel free to change the data, but keep the schema consistent). This would help get an answer to your question.

This has been brought up before. Can we merge these topics? @AnnaYardley Also, can we get an update? Because this is a great idea!

Congratulations @DavidChurchman !

When you add a window function to the filter section, you will need to make sure that you partition by everything that is getting partitioned in the table or graph. For example, it looks like you have two fields, "SUB_CATEGORY_TXT" and "Manufacturers" in the table, but you are only partitioning your calculated field by the…

This would be useful for all filter card types.

@John689 Is that different than this Lock Page option?

Thanks @MichelleH Unfortunately, every time that I try to create a card from this dataset, I see the same error where I cannot click on the save button. I'm going to open a ticket.

@bperry30 It would be a group by tile in the ETL. (Group by Store and Item and sum the Retail field) You could probably do this with a calculated field as well. Something like: SUM(SUM(`Retail`) FIXED (BY `Store`, `Item`))

@afieweger Can you share the settings that you have in the analyzer? The columns being used and the sorting?

@bperry30 Could you just SUM the Retail field by store and item and then filter your results to show items where the sum is not 0?

You could add a case statement Case when curdate() > End Date then 1 else … end where the … is your formula from above

@NateBI Here is a tutorial put together by @MarkSnodgrass with filling in missing dates.

Ah. In this case you will need to join your data to a calendar dataset so that you get at least one row of data for every individual. This will allow Domo to find values for any combination of dates, even if there is no data originally present. This has been written up in other solutions as well, I'm pretty sure there may…

@NateBI Would there be a use case where a user would apply a date filter that would cut in the middle of a week? If not, you could create your null filter per user by week. This way there would be a flag in your dataset to indicate each week where a user had a null value.

@ValentinaSav I think what @ArborRose suggested is probably the issue here. It would seem that your dataset already has a field with the same name as one of your beast modes. For example, if you created a beast mode that was called Profit and then later decided to add that field during the ETL, you would expect to see this…

@deona720 Are you looking for help calculating the percent change? Or is that already part of your data and you are just looking for help building the card?

Hi @rajaparthasarathy I'm afraid that I don't understand your question. Could you clarify? Maybe add some screenshots of your issue and describe what you would like to have happen?

@SusieQ Have you looked into the Domo plugin for Power Point?

@SusieQ I would consider splitting this task over two charts in a dashboard then. Place your custom map on one side and then add a table card that lists the counties along with the value next to it.

This would depend on how your dataset is structured. Could you share some more info about your data? Is the prior year benchmark in your dataset already? Or would that need to be calculated as well? I'm pretty sure this is doable with a beastmode and a trellis category.

It sounds like the error message is saying that you can only reference a single calculated field. Because your calculated field was already referencing another calculated field you were getting the error. You have one beastmode, we will call that A. You then have another calculation, B, that references A. What the error is…

@Zel The issue that you will run into with @DavidChurchman solution is that the field will then be a text value and you will not be able to get an average. I would use something like this to get the number of seconds between the two values. You can then find the average of that numeric value. Then the issue becomes one of…

@Zel all of your Closed Dates are actually occurring prior to the open date? From your screenshot, all of the elapsed times will be negative.

@tmerchant I did this in a magic ETL. My initial dataset looked like this: I then ran the following steps in Magic ETL Dynamic Unpivot. This is used to stack all of your columns on top of each other. field number. I create two fields in this step. One to identify the id, request, and column number; and one to designate the…

That is just the chart type. It is called a sparked bar and is found in the "other charts" section:

Hi @Zel What do your input datasets look like? Also, are you wanting the ETL to calculate the Averages for you, or are you going to find the average at the card level?

@deona720 Just to be clear, using the Dynamic Unpivot tile in ETL will not quite get the results you described. You would end up with three columns: "MemberID" | "Date" | "Value" 123 23-Jan 33 You would not get 33 rows for member 123 in Jan.

@Brian_WPI My thought here is that your table card (where the field is working correctly) is displaying more fields than the bar chart. You may want to include a partition by clause in your beast mode. CASE WHEN Onboarding Date <= (MIN(MIN(Report_Date)) OVER(PARTITION BY `Place`)) THEN 'Yes' ELSE 'No' END Essentially, my…

@Abe Did you try bringing the field into the table? Or just as a filter? Try adding it to the table to see if it is calculating correctly.