ArborRose Coach

I don't think there's a built-in feature. But you could create another column in the dataset to represent the colors based on your value criteria. And use custom marker icons (blue and red airplane icons), assigning them based on the data.

@Dobbrunz - the problem I had was that I could not find an example using Domo. I was eventually able to find a way to do it using blank brick. See my code and example below. The result is good but the implementation is too much work.

Applying PDP to a dataset restricts access to the underlying data. You still need to separately grant user access to view alerts that use that dataset. Make sure users have been granted appropriate permissions at both the dataset and alert levels to ensure they can access the data and receive alerts.

I believe in Domo, when you apply a PDP policy to an alert, it limits the data displayed in the alert, based on the permissions specified in the policy. Applying PDP to an alert wouldn't automatically grant access to view.

The following link is to a Domo created presentation. When we gave an internal presentation, we showed a brief slideshow of our topology. Then we demonstrated how we bring data into Domo, display it in Domo, and how we use extracts to populate other information on our network. I would suggest you use an existing dashboard…

I think it would depend upon the specific functionality and actions that the add-in performs.

In most cases, the expires_in value is expressed in seconds. Therefore, in your example, the expires_in value of 3599 indicates that the access token is valid for approximately 3599 seconds, or about 59 minutes and 59 seconds.

That's a question for Domo. Possibly someone else can comment with another way.

One way you might be able to get it would be through the Domo API using Python. import requests Set up authenticationheaders = { 'Authorization': 'Bearer YOUR_ACCESS_TOKEN' } Make API request to retrieve user profileresponse = requests.get('https://api.domo.com/v1/users', headers=headers) Check if request was successfulif…

The original posted question mentioned the dataset changing every morning. And that refresh was over-writing the responses entered. If you use more than one dataset, you can refresh the main set without impeding upon your answers in another. Use a "key" field, like an ID that is common to both. In the data, let's assume…

Okay…I see the connector you posted. It shows the credentials need to come from the azure portal active directory. That can get tricky and possibly involve firewall ports.

Have you reviewed the Domo information page? Have you attempted a connection and now receiving an error?

@Ashleigh - Thanks. Yes, it looks like it save it this time.

Hmmm…unfortunately it doesn't save when you hit apply. I made the change, hit apply. But when you open it back up, the triggers didn't change. Apparently you still have to hit the save and run.

Colemen's answer refers to having json coming through an API. As Jason mentions, the workbench can simply load it in from a file. Find Domo Workbench under Admin > Tools.

Argh. I was trying to stay off the forum so others can answer. But I recently had to solve this for myself. I created an ETL with an aggregate tile grouped by whichever fields were needed. With the visits in an aggregate and the amounts in another aggregate: The trick here is the count distinct values. Then AFTER this…

It's been a minute. I have to re-read the problem to see what it is you are trying to solve. Then I need to recreate a data sample. You say, "It is going in a gauge card, I just provided the table for context into the data." So you want a date filter, a table of data, and a gauge showing the percentage of repeat customers…

Ah, nice. Thanks for that information.

@Ashleigh - I know this is an older post but I'm curious…how did you get to settings on an ETL? That might have changed. I need to change triggers on an ETL that takes 45 minutes to run. I don't want it to start and then have to cancel it. I simply want to change the triggers before it runs this morning. Settings doesn't…

I've also noticed after hitting "validate" to validate the code, when you hit Save and Close it doesn't….close.

We haven't completed the setup of the Domo NetSuite connection yet. Your question is a nice reminder that I need to move some focus back to that topic. Have you looked at the Domo NetSuite Connector?

Sounds like you need to do a left join on the matching tables and then a calculated field that says {columnname}: CASE WHEN {value in A} IS NOT NULL and {value in A}<>'' THEN {value in A} ELSE {value in B} END

Let's see if I have this correct….you have data that looks like this… You create a report that looks like this… But you want to unpivot the data so you can see All Sales, then all LBs, and all Cases. We can take the sample2.csv data and run it through an ETL to create Sample3.csv. Which gives us this.. And put that on a…

Assuming data looks something like my sample below, you could create a percent of total and then rank those. With a rank you can decide whether to display them ascending or descending and how many by filtering or setting the limit rows value. Dimension Value Totals A 50 200 A 30 200 A 40 200 A 80 200 A 100 200 B 20 150 B…

When I click the plus sign on the overview section and save, it saves there no problem. Where are you starting the card?

Can you show us any kind of mock up of what you are doing currently with your spreadsheet? There are quite a few forecasting videos and Domo examples on the web. Have you reviewed any of them? I would first look to the forecasting tile in the Data Science are of the Magic ETL…link…. There are also videos posted. Based on…

I do it as Grant mentioned - add an output on the dataset can give you a dataset to debug. I label that output set with the word debug so they are easy to find and remove afterwards.

You should be able to programmatically log into Domo using Domo's API OAuth 2.0 authentication to give you an access token. Register your app to get client credentials (client ID and client secret) through the developer portal. Implement the authorization to get an access token and redirect back to your application. Not…

It doesn't sound like a Domo issue. Sounds like something that needs to be addressed in the HTML and javascript code used to display the form. Different browser platforms have different compatibilities. Its typically the developer that needs to address the code to make things work.