MichelleH Coach

I agree with @marcel_luthi I think a flex table or some other time series chart would be better for visualizing this.

@Chris_Wolman Can you provide some more information about the business case for why the starting inventory for an item that wasn't available until 5/5 would not be 0 for the period between 5/1 and 5/15?

@Chris_Wolman Typically, aggregation functions should be outside of the entire case statement in order to return a single row. However in this case the min date is also causing an issue because you would have an aggregate inside an aggregate (min inside a sum). Based on your use case, I would suggest setting up two date…

@user029082 In that case I would recommend reaching out directly to Andrea or the beta team to help you with the your specific use cases.

@user03163 You can create a beast mode like the one below that you can use a as a filter. Using the LIKE operator with the % wildcard will allow you to exclude any records that contain the specified text. In this case searching for "Dup" will also return "Duplicate". case when `Closed Description` like '%SPAM%' then…

@user029082 I suggest checking out this recording from one of the previous Lunch & Learn streams. There are some great examples and use cases for partitioning!

@MayaU_01 Can you please share some more information about your data and what the beast mode calculation represents?

@muahmmad_zaidi You can set up your % Change beast mode to calculate based off of the sums of your two fields like this: (sum(`Field1`) - sum(`Field2`))/sum(`Field2`)

I agree with @MarkSnodgrass's suggestion for the single value card. If you want to show the First Week and Second Week in the same card, then I would suggest adding the week 2 filtering inside each sum using case statements: ((sum(Case WHEN `Survey Type` = '2 Week Survey' THEN `Promoter Count` end) - sum(Case WHEN `Survey…

@MThebeau Can you please share your beast mode code so we can look into it further?

@user17188 It sounds like you're describing Smart Text. Is there something you're not able to do with this?

I agree. It would be helpful to be able to see "Direct Impact" vs "Total Impact" as separate columns in the DomoStats/Governance datasets. In our case we could use this information to more quickly prioritize dataset cleanup/migration projects.

@mroker It depends on how you are pulling the data, but most connectors should have an option to change the update method from "Replace" to "Append" so it simply adds new rows to the existing data.

@Josh_Godec123 It looks like "CARL BEAN MEN'S WELLNESS CENTER" is not specified in your case statement, so it would fall into your ELSE 0 bucket. I second @MarkSnodgrass's suggestion of using the LIKE operator to capture patterns rather than exact values.

@ccc123 Try using filter cards instead since they will adjust based off of other filters

@ccc123 Are you using a filter card or the dashboard filters on the top panel (near filter views)? Filter cards react to other filters, whereas the dashboard filters do not.

Congrats @colemenwilson! Also shout out to @GrantSmith for reaching 10,000 points on the Community Forum!

@NathanDorsch It might also be worth copying the top and bottom flows from your screenshot into two separate test dataflows. If one runs successfully and the other doesn't that could help narrow down where the issue is. If they both run successfully, try reverting to a previous version of the original dataflow and re-do…

@nmizzell A beast mode calculation would be your best bet since the calculation will update based on whatever filters are selected. The formula should look something like this: sum(`Revenue`)/count(distinct `Date`)

@ScottLeeds To count the whether the completion date was 7-14 days ago, you can add a second condition to your case statement like this: case when `Completion Date` >= CURRENT_DATE() - 14 AND `Completion Date` < CURRENT_DATE() - 7 then 1 else 0 end

@SaskiaV Add a formula tile to the beginning of your dataflow to only accept values that are not equal to ERROR 42 like this: case when `Field` <> 'ERROR 42' then `Field` end

@ScottLeeds Yes, you can use a rolling 7 days approach like this: case when `Completion Date` >= CURRENT_DATE() - 7 then 1 else 0 end

@Mickey You can hide the "Grand Total" label by adding "<br>" in the Label under "Total Row"

@ScottLeeds You can create a numeric field that you can sum through either a beast mode or ETL formula tile like this: case when `Completion Date` >= '2023-06-12' and `Completion Date` <= '2023-06-16' then 1 else 0 end

@damen The Lag function should be used to add a column to hold the prior quarter expenses. In your first screenshot, name your new column "Previous Quarter Expenses" (or something similar), change the function drop-down to "Lag", run the function on your current quarter expense column, with an offset of 1. Once you've…

@renee12345 You can use a Group by tile on the data that includes Name to find the First Non-Null value for Name by ID. Then join that to the data without name on ID to fill in the Name column before appending.

@damen When you use the Rank and Tile column to find the expenses from the previous quarter, be sure to partition by project to make sure you are only including previous quarter data for the same project.

@Rupak I second @colemenwilson's recommendation of recreating the fields. I would do this in MagicETL using the Formula Tile. If you don't want to specify every value to swap, you could use a regular expression to match patterns based on whether `Number` contains alpha characters and `City` contains numeric characters.…

@NateBI It looks like you're on the right track. You should be able to add a color rule to your card based on the Rank field to add a color when Rank is greater than or equal to 8.

@muahmmad_zaidi It looks like @marcel_luthi and @jguzman answered a similar question to this earlier this week. Take a look and see if this applies to what you're looking for