MichelleH Coach

@Kyle_Russell It looks like there are some spaces in the as well. If you wrap a TRIM function around it that should work: CAST(TRIM(REPLACE(`Amount`,',','')) as DOUBLE)

@Kyle_Russell It looks like the commas are causing the numbers to be imported as strings instead of numbers. Try this formula to remove the commas and convert the datatype: CAST(REPLACE(`Amount`,',','') as DOUBLE)

@Kyle_Russell Could you send some examples of values in those columns? If there are any extra characters, like dollar signs, in the original fields you will need to remove them before you can use the alter columns tile.

@deona720 You only need to include the word CASE once within a case statement, but every CASE must be concluded with the word END. I also recommend using the LAST_DAY function (which returns the last day of the month) over the MONTH function since it also accounts for the year. Your formula should look like this: Case…

@ScottLeeds I recommend using a beast mode with the IFNULL function to default to the Pre-Lease % Summer 2024 value when present, otherwise use Pre-Lease % 2024: IFNULL(`Pre-Lease % Summer 2024`,`Pre-Lease % 2024`)

@robdmitchell There are a couple different ways you could do this in MagicETL: Date Operations Tile: Use the Difference between dates operation, with hours as the unit of measurement Formula Tile: Add a field with the following formula: DATEDIFF(`DateTimeOff`,`DateTimeOn`)*24 +…

@haihoang According to this Knowledge Base article, FIXED functions do not currently work on federated datasets. However, based on your screenshot you do not need to fix by ent_name if you are already grouping by that field in the X Axis. You can just use a sum of intDuration in the Y axis.

@Jason Is Curious Are you using the same field for the color rules in the "Series for Color" spot in Analyzer?

@Jason Is Curious How many programs do you have? Would setting Color Rules by program work for what you need?

@Viswaja Do you have any fields in the Sorting section of Analyzer?

@Mendoooza Check out the DataSet Copy Connector, which can be used to transfer data between instances

@ArborRose That's correct. The reason I mentioned the Domo Dimension Connector is that the "calendar.csv" report includes fields to indicate whether each day is a weekday or holiday, which you could use to exclude non-working days from your ranking

@ArborRose What if you used the isWeekday and isHoliday fields in the Domo Dimensions Calendar dataset to create a "Working Day of Month" dimension that you use for the X-Axis in your cards? You should be able to apply a rank window function partitioned by month and year to all the non-holiday weekdays to come up with that…

@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…