MichelleH Coach

@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`)

@Anna_Otake You're definitely on the right track. The only changes I recommend are moving the COUNT outside the case statement and removing the ELSE 0 clause. Your formulas should all be formatted like this: count(case when `FY Order` = 0 then `cm_pla` end)

@renee12345 I would suggest using a dataflow to group your data by week and name. In the same group by tile add a distinct count of Status. Whenever the distinct count equals 2, then that indicates that that person's status changed within that same week.

@domoexpert You can try using MAX(`DateField`) instead of CURRENT_DATE() in the beast mode, though it's possible the Max Date could change if you apply filters to the card. I have also found that using an aggregate (MAX) inside another aggregate (SUM) is less reliable in beast mode

@domoexpert Yes, you could do that. In that case I'd recommend creating a "Max Date" column in your dataset using the Group by ETL tile to use instead of CURRENT_DATE()

@domoexpert You can accomplish this using a case statement within an aggregate for each value in your calculation. It should look something like this: (sum(case when LAST_DAY(`DateField`) = LAST_DAY(CURRENT_DATE()) then `ValueField` end) - sum(case when LAST_DAY(`DateField`) = LAST_DAY(DATE_SUB(CURRENT_DATE(),interval 1…

@NathanDorsch Do you have your date range set to graph by "Day" or by "None"?

@jakebutterfield If you want to show the totals for each year, add a beast mode using the formula YEAR(`Date`) to extract the year from the date column. Then add that new beast mode to the pivot table in your second image in the rows in front of Date. The pivot table will add subtotals by year once you do this.

@Rupak Instead of using a fixed function, you can add a case statement within your sums to find the current year totals like this: when sum(case when `Year` = YEAR(CURRENT_DATE()) then `Count Yes` end) / sum(case when `Year` = YEAR(CURRENT_DATE()) then `Count Overall` end) > 0.99 then 4

@muahmmad_zaidi I'm glad you got it to work! Can you please share what you did in case others have the same issue?

@muahmmad_zaidi Can you please send another screenshot of the full Analyzer view? The Series option should appear next to Y Axis

@EmmaDonery Can you share a little bit about what data you currently have available and what you want to do with it? If you need to take snapshots at particular points in time, then a recursive dataflow would likely be your bet bet. Otherwise there are some other methods you could use by categorizing and appending data…

@muahmmad_zaidi The stacked bar chart type is listed under "Bar", and is the first option listed under Popular Charts

@jakebutterfield You are correct that nulls are populating after the join because the right table has fewer unique values in the Campaign field than the Session Campaign field in the left table. Left joins return all rows from the table on the left, regardless of whether it matches any rows in the right table. If a match…

@Aag2023 What do the valid date values look like in Domo? You will likely need to use a STR_TO_DATE() function to parse it into a date field yourself

@JohnnyN In that case I would follow @ST_-Superman-_'s suggestion in trying an upsert dataset so you can bring in a rolling X number of days without duplicating.

@JohnnyN What kind of connector are you using to pull this data? If possible, I'd suggest setting the update method of your dataset to Append, then aligning your query and update schedule so that it always pulls data since the last time the dataset ran. For example, if you have your connector set to run once a day then you…