MichelleH Coach

@scpradhan You could use a variable for "Number of Days" instead of using the date range filter, then you could reference that variable in the beast mode that @ArborRose suggested

@JakeWright Does your dataset include a date column for the first day of the week? If so, I would recommend using an Unpivot tile in MagicETL to turn your day of week columns into separate rows. Then you can use a formula tile to derive each individual date by adding a certain number of days to the Week Start Date based on…

@shreeyab The issue is because you are grouping your data by Day, so your calculation only includes orders from that particular day. Just so I understand your requirements, what should a weekly average by day represent? Is this the week to date average, rolling 7 day average, or overall average (including future dates)?

@shreeyab Can you please show some screenshots or examples of the incorrect results?

@shreeyab If your data is already grouped by day, then you can change the numerator to SUM(`Orders`)

@shreeyab This largely depends on how your data is structured, but assuming you have one row per order you can use a beast mode like this and group by week: count(`Order`)/count(distinct `Order Date`)

I agree with @marcel_luthi that the issue is likely caused by the nested aggregation and that it would be helpful to see a sample of the data. I'd also suggest summarizing the logic you used to create the beast mode in words so we can point you in the right direction.

@SayyedHussain I'd suggest checking out the New Product Features page to see which new features may be valuable to you. It looks like there were some new chart types and bricks that became available in last month's release.

@ColinHaze You can visualize routes with 3 legs on a route map by structuring your data to include one row per leg with lat/long like this: Point A to Point B Point B to Point C Point C to Point A Then add a beast mode with your lat/long variables like this: Latitude: case when `Point` = 'A' then `Point_A_Lat_Variable`…

@ConstelliumShawn It looks like your first CASE statement was the only one grouped inside the SUM. Rather than using separate CASE statements for each value of Material Description, you can structure your denominator to use a single CASE statement with each condition separated by WHEN… THEN… like this: SUM(CASE WHEN…

@Byboth Yes, Domo supports SQL dataflows in MySQL and Redshift: That said, MagicETL runs much more efficiently than SQL dataflow because it can execute steps simultaneously whereas SQL transforms must be run sequentially. As someone who was also more comfortable with SQL I've found that switching to MagicETL has been well…

@Byboth The DomoStats connector has a Buzz report. Here is an article about the DomoStats connector:

@pauljames You can do this by concatenating the month and year into a date format, then using the STR_TO_DATE function to convert it into a date field. STR_TO_DATE(CONCAT(`Month`,' 1, ',`Year`),'%M %d, %Y')

@mroker Can you please show what the results look like?

@mroker I'd suggest using a pivot table chart with Island in the rows, Date in the columns, and Count in the values

@Jones01 Can you send a screenshot of how your tooltip is configured?

@Stu5677 Since your TALK TIME column is already in a time format, I'd suggest using the TIME_TO_SEC function to convert that duration into seconds, divide the number of seconds by the CALL ID count, then use the SEC_TO_TIME function to convert those seconds back into a time format like this: SEC_TO_TIME(TIME_TO_SEC(`TALK…

@damen What connector are you trying to use? The File Upload connector can handle files up to 250 MB, so a 6 MB file should not be a problem

@newbie123 You use a case statement to check whether the order date field is null like this: case when `order date` is null then 'incomplete' else 'complete' end

@Liv_Stearns When trying to match multiple patterns, you will need to repeat the LIKE statement each time. So instead of this: When (`model` LIKE '%250%' OR '%2500%' OR '%350%' OR '%3500%') THEN 110 You will need to structure your conditions like this: When (`model` LIKE '%250%' OR `model` LIKE '%2500%' OR `model` LIKE…

@ColinHaze Do you have either of these options set to something besides the default?

@rmbourne I would recommend using the INSTR function instead of having to check every possible split like this: case when INSTR(`enter_account_ids`,`account_id`) > 0 then `account_id` end

@BSovers Yes, Domo is listed as the publisher in the Appstore. You can read more about the connector here:

Hi @ColinHaze there is also a setting in Bar/Line charts to create running totals under General > Number of Running Total Lines (Bars)

@BSovers It has not been removed, but it is a report in the Domo Governance Connector, not DomoStats.

@Canio I have used outer joins in Magic before. What challenges have you had with them?

@Marie_Serrano Each row/column combination used in a card are treated as a "row" from the perspective of the Limit Rows function. If you are using both rows and columns in a pivot table, then I suggest adding a Rank column in the MagicETL using the Rank & Window tile and filtering by that rank instead. The only drawback of…

@Canio Coalesce is very helpful for null handling, but it cannot add new rows to your data. Some chart types (like bar charts) have an option to fill in missing dates if a date field is used in the X axis. Otherwise, you will need to create a separate period mapping dataset to join or append in a dataflow and add the…

@Marie_Serrano Your logic is sound, but it is likely not working because Domo does not allow you to filter by beast modes that use window functions. I suggest sorting your card by COUNT(DISTINCT `SHIPMENT_NUMBER__TKNUM`) and using the Limit Rows function in Analyzer to only show the top 10

@ST_-Superman-_ I've run into this a few times before. I have been able to resolve it by clicking the X to close Analyzer and it will work when I re-open it. Unfortunately, your changes will not be saved and you will have to redo it.