ArborRose Coach

You added single quotes in the image. In Oracle, when you're calling a procedure like fnd_client_info.set_org_context, you should pass numeric values without quotes, as it expects a number rather than a string.

You can remove cards from the "Shared" page in Domo by adjusting the sharing settings. Open the card, and click on the three dots (menu) in the top-right corner of the card. In the sharing settings, you’ll see a list of people or groups who have access to the card.

I don't believe Amazon has an API for product reviews, just product advertising. But there are third party services that offer APIs to Amazon review data through scraping: SerpAPI, Apify, RapidAPI. You could also use Python to create a custom web scraper, but you need to check the Amazon terms of service to make sure it…

The warning about being unable to access the CRAN repository seems to indicate the environment in Domo might be blocked from making outgoing connections. Possibly due to network or firewall settings…on Domo's side? Can you install from a mirror? install.packages('SentimentAnalysis', repos = 'https://cloud.r-project.org')…

It may be that Domo does not recognize the date field. You can go to the schema and check the data types to make sure the field you are using is a Date type. For filter, you can use a calculation such as CASE WHEN `Date` >= CURRENT_DATE() - INTERVAL 9 DAY THEN 'Last 9 Days' ELSE 'Other' END

Domo doesn't have a built-in hover interaction across separate cards. I believe you would have to use a filter on click (click on a bar in one card to trigger a filter that affects the other card), a slicer card, or create a custom application.

Domo doesn't have a centralized API or DomoStats feature that retrieves information across multiple Domo instances. You can only pull information within a single instance.

It's done to optimize performance. My company works with datasets that have millions of rows. I wouldn't expect Domo to have dropdown filters and such with millions of entries. So I aggregate the data beforehand or set filtering so it breaks up the data to something reasonable to handle on a card. It's my understanding…

If you are filtering on created date, all orders created on that date (10/18) should show up regardless of updates. Domo and Shopify may have different time zones. If Shopify are in UTC and Domo uses local time zone, some orders may fall outside the range. You may also encounter issues due to delayed order updates. The…

There are two date filters in the Shopify connector. Created date and updated date. The created date gets all the orders that were placed with the date range you request. But it won't include updates if the fulfillment occurred after the dataset refreshed. You miss the updates to the order, such as fulfillment statuses…

Can you process this through a Magic ETL?

How about doing it this way? CASE WHEN Coop Event = 'Aug 2024 Moto Coop 2' THEN SUM(CASE WHEN SUM(OrderGrandTotal) FIXED (BY MpowerOrder) >= 963 THEN SUM(OrderGrandTotal) FIXED (BY MpowerOrder) - 963 ELSE 0 END) FIXED (BY MpowerOrder) WHEN Coop Event = 'Aug 2024 Moto Coop 1' THEN SUM(CASE WHEN SUM(OrderGrandTotal) FIXED…

As @MarkSnodgrass mentions, I use Domo Workbench. You can also schedule file and ftp imports in other methods like Python.

I would suggest capturing your data using recursion or some other method…as a snapshot. This would let you compare it with the current data. You can use the contract date to see if the order expired, even if its no longer in your dataset. You can join the current with the historical snapshots to compare and identify which…

You could try to "debug" the issue by simplifying and testing aggregation separately SUM(OrderGrandTotal) FIXED (BY MpowerOrder) And testing the logic without the aggregation: CASE WHEN Coop Event = 'Aug 2024 Moto Coop 2' THEN CASE WHEN OrderGrandTotal >= 963 THEN OrderGrandTotal - 963 ELSE 0 END WHEN Coop Event = 'Aug…

Sounds like you might try creating a Magic ETL with beast mode formulas to distribute the data across the desired time period. To join your aggregated data by ad type with a calendar table based on the date range that matches your aggregated period. If the ad type data is aggregated for a month, distribute the value across…

It appears you may be having trouble because of the nested aggregation (SUM within a SUM). Try this: CASE WHEN Coop Event = 'Aug 2024 Moto Coop 2' THEN SUM(CASE WHEN OrderGrandTotal >= 963 THEN OrderGrandTotal - 963 ELSE 0 END) FIXED (BY MpowerOrder) WHEN Coop Event = 'Aug 2024 Moto Coop 1' THEN SUM(CASE WHEN…

What @MarkSnodgrass said above. His trick with the svg shape naming is brilliant.

I don't believe there is any built-in way to configure log retention. They are stored locally and accumulate over time. But you could create a script (PowerShell or batch file) that checks the date and deletes anything older than your desired retention time. And schedule the script in Task Manager.

Have you tried using Magic ETL with Text tile, Split Column to split on the pipe symbol?

You need someone smarter than me to answer that.

I'm not sure about creating 21 charts using Domo charts on an App. That's what I would try first. And I haven't tried it. But…as an answer to how I might do it more efficiently - you could do it in a blank brick. const widgetData = [ { type: 'Small', color: 'Red', data: [12, 19, 3, 5, 2, 3] }, { type: 'Small', color:…

Are these all bar charts with the same column names (fields), created from a Magic ETL? The only difference being how they will filter?

Have you considered connecting using Jupyter Notebooks and a Python script? I don't believe it would cost any extra credits if it is done in the same script. In Domo, credits are typically tied to the DataFlows, Workflows, or API execution rather than each individual execution of a Python script. Executing a Python script…

The issue appears to be how the datatables library handles rendering. It applies the styles after rendering the data, which appears to be causing it to skip the first column. You can try applying the formatting during the drawCallback. $(myTable).DataTable({ data: reorderedData, lengthMenu: itemsPerPageOptions, columns:…

I don't use the Adobe Analytics Connector, but you could try making more than one API request. Each with a different set of dimensions and then combine the results using Magic ETL. Or possibly do some of the processing in Adobe Analytics and then pull the metrics instead of the raw details.

The Beast Mode calculation appears to be causing a processing error, likely due to the combination of a window function and the dataset size. The calculation for repeat customer revenue may be leading to the error. To avoid the complexity of window functions and reduce processing load, the OVER (PARTITION BY), appears to…

Error: "Domo is ready, but you don't have access to the associated account. Please contact the account owner to have them share the account with you." Cause: Permissions Issue: The user does not have access to the NetSuite account linked to the Domo connector. This could happen if the account owner (the person who…

I'm still doing a bit of work. But my end goal is to create a blank brick that summarizes my API and Jupyter calls as a custom made Gantt chart. Basically because I couldn't figure out how to do it with a Domo chart. I want to visually see which tasks I have scheduled at specific times to ensure hand-offs and to…