GrantSmith Coach

You could attempt to inspect the network traffic and call the same APIs that Domo uses, but that isn't a supported method for extracting the data.

Card-specific color settings will take precedence over the default coloring. If you're changing the hex code for the color you already are using on the card in your brand kit, it'll add it to the existing card.

CASE WHEN `Program Guide URL` IS NOT NULL AND `Program Guide URL` LIKE 'http%' THEN CONCAT('<a href="',`Program Guide URL`,'">',`Certification`,'</a>') END

You need your </a> at the end of certification so that it actually makes the Certification clickable to the URL you define. CONCAT('<a href="',`Program Guide URL`,'">',`Certification`,'</a>')

This isn’t possible le currently unless you go down the custom app route. I’d add an idea to the idea exchange to see if Domo will add this ability

Depending on your prediction model it can be fairly compute-intensive so I typically leave this to a MagicETL to do the heavy lifting for me. Doing a self-service type model isn't really supported unless you're doing a very simplistic algorithm for your model. When doing it at the card level the Adrenaline layer isn't…

If you recreate the job are you able to get it to connect to Domo?

Have you tried using a Gantt chart?

@pauljames is correct, it'll prompt you to change ownership of the users. You can also swap ownership of Domo objects using the swap-owner command as part of the Java CLI tool that Domo provides.

@cepii - Why do you want to utilize Domo as a middle layer for this when a direct connection between ADP and Azure would likely be simpler and less complex?

Currently there isn't a report to show all of the embed IDs but I'd recommend adding an idea to the idea exchange to improve the DomoStats connector

You can use a magic ETL and a formula tile to tack on the specific time your dataset was imported. It wouldn't match exactly to your system's date but would allow you to have a date tacked on in your dataset every time it's imported. You use a formula tile with the formula: CURRENT_TIMESTAMP() If your data is being…

A recursive dataflow will allow you to UPSERT your date (update if it already exist or insert a new record if it doesn't). So if you need to re-run your dataset it'll protect against duplicated data. The caveat to recursive dataflows is that by nature as the dataset grows the ETL will take longer to run as there's more…

a 429 error means that the connector has made too many requests in a specific amount of time and has hit the API Rate Limit (can either be x/day, x/second etc). The connector should intercept these errors and then wait the required amount of time to then resume the request without failing. This would need Domo to update…

How are you wanting the summary number to change? It should automatically update when you filter the card

Have you attempted to calculate the difference between today and the date field and then filtering on that field? DATEDIFF(CURRENT_DATE(), `date_field`) And then drag that into the filter and have it be between 1 and 8

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.