david_cunningham Coach

@GrantSmith thanks so much for sharing this! I had no idea this existed. You're the man! 😎

@LearningNinja - I'm not super familiar with the Indian numbering system, so did my best to provide a good answer for you. You may need to adapt/adjust this. This was the reference material I used. CASE WHEN LENGTH(ROUND(value)) < 6 then value WHEN LENGTH(ROUND(value)) < 8 then CONCAT(value/100000,' Lakh') WHEN…

So my recommendation would be to use the built in Fiscal Year feature offered by Domo. You can set this up by emailing your CSM and Domo Support. See the below linked support article that details the information you will need to supply. Alternatively, you could also use a date dimension dataset joined up to your base…

The easiest way to do this is in analyzer. Just "Save as". You can either name your card the same thing or something different. These 2 cards will not be linked. Alternatively, if you're wanting to do this with a dashboard, you can "Save as" the dashboard in the same way and create a duplicate copy where the cards are not…

@Patricia_Zavisky - here is how you would need to set this up to achieve 2 distinct lines. You would need to define a series for each FY goal. You could do this in either your base dataset, an ETL, or in a Beast Mode. Example below. Example output. Alternatively, you could make use of a bullet chart to avoid having to map…

@froghunter the average line should be visible as long as the axes are visible. You should be able to get the card pretty small before that happens. I know it's hard to tell the difference with these images. But one thing you could do is remove the Title, Summary, and Date Grain. This will allow you to get the card about…

The easiest way would be to use a date dimension table and a cross join (Cartesian Product). Say you have your budget dataset. You would join your date dimension table (a dataset that has a row for every day) with your budget dataset. You would then filter to where dt (the day in your date dataset is >= start_date and < =…

If you're not wanting to have a tile per column you want to detect outlier on, an option is to use the Python tile. You can create a function (or multiple) to run through columns you want to evaluate and generate everything in one tile. You can also customize how you want to define the outlier detection methodology. You…

You can achieve part of this with variables. If you set up a variable with your column names. You can then build a beast mode that references that variable. Make sure that the text matches the options you set up in your variable. Then if you use that beast mode on your card, you can let users select what they want. In the…

@MarkSnodgrass has a fantastic YouTube video on this exact topic! Check it out 😁 The video covers 30/60/90 day rolling windows, but you can adapt this to your particular requirements. Thanks Mark for creating this great video!

Not that I know of. Datetimes without a time component will always default to 12am. If you have datetimes that are not actually datetimes, I recommend converting them to a Date type column. There can be some weird timezone issues that crop up with datetimes that don't have a time component. If you really wanted to set them…

SUBSTRING_INDEX(url,'/',2)

I think 3 beast modes is your best bet case when application = 'App 2' then '' else application end case when application = 'App 2' then '' else application_role end case when application = 'App 2' then '' else client_name end

So this answer makes use of a Beast Mode provided by @JacobFolsom from 2018. Thanks Jacob! This answer is set up for a max of 9 digits. You can modify it if you need to handle more than that. An example below. Value shows the base value, formatted with commas as Domo automatically does. The next column shows the CONCAT()…

@LearningNinja you could do something like this. Use the single value for the current value, and then a beast mode for the previous and next value. A few things to keep in mind. For summary numbers with CONCAT(), you can use a <br> tag to force a new line. See how in the example the previous value and the next value are on…

The short answer to the best of my knowledge is that concat() removes formatting. However, with that being said I believe there is a way to achieve this with some logic in the beast mode based around the length of the output. Or with division and rounding. I’ll update tomorrow morning with some more specific examples once…

If you only need filters for a couple of columns, you could always just include those in your group by defintion. This would let you implement the above solution, aggregating by day, while still allowing you to filter by subscription type (or other columns you may need). Although you wouldn't have all your columns for…

It sounds like it's possible you may have ended up with more rows in your joined output dataset. The way that SUM(1) works is that it counts the number of rows in the set, so if you're getting more rows than expected it's possible that is due to the join. Do you have an ID column? If so, you could do something like…

To do that you can just use a counter column or create a beast mode. For example SUM(1) You would use this in place of Action in the Value section of the Pivot table. You'd then want to include the Action dimension as a row in the your pivot table. You can either put it above Recruiter or below. Above will show all Actions…

@rahulrampa the answer provided by @MichelleH is exactly spot on, and should be accepted as the correct answer. I just wanted to provide a little more detail on what she is suggesting for your convenience. You can see this is now sorted alphabetically.

@kim_barragan0126 can you provide a little more detail on what exactly you are trying to accomplish? I'd be happy to try and help you out. You can aggregate dimensions (see image) This shows a count of date by day

@LearningNinja You can do this in a beast mode. case when COUNT(DISTINCT name)=1 then name else 'All' end Then use that beast mode in your card. You can replace the word "All" with whatever your desired default value is. For example - No Name selected… Name selected…

@SherryR - love this idea! Upvote from me for sure. Would help to really understand how people are using/viewing/interacting with the data to make decisions on what to keep/remove.

Happy to help @joshnoyes , let me know if you would like any assistance with troubleshooting the error and getting the ETL to run 😁

If you create a beast mode using a window function, you can get the latest available data. CASE WHEN ScheduleDate = MAX(ScheduleDate) over () then 'Latest Data' else ScheduleDate end This will make the latest data show as "Latest Data" and all other data show as the date. You can then set your default to "Latest Data"

I took a look at the connectors you mentioned. For the Xero and Xero Payroll Connectors, it looks like you'll just need the email address and password associated with your Xero account. If you click the orange "connect" button, it will prompt you to sign-in with your account. From there you'll be able to set up the…

I took a quick look at your API documentation to confirm that it's structured in JSON. Looks like you have the option for both JSON and XML. Domo also has connectors for both of these. For JSON, you have a bunch of different options depending on your particular set-up, authentication needs, etc. There are a couple of great…

@joshnoyes - you may have already tried this, but wanted to share in case you aren't aware. If you got to the history tab of a dataflow, you can access a more detailed view of the ETL execution. From there, you should be able to access more details about what caused the failure. If using a python tile, I highly recommend…

@AO3 as long as there is only 1 CreativeName per week (or whatever your date grain is), you don't have to do anything special. Since you are aggregating Inquiries, Core Leads, etc. You can simply include CreativeName as a column and the card will do the grouping to display a single value. You can then just transpose the…

@Cara, the answer provided by @JedP is excellent and thorough. I'd just like to add on one bit that I think is helpful. It's very important to think about where you're applying the aggregation context with case statements, and the order of operations when processing the beast mode. case when Department = 'Finance' and…