MarkSnodgrass Coach

I would use the NOT IN condition, which would look like this for you: `domain_2` NOT IN ('url1','url2') Replace url1 and url2 with your actual values. This would exclude these values and include any others.

I have not seen that happen before. In fact, the Magic ETL joins tend to be very exact, including be case-sensitive. I would try making a new ETL and trying to do the join again. Also, to be clear, LEFT JOIN will include all records from the left table and any matching entries from the right table. INNER JOIN will only…

It sounds like you are wanting the card data and not the card definition, which you can get my choosing Send/Export and choosing CSV. To do that via API, I would suggest watching the network traffic using the Inspect option when you click those options on the card and see what APIs they call.

One option is to leverage the zoom capabilities, where you click and drag your mouse around the months you want to zoom into, such as the last two months. You can even start it zoomed in when you are in Analyzer, and then the user can click the arrow to zoom back out. This should keep your running totals in tact. I could…

I have seen some old posts in the Dojo about being able to add [yyyy-mm-dd] as dynamic variable in the file name, but I don't see any documentation for it in the knowledgebase and I can't make that work in my Workbench. Another option to consider would be to use the CLI Tool. This would give you the option to potentially…

Odd. I tested it in my instance with some sample data and it came out looking good.

I would create this for a beast mode and then add this to your sorting: MONTH(`dt`) + (YEAR(dt)/10000) This will make your dates become numbers with decimals where the year is to the right of the decimal place and the month is to the left of the decimal place.

@kofagerburg you might consider using the comparative fill gauge to show this difference. It has the ability to compare the difference between two different fields, which is what you are wanting to do. Here's the KB article for it. https://domohelp.domo.com/hc/en-us/articles/360042924414-Comparative-Fill-Gauge

You could look into using a non-period over period card type and building out your period comparisons using something like this: https://dojo.domo.com/discussion/53481/a-more-flexible-way-to-do-period-over-period-comparisons#latest You might also consider building up the numbers in an ETL.

To my knowledge, period over period cards don't have that functionality. You could add a quick filter of your list of locations and then the user could select which location they want to view as a way to accomplish what you want to do.

I would suggest looking at the Domo Excel plug-in, which is available under Admin - More - Tool Downloads. You should be able to do it with that. Here's the link to the KB Article. https://domohelp.domo.com/hc/en-us/articles/360043437933-Using-the-Domo-Excel-Plugin

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