Comments
-
Domo provides an R package you can leverage to extract data from Domo using R: It outlines how to connect within the README
-
Are you currently utilizing the "Line + Grouped and stacked" chart? You'll also need to make sure you have your projections included in your dataset as well. You can leverage a Metric field with the type of metric which would have "Prior Year", "Current Year" or "Projected" as the values and use that as your category. Are…
-
Use IN instead of = SUM(CASE WHEN Product Code Number IN ('10','11','12','13','14','15','16','20','21','30','40','50','60','61','70') THEN Quantity ELSE 0) - SUM(CASE WHEN Product Code Number = '83' AND Unit = 'SF' THEN Quantity ELSE 0) / SUM(CASE WHEN Product Code Number IN…
-
@HowDoIDomo - Domo's Google Ads connector works for me now and I've had success utilizing it.
-
You should be able to use your code function to extract the email address out of the JSON with some javascript and then send your email.
-
Are you able to monitor the network traffic in an effort to sniff which APIs it might be calling and then use those APIs? The cleanest option you have with your excel file would be the ctrl+v paste option into a local excel file that you upload then you can use Magic ETL to convert the data types and clean the data.
-
How isn't the color rule working properly? How are you calculating the Average - is that stored in a separate column?
-
Try and pass the attributes in the correct format: "attributes": [ {"key": "customTestAttribute", "values": ["test value"]} ] You may need to save a user manually and monitor the network traffic to make sure you're using the correct field ID as it won't always be what's displayed.
-
Alternatively, you can create your own custom connector using the connector framework if you want to get more technical:
-
There isn't a native Microsoft Sentinel connector however Domo does provide a JSON No Code OAuth connector you can attempt to utilize and point to specific URLs I'd recommend looking into. https://[INSTANCE].domo.com/appstore/connectors/com.domo.connector.json.customparsing.oauth
-
Does your data have July-Sept in the Current YTD YTD_Period field? Are you using Domo's Fiscal calendar?
-
What API are you attempting to connect to? Do you have the appropriate APIs enabled in your Google Console?
-
Are you wanting to view the code and make changes to it or are you just looking for the URL to deploy it again? If you need to make code changes you need to unpublish it and then make changes and re-publish your connector.
-
Because the AppStudio is sandboxed you won't be able to use a button to bring up the print dialog box. You can log an idea in the idea exchange to allow that functionality.
-
There isn't an option to increase or decrease the ratio between the bars and the data table. You could leverage two separate cards (bars only and table only) to enable you to resize them to the desired ratio.
-
If you add the account back with the same email address it should restore the user's account with the same ID and metadata.
-
Domo won't track your current filters automatically across the different dashboards. I'd recommend adding this to the idea exchange.
-
Domo has a good KB article on setting up partitioning in Workbench you can follow here: . It's for 5.1 but should be the same for 5.2
-
Currently, this isn't an option; however, you could leverage a custom app to set the background yourself.
-
You could configure the card interaction in the dashboard to go to another card where it wouldn’t apply the drill path filters. Are there some filters you need to keep?
-
you can possibly leverage the activity log dataset to count the view events
-
Have you tried re-authenticating the account to approve the scopes necessary for the connection?
-
OKTA's System Log API keeps data around for 90 days (source). It should be possible to get data for the last 30 days. Since Domo provides the API connector they'd need to be the ones to change the code to pull 30 days instead of 7. As Colemen mention you can log an idea in the idea exchange or you can possibly log a…
-
Ah, since you're displaying dates in your x-axis and you don't want the dates to be included in your amount you can use the REMOVE clause in your fixed function:
-
You could use a beast mode to display the selected state if only one is selected: CASE WHEN COUNT(DISTINCT `State`) = 1 THEN MAX(`State`) ELSE '' END
-
have you tried using your fixed function but instead of using by date use filter deny date and have no by clause
-
When I'm doing period over period type analysis I'll restructure the data so that I can reference each period type for each day. Then use Beast Modes to calculate the differences and the % changes. I've done a write up on this in the past:
-
Are your transactions duplicated? If not you could do a conditional sum like: SUM(CASE WHEN `transaction_type` = 'Quantity' THEN `quantity` ELSE 1 END)
-
Can you connect to the SFTP server using another tool besides Domo? If you can I'd recommend reaching out to Domo Support
-
Currently this isn't possible however may be able to do this sort of functionality within a Domo Brick