ArborRose Coach

CASE WHEN Total_Hours_Worked >= 0 AND Total_Hours_Worked < 50 THEN '0-50' WHEN Total_Hours_Worked >= 50 AND Total_Hours_Worked < 100 THEN '50-100' WHEN Total_Hours_Worked >= 100 AND Total_Hours_Worked < 150 THEN '100-150' WHEN Total_Hours_Worked >= 150 AND Total_Hours_Worked < 200 THEN '150-200' WHEN Total_Hours_Worked >=…

Based on the error, it sounds like the data includes too many columns. But I think the number of columns may vary based on the Domo plan or configuration. It may be that there are other reasons contributing to the issue. Size of the dataset, complexity of the JSON, etc. I would suggest testing with a subset of the data to…

Taking the JSON you presented…if it were listed as a single record for 1984933, it should terminate something with parenthesis at the end like this… { "1984933": { "ListingKeyNumeric": 1984933, "ListingStatus": "Active", "ModificationTimestamp": "2024-03-08T07:32:57Z", "PropertyType": "Residential", "PropertySubType":…

The error indicates an extra character was found at the beginning of the file. Something wrong with the JSON structure. But the portion you posted looks correct. When I code my own applications with JSON calls, I something find I need the outside wrapper and sometimes I don't. You can use online JSON validators to ensure…

Instead of relying solely on the built-in "Last updated" smart text, you can create a separate card in your dashboard to display the last update time in a custom format.

Something like this? CASE WHEN MONTH(Date) = 1 THEN SUM(CASE WHEN MONTH(STR_TO_DATE(CONCAT(YEAR(Date), '-02-01'), '%Y-%m-%d')) = 2 THEN Revenue ELSE 0 END) ELSE 0 END Check for the month of "date". If it's January, then SUM the contents…which makes a date string and verifies it's month is 2 (February). If so [revenue] else…

Did you make modifications to the underlying data? Sometimes your data can affect whether subtotals display.

@hanmari - that second line should be: SELECT 2020 AS year UNION SELECT 2021 AS year UNION SELECT 2022 AS year UNION SELECT 2023 AS year UNION SELECT 2024 AS year

https://usosm.domo.com/admin/tooldownloads The link is down at the bottom and says Tool Downloads. Install Workbench on a computer that is always on and available. You can also import using pydom (Python), but there's no need when Workbench can do it well.

Use Domo Workbench to import (on schedule) Excel spreadsheets. Find the link under admin > tools.

This isn't a solution for everyone, but you could screen-scrape the status page and extract based on incident. When the code sees the DIV containing incident details, have it send you an email. Takes about 60 lines of Python code. But you would have to have it running constantly.

You need to make sure the data partition is configured correctly. And make sure the partition key accurately segments your data without omitting relevant data. One of the things I watch closely in Domo ETL processing is duplicate records affecting joins. Number of rows can easily go whack. Normally expanding not loss. With…

Use lower to change all case to lower when comparing. CASE WHEN LOWER(Event_Label) LIKE '%thd%' THEN 'Y' ELSE 'N' END

Congratulations John Le!

@shreeyab - does the data look something like this…

I submitted a request for customizable padding when I first started using Domo. Why limit padding options for only embedded dashboards. All cards and dashboards should have options for padding, border thickness and color. These were among the first things available in html.

I haven't used pivot tables as source myself, so I can't answer that. But I don't think WorkBench wouldn't care as long as you can define the area of rows & columns. Example, I screenshot this image from an online pivot table example (below). If I set WorkBench to read the whole table I would expect it to fail. But you can…

I don't have the Location.ID or TransactionDateUTC in my data sample to play with. But they look to be further quantifying the condition. I can't test this, but what about something like this….

The error indicates that there's an issue with the way you're referencing positions in your Workbench job. Make sure your fields are in the correct order and that the data structures match. Such as date formats. Oh….also make sure you have your data laid out without merged rows. All rows should lay out with specific…

Sorry….should have explained my answer. When I review the way you have the data, you only want to count the repeat customer once per each customer that is repeating. We know they repeat when your cumulative sessions goes above 1. Thus we only check for 2 and count that. In my code, I am using SUM since my condition is…

As code block… SUM(CASE WHEN Cumulative Sessions = 2 THEN 1 END) OVER() / SUM(CASE WHEN Cumulative Sessions = 1 THEN 1 END) OVER()

I'm not sure how you are going to be to troubleshoot the download if you don't have access to the file. I use a regular SFTP program (such as WinSCP) to verify everything about files before trying to download or upload. Using provided settings, I can verify the file's existence before I try to connect. Make sure you have…

If I understand your issue correctly, you want to make edits in a webform that is being replaced each morning. My method is to make a separate form and join it to the webform via ETL. My changes and fields are in the side form…joined to the main dataset. No matter how the main set changes, my values for Yes/No stay the…

You may also check to make sure the issue isn't with the cache or dataset access. If the user can't see the dataset, it may not let them see the card. For cache, go to the browser setting and clear cache to make sure that isn't an issue. Although I haven't had that issue recently, when I first used Domo it seemed my cache…

When you share a dashboard with users, all the cards on that dashboard inherit the sharing settings of the dashboard by default. So, if you shared the dashboard with a group of users, they should have access to view all the cards on that dashboard. However, when you add a new card to an already shared dashboard, it doesn't…

Thanks to Anna Yardley, I now know how to access the rich editor to paste code. Apologies.

@nickcorona - Did you do it as typed, or did you change the [] to back ticks? I typed brackets because I don't know how to make back ticks show up in these comments.

Sorry…I should have expanded on that. You say it gave a duplicate entry. When you give it an explicit list (stating each one) such as s.Name, s.Year…. and then you also include s.* you are repeating yourself. s.Name, s.Year are included in s.* and thus would repeat or duplicate. By explicitly specifying the columns you…

It might be having a problem with aliasing - using asterisk. Asterisk is a representation for all. SELECT s.Name AS State_Name, s.Year AS State_Year, s.Gender AS State_Gender, s.Id AS State_Id, n.Count AS National_Count FROM state_names s LEFT OUTER JOIN national_names n ON s.Name = n.Name AND s.Year = n.Year AND s.Gender…

Hmm. Okay, maybe we can simplify. SUM(CASE WHEN COUNT([PhoneNo]) > 1 THEN 1 ELSE 0 END) / COUNT(DISTINCT [PhoneNo]) * 100 We count the instances where a phone number appears more than once (indicating a repeat customer). We divide this count by the total count of distinct phone numbers (representing all customers).…