GrantSmith Coach

Hi @Joe_M The tool tip fields allow you to put additional information into your hover text or data labels without having to generate a new beast mode to display all of the information that you need. You can refer to them in the analyzer settings as %_TOOLTIP1/2/3 etc

What is your beast mode you're using to calculate the percentage? Are you able to use a Magic ETL to pivot your data, calculate the percentage and then display the resulting data using a regular table instead of a Pivot?

Hi @Crisocir It's the number of blue cylinders displayed on the warehouse infographic. Each one represents a dataflow grouped by the types of inputs so you may have one for ODBC / Dataset via Email or Gooogle Analytics / WebForm etc. It's just grouping them by the unique input types for the dataflows.

Glad this worked out for you @Rvannoy . Can you make sure to accept the answer so that others can more easily find this in the future?

Glad this worked for you @Emma. Can you make sure to accept the answer so it's easier for others to find in the future? Thanks.

Hi @Emma You can use the COALESCE function to default a null value to a specific value. It does this by selecting the first non-null value in the list of parameters given COALESCE(`Total Stock`,0)+COALESCE(`Total QTY to be delivered`,0)-COALESCE(`Total fcst QTY`,0)-COALESCE(`Total Reqmt QTY`,0) If you use simple arithmetic…

Hi @simontarry76 You need to pass in the authentication headers. You can either do this an API/Developer token (More - Admin - Authentication - Access tokens). You'd need to pass in the header value X-Domo-Developer-Token: {TOKEN_VALUE} Alternatively you can do this also with a client ID and secret from developer.domo.com

Thanks @MarkSnodgrass I left out the greater than and less than because it kept auto formatting it as a quote and forgot to put them back in.

Hi @Rvannoy You can't dynamically configure the date selector to go 4 weeks back and 4 weeks forward in the same report. You could configure the card to have a beast mode such that it will compare the date to now - 4 weeks and now + 4 weeks and then return to include it or not. CASE WHEN `date_field` = CURRENT_DATE() -…

HI @Rvannoy You'll need to have data for those weeks in your dataset in order for Domo to pick them up. What I recommend is using the Domo Dimensions connector - Calendar dataset and left join your dataset to that specific one on a daily basis - then you can use a COALESCE on your field to default it to 0 for that week.…

I heard @GrantSmith will be there.

I believe the only updated data flag will only kick off the dataset copy of the origin dataset has been run after the last time the copy has run. This way it won’t keep importing the same data multiple times.

Ah, your data has some other cases than the original one. It's not capturing some of them because it's not configured in the same format. Try something like this: REGEXP_REPLACE(`Name`, '^([^,]+), (\w+)(( \w+\.)?)|( \w+)$', '$2$5 $1') Breakdown: Group 1: Last Name ^([^,]+) This captures () one or more + characters which…

You could use a regular expression in a formula tile with something like this: REGEXP_REPLACE(`Name`, '^(\w+), (\w+) ((\w+) )?\w+.*$', '$2 $4 $1')

Hi @DuncanDomo This would be an idea / feature request as it's not currently possible in the platform. Feel free to log it on the Ideas Exchange. You could follow up with your CSM just in case but the likely answer is that it's not currently an option.

Hi @user18045 DomoStats doesn't contain the amount of rows. You'll need the third party data governance connector and pull the DataSets dataset. It'll have Row Count as a coulmn for you to use.

One minor issue with the prior beast mode, it's short circuit evaluating to only pull in the 2nd digit in the months. This update version should resolve that issue: REGEXP_REPLACE(`_FILE_NAME_`, '^.*_(\d{1,2})_(\d{1,2})_(\d{4})_to_(\d{1,2})_(\d{1,2})_(\d{4}).*$', '$1/$2/$3') REGEXP_REPLACE(`_FILE_NAME_`,…

If you want the 12 month turnover rate you'll need more than 1 year worth of data. When it's attempting to do the lag for prior months and getting 12 prior records it's returning NULL. When you use + and NULL the end result is a NULL so your data is blank for all of the prior months. The beast mode should work assuming you…

It's splitting the first part of your filename 'security/public/storage/account/time/range/report/11/1/2021' as the date. This of course isn't a format that Domo can understand for a date. For more complex cases like yours I recommend using a regular expression in a formula tile: Start Date: REGEXP_REPLACE(`_FILE_NAME_`,…

Hi @Fadem You can use a case statement to conditionally sum your numbers together: SUM(CASE WHEN `Department Number` IN (1,2,3,4) THEN `Value To Sum` END)

Hi @Fadem Do you have a beast mode you're using? How is the sum function not working? For your department numbers are you looking to get a part of the department name or are you wanting to conditionally add values together based on the specific department numbers?

That's correct. If you change it to a string then you won't be able to do a lot of different mathematical aggregates like SUM, AVG etc if you convert it to a string. You'll be able to COUNT the records. This is only a display issue. You can format your field as a number when displaying it on a card and tell it to not…

Hi @CarolineRogg1 this is a display issue. You can convert the field to be a string using the alter columns tile if you want it displaying without the commas. Alternatively you can make it a string on the input dataset tile configuration

@DavidLee Can you post your exact formula you're using? Also are you doing this in a beast mode or in a magic ETL formula tile?

@Abhijith You should be able to use multiple lag functions to calculate the total and average. This is assuming your data has been unpivoted and you have a single row for each month instead of a single column for each month as in your excel document. Part 1: (LAG(SUM(`Exits in month`), 12) OVER (ORDER BY `headcount as at…

Hi @eriena You'd need to generate Grape rows with 0 as the number of pieces for each date. To do this you'd need to do a cartesian join between your dates and your products. This can cause a massive increase in the number of records you have in your dataset so be mindful it will increase the dataflow execution time as…

Hi @Hiraayub When I'm dealing with date comparisons like this I use a custom date dimension to easily define offsets like "last year". I've done a writeup on this in the past: https://dojo.domo.com/discussion/53481/a-more-flexible-way-to-do-period-over-period-comparisons#latest to get the value for the current date or the…

It's showing the thousands separator because it's a number but it likely doesn't actually have the separator in the value. It's a display enhancement to make numbers easier to read. To do a quick test you can view the data in a table card and they shouldn't show up there.

I'd recommend using a formula tile to input your CASE statements which are inside your SUM aggregation as two separate values. Then do a group by to get the SUM then another formula tile to do the outer portion of the beast mode (checking if your denominator is 0)

You're missing a single quote and a few back ticks (these designate column names). CASE WHEN `Journey-Pathway Content Progress` = 'Completed' THEN 'Completed' ELSE `Content Progress` END Doing this as a beast mode will create a second column in your dataset as that's how beast modes function. You can rename your column's…