MichelleH Coach

@chetan_cricut The error is likely because of the COUNT(DISTINCT ) in your order by clause. I've often seen beast mode errors when using aggregates inside of other aggregate/window functions. Are you able to hard-code that count using ETL?

@gbrown I would suggest changing the format of the other dataset using the Dynamic Unpivot tile in MagicETL instead, if possible. You will have significantly more flexibility with the dataset when it is not already pivoted.

@gbrown You should be able to use your existing data as-is in a table card, and select the Transpose Columns option to put it in the desired format.

@hunter_brown To answer your question, what you are describing should work in beast mode. What are you getting instead?

@hunter_brown Is this data time-bound? If so, could you not link your datasets by month?

@hunter_brown Be sure to use ` around your column names instead of an apostrophe so that it knows you are referencing a column. They way you have it now, Domo thinks you are trying to perform a mathematical operation on strings

@zaclingen_zips This sounds like a mis-alignment with your instance time zone from your company settings. Does the dataflow produce any different results if you set the time zone in the Dataflow Transform settings instead? Here is a Knowledge base article about troubleshooting time zones in Domo:

@mroker This sounds like a timezone mismatch between your Domo instance and the source data. You will likely have to add a Timezone conversion transformation to your workbench job to match the timezone of your Domo instance.

@Pau I don't think a free-standing legend is an option, but I would suggest setting the same color rules on all 3 cards and hiding the legend on all but one of them so it doesn't have to repeat.

@jtrollinger What type of aggregation/subtotal are you using on that column in the card? It looks like it might be set to MAX instead of SUM. As @colemenwilson mentioned, I don't see anything obvious in your Group by tile that would cause it to display that way.

As others have mentioned, I definitely agree with going back to in person and showcasing the "How". It would also be helpful to have a session on how to solve the most frequently asked problems that users ask about in the Community Forum.

@ArborRose Instead of Value Mapper you could just put that exact case statement into a Formula tile to give you more flexibility.

This is great, thanks for sharing @AnnaYardley!

DONE

@Domomon It sounds like you could use variables for this, though that likely depends on the details of your specific use case.

@domoexpert I'd suggest using a Variance Trendline card under the Period Over Period chart types, though note that these types of charts do not offer much customization

@dkonig If you are using MagicETL you can use the Split Column tile to separate a column based on a particular delimiter, in this case the pipe character. You can also do this using the SPLIT_PART function in a formula tile. Edit: @colemenwilson beat me to it!

@SayyedHussain If you want to only include months to date you can add a beast mode filter like the one below: case when MONTH(`Date`) <= MONTH(CURRENT_DATE()) then 'Include' else 'Exclude' end

@SayyedHussain You can accomplish this with a pivot table card with MONTHNAME(`Date`) and YEAR(`Date`) as your columns and rows, respectively, and `Metric` as your values. You can also use MONTH(`Date`) to sort your months chronologically

You could use a beast mode like the one below to sum the file collected if the date field is one or two days before today: sum(case when DATE(`local_collect_date_time`) = CURRENT_DATE() - 1 then `FilesCollected` else 0 end) - sum(case when DATE(`local_collect_date_time`) = CURRENT_DATE() - 2 then `FilesCollected` else 0…

@Zel Can you please share some example data to demonstrate the behavior you want to see?

@MThebeau I would recommend restructuring your formula so that @colemenwilson's case statement resides within the denominator sum to ensure that all your conditions have the same granularity. Also MagicETL actually has a function in formula editor called DATE_WORKING_DIFF that calculates number of working days between two…

@Zel Start with this KB Article to point you in the right direction!

@Zel It sounds like you will need to set up a variable control for Customer (instead of a filter card) so that you can add conditions to your case statement based on the selected value.

@Zel Yes, you can create a beast mode filter to exclude the current day like this: case when `Date` = CURRENT_DATE() then 'Exclude' else 'Include' end

@Stucker Does it still have the same behavior if you remove the sorting?

@Stucker Can you please share your beast modes and sorting?

@Stucker Does your table have subtotals or any aggregated columns?

@Jordantm Have the credentials for the account changed? If so, can you confirm that that Box account has the same access as the previous one?

@Aaron_w_SMG Have you validated that all there are records in your data that meet the criteria for all the filters?