MarkSnodgrass Coach

@nshively Understood. I'm sure @GrantSmith will come up with a very elaborate beast mode for you. You can whatever you are potentially slicing by into your group by and rank and window tile and then save the final formula tile work that calculates the average headcount for your beast mode. I have done this multiple times…

I would suggest creating an ETL that groups the data by month/year and sums the employee count and term count. You can then add a rank and window tile and use the lag function to get the total employee count for the previous month as a column right next to the current month. Next, add a formula tile to add your current and…

I agree that this should be an option. In your column label, you can add a \\n to force a new line between words. Not sure that will help you get your text consistently aligned, but thought I would point it out as it is not well documented.

I would create an ETL that splits your data into two using two filter tiles. One filter where userid is null, which is your pre-authenticated data, the other where userid is not null is your authenticated data. You can add a constant tile to create a column called authtentication status. You can then use a join tile to…

What columns are currently in your dataset? I'm having trouble picturing what your data looks like. Do you have one row per month right now? If you can explain a bit more what your data looks like, it will be easier to suggest a solution.

Whenever I am needing to show a goal, I tend to use the Bullet Chart, so I would suggest looking at that for your visualization. https://domohelp.domo.com/hc/en-us/articles/360042924154-Bullet-Chart As for the data, I would start with adding a group by to total your orders by datetime, so that you have one row for each…

If you are using a dataflow, you can click on the settings tab and set the frequency of the refresh rate by choosing On a Schedule and then select the appropriate options. If the card is tied to directly to a dataset that comes from outside of Domo, you can build a basic dataflow that just has an input and output and then…

Depending on how many exceptions you have, it's easy to just add a case statement into the process so it would leave it alone if the group was AD Group: All Users. Something like this: CASE WHEN `String` = 'AD Group: All Users' THEN `String` ELSE split_part(`String`,'-',1) END You could add additional when statements if…

It looks as though you want anything before the colon to be your new field. You can use the SPLIT_PART function to extract this: split_part(`String`,':',1) This will take everything before the colon and ignore everything else.

That is correct @jaeW_at_Onyx , but can be accomplished by getting a distinct list of employees and add another join in the process. Your denominator suggestion would require the same work. It would look something like this. The Domo Calendar data would be on the left side of the left joins and your 2nd join would need to…

@rishi_patel301 the steps are a little tricky, but you will end up with just one dataset once your done. I would review the steps again as you shouldn't end up with two datasets.

It sounds like you are wanting to leverage recursive dataflows. I would recommend looking at this KB article which will walk you through how to set it up. https://domohelp.domo.com/hc/en-us/articles/360057087393-Creating-a-Recursive-Snapshot-DataFlow-in-the-New-Magic-ETL

@pstrand2 I would recommend my previous suggestion of using the Domo Dimensions Connector and the calendar dataset to pull in a complete list of dates and then do a left join to your dataset in Magic ETL and use the formula tile to indicate the working vs non-working days as 0 or 1 and the calls activity as 0 or 1. This…

You can use Buzz when viewing a card to @ mention someone to get them to look at a card. https://domohelp.domo.com/hc/en-us/articles/360042925574-Chatting-in-Buzz

I think this can be done much cleaner if you do some of this work in Magic ETL. You can use the Domo Date Dimensions dataset to create a row for every day of the year and then join it to your data. Then you can create an integer field called IsWorkingDay with a value of 1 or 0. You can use the DayOfWeek function in the…

Are you just grouping by using the date range filter? If you add the month or the quarter to the actual display of the pivot table, it should calculate better.

This is where I would turn to using Magic ETL. You can use the Rank & Window tile to easily do the Lag and partitions. You could also join it again itself to create a list of sales people and list of years so that there are no gaps, and then do the rank and window work.

You can utilize the LAG function in a beast mode to do this without building an ETL. You need to make sure you have Window Functions in Beast Modes enabled. Your CSM can enable it if it isn't. To calculate the difference you would do something like this: LAG(SUM(`sales`)) OVER (ORDER by `Year`) - SUM(sales)

It's also worth pointing that sometimes you can achieve the same look by using the mega table, which will give you the option to just check a box to get percent of total instead of having to write a beast mode. This will depend on how you are wanting to present the data, but is worth looking into.

Here's a screenshot of a dynamic textbox card in a dashboard if this helps:

Interesting. I use the dynamic textbox card to display this type of information on a dashboard and it doesn't do the dotted underline. I don't have a notebook card in a dashboard to compare against at the moment, but you could try the dynamic textbox card as an alternative.

You shouldn't need to do any ETL or beast mode work for this. If using a table card, for example, drag in all 3 columns into your column listing. Click the pencil next to sales total and choose aggregation of Sum. In the date range filter, choose group by year. This should give you the sales totals for each client for each…

I don't see it in the appstore, and the KB articles lead me to believe it might need to be enabled by your CSM or support. I would start by asking your CSM to see if it needs to be enabled. If you are an admin, you can also go to Admin and Pages and make sure there are no pages listed as Business in a Box and it is just…

I have not seen that before. Are you sure that isn't a browser extension causing that? Is this on a specific card type? I would first try a different browser and see if it is still there.

There doesn't appear to be a connector for NCR. However, Domo provides a lot of different methods to ingest data. If NCR has an API, you could write your own custom connector. You could utilize the Dataset via e-mail connector if it can send data to an e-mail address. The CSV Advanced Connector and is useful for ingesting…

@jaeW_at_Onyx often recommends appending your data so that you have one larger dataset and allows you to easily perform drill paths. I would encourage you to look at the videos he has posted as there is likely one that covers this: https://www.youtube.com/c/OnyxReporting_2

@moneyshot that makes sense. Domo needs to add the divergent color chart properties to the standard table card and not limit it to the heat map card. That would get you what you need.

It's available on the Heat Map card and the Map card. You can find it under Chart Properties -> Diverging This KB article gives a breakdown on each property. https://domohelp.domo.com/hc/en-us/articles/360042924634

You are going to need to utilize some rank and window functions to determine if you have 3 or more consecutive dates. I would recommend using Magic ETL and the Rank & Window tile. You would use the Lag function to check for consecutive days for starters.

Agree with this and there have been other Idea Exchange posts with the same suggestion, but you can't vote them up anymore. See this similar one as an example: https://dojo.domo.com/discussion/21844/beast-mode-number-format-function Would be extremely helpful to be able to call a Format_Currency function for example to…