ArborRose Coach

Have you considered some type of dropdown where the user can set their timezone in a dropdown and your dashboard adjusts by adding/subtracting from UTC time?

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl/DateTimeFormat/resolvedOptions I believe you can get the timezone in Javsascript using Intl.DateTimeFormat().resolvedOptions().timeZone. See link above.

In the JSON No Code connector that Grant describes, you will see some configuration fields for parameters. It might be easier to understand looking there. When parameters are passed to an API, they are either passed in line, like HTML does it on webpages. www.mysite.com?param=1 Or they are passed as part of a header…behind…

And you could create a bar chart such as… quartername: CASE WHEN QUARTER(date) = 1 then 'Quarter1' WHEN QUARTER(date) = 2 then 'Quarter2' WHEN QUARTER(date) = 3 then 'Quarter3' WHEN QUARTER(date) = 4 then 'Quarter4' END Expand on the chart by setting filters with your selection of year. Or include year as part of the…

If you put your data in a format like the webform below. You can use it as a source on a Domo card and let the card do the aggregation (finding the number of per whatever) In this case, I'm showing months and year. Just add a function for quarter where the formula is quarter([date]) and add it to the columns. Note, the…

Typically you want your data in detail form such as: user program date ———- ————— ——————- User A program2 2024-11-15 User B program2 2024-10-20 User B program3 2024-10-25 User D program1 2023-03-01 User D program3 2024-12-01 User D program4 2024-11-01 User E null null Then build out your card, whether that be a table…

Not on the normal table card, you can't merge cells. The card is pretty limited on any styling. You can find more capabilities on html tables and DDX bricks.

You can create formulas for each year. That way its dynamic and you don't have to hard code the years. For year to date use the following. Take out the condition that says and date less than equal current date if you want the full year. If your data field is amount, simply use [amount] and add the topics and it will break…

Monday.com has an API for you to connect (link below). As Grant mentions, you should be able to use the Domo JSON No Code Connector to connect. To find it, go to the Domo AppStore and type "JSON". The connector will show up in the results. You can also import and export from Monday.com. That's pretty much a manual process…

How about using something like GROUP_CONCAT to create a distinct list of all locations. GROUP_CONCAT(DISTINCT locationName) Create a calculated field that flags locations with audits within the date range desired. CASE WHEN startDate >= [Start Date] AND startDate <= [End Date] THEN locationName ELSE NULL END And filter out…

Duration of audits: DATEDIFF(completeDate, startDate) Date Range: Apply a filter to your dataset to only include audits within the selected date range. Where [Start Date] and [End Date] as user set params. CASE WHEN startDate >= [Start Date] AND completeDate <= [End Date] THEN 1 ELSE 0 END Identify locations without an…

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…