GrantSmith Coach

As a workaround, you can pre-pivot your data with an ETL and then use a mega table with the HTML code you need

To clarify you're wanting to update Azure AD when ADP is updated? Does Domo need to be part of that process? Domo doesn't have a way to automatically update Azure AD. If you're wanting to sync ADP and Azure ADP I'd look to see if ADP can handle the syncing? Something like may work for you

You can't use a beast mode within a card title or description currently. Only variables, filters, date ranges and dataset metadata. You could create a beast mode and use that for your Summary number and then display the summary number instead of the card title on your dashboard.

If you only have zip codes, FIPS codes, or state abbreviations in your data for Florida, you can set the US map to auto-zoom in your data so it'll show Florida. It's under "General > Auto Zoom to Data". You can also hide the states that don't have any data under General> Hide No Data Items

It seems several users are having issues with the workbench group error. I'd recommend logging a ticket with Domo support so they're aware of all of the users reporting this issue and to assist.

It's currently not supported by default. I'd recommend adding an idea to the idea exchange to add an option for 0 specific colorization. I'm sure others are wanting to do this as well. You could possibly try and "shudder" your values by adding a trivial amount (0.001 for example) so that you don't have it being exactly 0…

One other thing, if you want to see the unique count you can add a DISTINCT to the count before the CONCAT

The issue is with the count portion, are you looking for distinct row counts you can CONCAT all of the fields together: COUNT(CONCAT(Plant, Group, Code, Month, Name, Part Number1, Part Number2))

CASE WHEN QUARTER(`booking_date`) = QUARTER(`shipment_date`) AND YEAR(`booking_date`) = YEAR(`shipment_date`) THEN `Shipment Dollars` END You'd want something like this then

To get the dollar amounts you can use Mark's logic to return the amount for the quarter: CASE WHEN QUARTER(`dt`) = QUARTER(CURRENT_DATE()) AND YEAR(`dt`) = YEAR(CURRENT_DATE()) THEN `Shipment Dollars` END

You can use the Alter Column tile to convert your string to a date type field. You'll need to specify the date format as %d.%m.%Y. Alternatively you can use a formula tile and the STR_TO_DATE function to convert it to a date: STR_TO_DATE(`date_field`, '%d.%m.%Y') Here's more information on date formatting characters for…

The Overview is an interesting special page. It is generated based on whomever is logged in so the ID will be the same however the cards that are associated with that specific page are dependent on who you are authenticated as. You'll likely just need to create several different tokens for the different users and repeat…

Are you looking for the actual definition of the dashboards or just a picture of the dashboards? Domo's Public APIs don't have a a way to currently do this but you could attempt to look at the lower level APIs which wouldn't be supported. Alternatively, have you tried using other automation packages to go to your dashboard…

The connectors currently don't support functionality like this doing a historical backfill. You'd need to do it manually.

At this point I think support will be your best option. Typically in the past when I’ve seen this issue was because the system wasn’t running the service scheduler properly but it sounds like you’ve already restarted and investigated that.

Simply put the publish dataset is being read from the main instance and not the publication instance. Same concept as a federated dataset but instead of a Domo database it’s pulling from a different database like snowflake

.

You'll need to log a support ticket then to have Domo's development team investigate the issue as it appears to be a python package issue.

Try and comment out your lines of code until you no longer get the error message. Is it in the summarize function call or does it happen when importing the package? im guess that you’re trying to use it in a non Domo Jupyter workspace which is likely causing the issue

Give your machine a reboot that typically solves problems I have with workbench.

If you have garbage data which doesn't match your date format ('Day' in your example) it may not be simple enough to just convert it to a date. You may need to conditionally set your date value: CASE WHEN REGEXP_LIKE(`date_field`, '^\d{4}-\d{2}-\d{2}$') THEN STR_TO_DATE(`date_field`, '%Y-%m-%d') END

Embedded dashboard currently don’t support scheduled reports. You can add this as an idea to the idea exchange to see if they may add it in future releases

Date BETWEEN DATE('2023-10-12') AND TODAY() in a filter file with a formula criteria

You need to edit your dashboard and change the card interaction to drill in place that would allow it to access the drill path Rather than filtering your dashboard

There's an existing request in the Idea Exchange I'd recommend upvoting:

You can have Domo configure a fiscal calendar and you can then use the standard period over period charts: Alternatively I'd recommend utilizing a custom date dimension where you can a define your fiscal years and also custom offsets. I've written up an article on how to do this here:

Regarding question 2 it will evaluate it in the orders of parenthesis first and then AND/OR equally going left to right so you're correct in that it will evaluate it like (A AND B) Or C ) AND D

You'd do the same thing above except use the batch id instead of the date to get the latest batch ID records.

You'll need to pre-aggregate your data with a window function in Magic ETL in order to keep all-time around. Window functions in Beast Modes will only apply on the data that is available after filtering.

I'm assuming by the latest row you mean the one with the most recent date and not the last row in your dataset. Using Magic ETL - feed your dataset into an add constant tile, add a constant called "Join Column" with a value of 1, feed that into a group by tile and group by this new field selecting the Maximum date, then…