ArborRose Coach

That's too bad. And you can't go back to the source of the API code and talk to them about it?

If you're applying this Beast Mode calculation to a chart, ensure the chart type is compatible with mixed data types, as some chart types may not handle string formatting (e.g., concatenating a %) on axis values. 1. Beast Mode Calculation with Mixed Data Types If your Beast Mode calculation returns different data types…

Given a structure: { "name": ["details1"], "name": ["details2"], "name": ["details3"], "name": ["details4"] } This JSON structure is not valid because JSON keys must be unique within the same object. If your data is like this: [ {"name": "details1"}, {"name": "details2"}, {"name": "details3"}, {"name": "details4"} ] You…

If your screenshot is showing a card with a dropdown filter, the card would have the field/column at the top in items and optional group. Go to the optional group and set the format as number and uncheck the thousands separator box. Result:

1. DataFlows: Data Storage: Yes, DataFlows (which include Magic ETL, SQL DataFlows, and Python/R DataFlows) store the output datasets in the Domo cloud. When you run a DataFlow, it processes the data and outputs the result as a new dataset in Domo, which is stored in the Domo cloud. 2. SQL View (Domo): Data Storage: Yes,…

How about CASE WHEN `Churn Unit` = '% of Units' THEN CONCAT(ROUND(`Churn (%)`, 1), '%') WHEN `Churn Unit` = '# of Units' THEN ROUND(`Churn (Units)`, 0) END ROUND(Churn (%), 1): Rounds the churn percentage to one decimal place. CONCAT(ROUND(Churn (%), 1), '%'): Appends a percentage sign to the rounded percentage value to…

The issue in your JSON code seems to be the repeated "name" keys without nesting. To properly reference the data in your loop, you should ensure that each entry in the array is an object with distinct keys for "name" and "details". JSON [ {"name": "details1", "detail": "detail1"}, {"name": "details2", "detail": "detail2"},…

To compare month to a previous year's same month: sum( case when YEAR(`transaction_entry_date`) = YEAR(DATE_ADD(CURRENT_DATE(),-365)) and MONTH(`transaction_entry_date`) = MONTH(DATE_ADD(CURRENT_DATE(),-365)) and `date` <= DATE_ADD(CURRENT_DATE(),-365) then `amount` else 0 end And add a criteria such as Month(date)=1 if…

Something to ponder

It sounds like you are encountering different levels of aggregation - the left table and the right table aren't matching correctly. Make sure the tables are aggregated consistently, and that the data formatting match. If there are duplicate 'Project ID' values in the left table and not in the right table, you will get…

You probably need to search the internet for some examples of using pfilters. Here's an example of what I mean with a pfilter. In the redacted card below, I created a field with a clickable link, "Details". The link is built using a formula with CONCAT. And it looks really complex because its HTML encoded. I did not code…

Whew. That's a bunch of columns. Whether you do it through Domo's AI or externally….you can feed AI a list of column names and ask it the question. It may have a limit on how many you can give it at one time. You may need to feed it a hundred or so at a time and limit the answers down til you get what you need. Let's say I…

Domo's ability to color text in cells is pretty limited. But you can work around it. One way would be to use an HTML table with custom formatting. This thread may give some insight: https://community-forums.domo.com/main/discussion/67852/html-table-conditional-formatting I believe you can also do the following: <p…

For Net Promoter Score (NPS), you'll want to create a formula that counts the number of Promoters, Detractors, and Total Responses, and then applies the NPS formula. You should have a column that contains the net promoter scores and another one for your calculated Promoters, Passives, and Detractors. You should have your…

"Not following what you mean by bottom branch not doing anything…" Sorry, I don't see any additional columns in your screenshots. Therefore, I couldn't see it doing anything beneficial.

From what I can see, your output is already coming from your Group By path (left side of the join). Although I wouldn't put the condition the way you have it. I would compare the date only and knock off the timestamp. Your bottom branch does not appear to be doing anything.

I think we would have to see what you have in the group by. The group by paths are going to aggregate the left and right sides. Assuming what I show below in yellow is the Nov 2023 path, you would be summing the planned cost and grouping by the other fields. On the green path, you would be summing the same way. Your tiles…

Oh…and add the condition of MONTH in the same way we do YEAR to get Month over Month.

If you use formulas for dynamic years in an ETL using the Group By Tile, such as: current year: sum( case when YEAR(date) = YEAR(CURRENT_DATE()) and date <= CURRENT_DATE() and sku='Product A' then amount else 0 end ) previous year: sum( case when YEAR(date) = YEAR(DATE_ADD(CURRENT_DATE(),-365)) and date <=…

The error "Invalid alias: T2" suggests there’s an issue with how Domo is referencing or aliasing the columns in the new dataset. Make sure the column name from the new dataset exactly matches the column name you expected in the Data View. Check for leading or trailing spaces also. If you copy and paste names, copy them…

Weeks don't match year over year. You may have a year with 3 business days in a week, comparing with another year with a different number of business days.

https://community-forums.domo.com/main/discussion/comment/97781#Comment_97781 Send an email to support@Domo.com

I don't know how much control you have over it. Go to the admin settings in Domo and review your SSO configuration. There might be a setting related to automatic user creation.

I don't think pfilters work across apps currently. As of now, pfiltering does not support passing filter values directly from one app to another. This means that filters applied in one app cannot automatically be carried over to another app. But that doesn't mean you can't work around it. You could try something like…

The Domo Eloqua API connector pulls data from Eloqua using its API endpoints. When setting up the connector, you can specify which objects and fields you want to retrieve, such as contacts, campaigns, or other data. Contact Data and Opt-In Status Eloqua has different fields and attributes related to contacts, including…

To my knowledge, Domo does not natively support .avro files through its connectors. If your .avro files are stored in a cloud storage service like Azure Blob Storage or AWS S3, you can use the Blob Storage connector in Domo to access them. However, this will only allow you to access the files; you would need to process the…

I think you are going to need to contact Domo Support. I don't see any information for the publisher nor links. Please don't click this as correct answer…someone from Domo may have the information to supply here. https://domo-support.domo.com/s/article/4409676591127?language=en_US

You could create a beast mode calculation to determine whether each actual value meets the corresponding goal. CASE WHEN `Actual` >= `Goal` THEN 'Goal Met' ELSE 'Goal Not Met' END Add to your table. Apply conditional formatting with this status.

As Jones01 says, either of these should work FLOOR((DAY(`date_column`) - 1) / 7) + 1 FLOOR((DAYOFMONTH(`date_column`) - 1) / 7) + 1 Create a Table or Chart in Domo. Add the fields: YEAR(date_column) MONTH(date_column) Week Number of Month as shown Total Spend: SUM(spend_column)

The seems to be pointing to an invalid JSON response. It indicates the response might be HTML…such as when an API call returns an error message. You could try to capture what is happening by adding some error handling code. for (var i = 0; i < 1000; ++i) { var res = httprequest.get(baseUrl + "?cursor=" + Cursor); try { //…