MichelleH Coach

@AZaiter Not all instances allow window functions in beast modes. If you have not used them successfully before, then I'd suggest reaching out to your Domo account team to confirm and get them enabled.

@AZaiter Just to confirm, do you have beast mode window function enabled in your instance and have they worked for you before? Also, you will need to add the outer SUM() back to your formula since that is required for window functions in beast mode.

@AZaiter That helps to know that you want to graph by month. I suspect the issue has to do with the date granularities of your calculation and the groupings in your card. Try removing the partition portion of your beast mode, since graphing by month makes partitioning by month obsolete.

@AZaiter How are you trying to present this metric in your card?

@AZaiter It looks like you're running into the issue because you are partitioning by year. So effectively it is taking the sum over the last 12 years, not months. Try partitioning and ordering by the last day of the month like this: SUM(SUM(fieldsAccident Count)) OVER ( PARTITION BY LAST_DAY(fieldsMonth Ending Date) ORDER…

@User_32667 Possibly, I'd suggest reaching out to Support to confirm.

@User_32667 I just found the same thing on one of my cards, but was able to get the control to return by re-saving the card. Does that work for you?

@User_32667 Can you please share some screenshots of what you're seeing?

@LJ You can use a beast mode like this to filter to the times you want: case when DATE(`Alarm Received Store Time`) = CURRENT_DATE() - 1 and HOUR(`Alarm Received Store Time`) >= 6 then 'Include' when DATE(`Alarm Received Store Time`) = CURRENT_DATE() and HOUR(`Alarm Received Store Time`) < 6 then 'Include' else 'Exclude'…

@bstephan Yes, that's correct. I'd suggest creating a branch of your ETL that uses a formula tile to move the dates forward by 1 day. DATE_ADD(`DateField`,interval 1 year) Then you can rename the `Sessions` field of this branch `PY Sessions`. From there, use an Append Rows tile to merge that with the original data. Once…

@muahmmad_zaidi You will need to use another dataflow that combines the outputs of all 3 existing dataflows into a single dataset to power the Single Value card. I'd suggest using a Group by tile to replicate the summary number from each summary number, then join all the values together and use a formula tile to calculate…

@bstephan With this setup, changing the global date filter to Month to Date would exclude all of last year's data. The best way to make the YoY variances to dynamically update with the global date filters is to restructure your data in a dataflow to add a separate dataset column for prior year sessions. Then you could…

@bstephan I agree with @colemenwilson about using a beast mode column to show the % difference. Mega Table cards are actually better suited than Pivot Tables for showing variances, so you will need to use beast modes to re-create your TY and PY columns and add the variances. Current Year: SUM(case when `Year` =…

@AdamC I agree with the above recommendations to use a variable. In this case, I suggest creating a numerical variable to represent the number of days you want to compare. Then your percentage beast mode would look like this: sum(case when `Days` <= `DaysVariable` then `Shipments` else 0 end)/sum(`Shipments`) So if a user…

@emmanuel_fabre Can you please explain the business logic of the calculation? I see some opportunity to simplify your original beast mode in a way that could resolve the errors, but need more details to be able to provide input

@kav_100 You will need to include the following to the end of your query: WHERE YEAR(`DateField`) >= YEAR(CURRENT_DATE()) - 3

@M_Bianco1 Yes, you can do this with the Dataset Copy Connector

@Tsharma8724 Are you the owner of the input dataset? According to this KB Article, that you must be the owner of the dataset in order to use this connector

@emmanuel_fabre How should the percentage value behave when multiple values are selected? For example if "Clicks - CTR" = 95% and "Engagement Rate" = 50%, what should the single percentage be and what does that mean?

@emmanuel_fabre Can you please share your beast mode code and some more information about how you are using it in your card?

@Buck You can create a beast mode that's shared on the dataset and put that in the quick filters section of analyzer instead of the original dataset field name. That way you only need to change the name once.

@renee12345 Do you have an formulas in your file? Usually that happens when there is an error the excel formulas themselves

@Aag2023 For the product key, you can transform this into a date using the STR_TO_DATE() function: WEEK(STR_TO_DATE(`PRODUCT_KEY`,'%Y%m%d')) Since `ProductSale_Timestamp` is already in a datetime format, @GrantSmith's formula should already work for that.

@Kunal If your dataset does not include every date, then use Calendar report from the Domo Dimensions Connector as both @MarkSnodgrass and @GrantSmith suggest

@Aag2023 Can you please share some example values of the `PRODUCT_KEY` and `ProductSale_Timestamp` fields?

@MycahD This warning usually occurs when the dataset used to power a card has a very large amount of rows. Are your values just coming from a simple count or is there other logic you're using in this card?

@Ajita It looks like you aren't specifying what kind of join you want to do. You will need to add either LEFT, RIGHT, INNER, or FULL OUTER in front of the word JOIN.

@Ajita It looks like you aren't specifying what kind of join you want to do. You will need to add either LEFT, RIGHT, INNER, or FULL OUTER in front of the word JOIN.

Hi @Anna_Otake I'm glad that worked! If you want to count unique email types, just use COUNT(DISTINCT) instead of COUNT()

@renee12345 Do you just need a date field for your cards? If so you could use the formula below to identify the first day of the week to group by instead: `Snapshot Date` - DAYOFWEEK(`Snapshot Date`)