ArborRose Coach

My last version didn't quite work either. But the theory still holds. If I separate the group by as shown below. The top one is getting me correct count and amount by month, store. The middle group by is getting me a correct total by year. The bottom group by is identifying the customers common to both. This gives me…

I am currently validating my numbers. I believe I have a process that is working. In the first group by, I total 2022 using GROUP_CONCAT. GROUP_CONCAT(DISTINCT CASE WHEN Year = '2022' THEN Store ELSE NULL END SEPARATOR ', ') I do the same thing in the next group by (Group By 1), totaling 2023. The output is then aggregated…

Thanks for the responses. Regarding the first suggestion, the resulting value for "In Both" results in only "out". The count is always zero. But looking at the data, I can verify there are instances that meet both conditions. @marcel, I am not familiar with LISTAGG. You say beast mode, as in a formula. But I don't know…

I'm interested if anyone has a solution. I asked this question once in a work session with Domo but I was told titles cannot contain any type of formula or beast mode.

Your value should look like a decimal before you format as percentage. (2.2 - 2.88) / 2.88

It looks like you are trying to do YTD comparisons. I would try it something like this…. Create a formula for SUM, AVG, COUNT for Current Year (CY) and same for Previous Year (PY). Then you can throw them up on to a card to see side by side comparisons.

I create a "link" using beast mode using a formula. First I get out notepad and write out the anchor reference string as if it were written on a web page. Then write that all out as if I were passing multiple parameters in a method of something like this…. destination_url?param1=something&param2=somethingelse Then I…

I create a "link" using beast mode using a formula like shown below. First I get out notepad and write out the anchor reference string as if it were written on a web page. <a href="destination_url">What gets clicked</a> Then write that all out as if I were passing multiple parameters in a method of something like this….…

I create a "link" using beast mode using a formula like shown below. First I get out notepad and write out the anchor reference string as if it were written on a web page. <a href="destination_url">What gets clicked</a> Then write that all out as if I were passing multiple parameters in a method of something like this….…

https://community-forums.domo.com/main/discussion/comment/87377#Comment_87377 If you review the screenshot I included, you will see there are operands included. So you can create the anchor reference to say things like where value in (X, Y, Z), or where value = X or value = Y. The problem to solve is how to gather the…

Coalesce is easier to apply then IFNULL.

There's a NerdGraph connector…. https://domo-support.domo.com/s/article/000005347?language=en_US

Yes, ETL has a rank and window tile.

Mark thought he wasn't fast….gee. Better late than never right?

Done

Dynamic parameters already happen. It's up to the API on the other side. I can call my APIs and pass them a list of specific customers with comma separators in a single parameter. Or multiple offices with comma separators. As long as the other side can understand it…it works. What I am not sure, is how I would expect to…

https://community-forums.domo.com/main/discussion/comment/86954#Comment_86954 Using the filter tile. When you review Domo's recursion example, they set up a dataset. Then use a calculated field to filter what is kept or filtered out. You can flush previous data the same way.

Sure. You can aggregate in an ETL (group by) and send the result to a tile that appends a dataset.

Interesting idea. If I need four different date ranges, I pull four different JSON connectors and combine them into a dataset. If we had the ability to do multiple date ranges, it would significantly reduce the size of the datasets being held…and reduce the strain for Domo's storage.

As a fixed field (test)….and filter.

Using a calculation instead of the aggregate…

What is your last field doing? Seems like you should be removing that last field from the table. Then put the filter in for >=3. You would then get the list of sites with 3 or more tickets.

https://community-forums.domo.com/main/discussion/comment/86919#Comment_86919 Your TicketNbr field seems to contain things other than ticket numbers. What are the COUNT 1 / xxxxx values? When doing a condition search for a value, I often write it as {fieldname} IS NOT NULL AND {fieldname} <>'' I use this because sometimes…

A beast mode calculation might be something like the SUM(CASE WHEN TicketNbr IS NOT NULL THEN 1 ELSE 0 END) Then put that calculation into the filter where fieldname is greater than or equal to 3.

Your filter appears to be on the site name, not on the # of tickets.

You can use the rank and window tile to identify the top 5. Then set color rules.

Two solutions that don't really solve your issue but might help. Using column widths, you can set the amount of width for a column. This includes making some fake filler columns. The other way is to use html table with a setting for padding. When I was looking for border styles, I came across a post talking about removing…

Btw…those identifiers in the URL are important. They can be used in Python code to identify a dataset to export the data to a local Excel file.