MichelleH Coach

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

@Matt_DAlto Can you please share the other settings you have configured on the job? The error appears to be related to mis-aligned ranges, not necessarily nulls

@ncelis Try changing the double quotes to single quotes around 'Active' and 'Unpaid Leave'. Domo expects string fields to have be surrounded by single quotes.

@SayyedHussain This tends to happen if a (non beast mode) field with the same name has been added to the dataset. Do you know if a field has been added to an upstream dataset that the datasets you're using may have inherited?

@ncelis It looks like you're not using the correct syntax for the count distinct function. The word "Distinct" needs to be inside the parenthesis like below: COUNT(DISTINCT CASE WHEN (Team Member status = 'Active' OR Team Member status = 'Unpaid Leave') AND Date BETWEEN 'start_date' AND 'end_date' THEN Team Member ID END)…

@learnDomo By forcing null values to 0, the stages with nulls are likely being converted to an integer. Try changing the 0 to a blank string ''.

@learnDomo Can you please share all your beast modes for the various stages? Also, do you have formatting applied to any of the columns in your table?

@deona720 I suggest using the Dynamic Unpivot column in MagicETL to accomplish this. You can read more about how the tile works here: Edit: Grant beat me to it!

@DeclanCPS What fields do you have available in your dataset?

@DeclanCPS Is there a column in your dataset that indicates whether they have accounts in the previous question? If so, try adding that column as a filter in your card so that you don't have to change a beast mode calculation.

@CR123 It appears to be listed as "Coordinated Universal Time" in the time zone drop-down under "Formatting"

Hey fellow Cincinnatian! I was wondering about your Musketeer avatar

@yogesh_1 Is Fiscal Year a column in your dataset or are you using the native date range selector in the card/dashboard? If you don't already, I would look into setting up a Fiscal Calendar on your instance.

@Charlie Bantoft Total rows and columns will use the same aggregation as the "Values" field by default. In other words if the other values are being summed, then your totals will also be using a sum. You could try swapping a beast mode with a fixed function into the values field like this: avg(sum(`value_field`) fixed (by…

@jtrollinger Since you're using two beast modes with different definitions it's not realistic to expect them to match. Unless they were written using assumptions specific to your business, they don't seem to be comparable.

@jtrollinger Can you please share some more details on how your cards are set up? It's difficult to give suggestions without understanding your data

Number 7 is too real…

@jtrollinger Total rows calculate based off of values in the source dataset, not the aggregated values in the table rows. In this case it means that there were 47 unique values in the SalesOrderNo field, some which have records for multiple Assigned Plumbers.