ArborRose Coach

Not sure if this support page reference helps: https://domo-support.domo.com/s/article/360042930154?language=en_US

I am not using this connector currently, but the Domo support pages indicates need for a ClientID, obtained after registering a Workday API Client. And it should have a token endpoint. In general, a JWT (JSON Web Token) is used as a form of authentication when connecting to APIs or services, including when using connectors…

One row, regardless of the person, will only meet one side of the condition. It's a transaction like a payment. Each row belongs to a specific store in a specific year. The GROUP_CONCAT or LISTAGG creates a big list of the offices visited. When the values are aggregated the string will have each store visited within. A…

Thanks for clarifying Marcel. I tried it via the ETL. Domo didn't like the keyword so I used an alternative method to implement the same basic idea. You are correct, in the scenario I gave y'all. I didn't tell the whole story. My true data involves patients, and I need to count visits.

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

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 responses. I don't use multi-select so I haven't needed that. But here's an AI…

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…

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.

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 values are NULL, other times they are blank or empty. Which is not the same…

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.