If you continue with regexp, you can try something like this… CASE WHEN REGEXP_LIKE(REGEXP_REPLACE(`body`, '^\s+|\s+$', ''), 'USD\s+\d{1,3}(,\d{3})*(\.\d{2})?') THEN REGEXP_REPLACE(REGEXP_REPLACE(`body`, '^\s+|\s+$', ''), '.*USD\s+(\d{1,3}(?:,\d{3})*(?:\.\d{2})?).*?', '$1') END

If the preview works but the output is empty, it might be there are characters unseen. Have you tried using trim/replace? I'm not sure if this formula is quite right as I'm not in an example. CASE WHEN REGEXP_LIKE(REGEXP_REPLACE(`body`, '^\s+|\s+$', ''), 'USD\s+\d{1,3}(,\d{3})*(\.\d{2})?') THEN…

The first part of that regular expression may not work with Domo SQL because part of that is a "lookbehind", which can be finicky. If you try to isolate the numeric part following the USD, you could try something like: CASE WHEN REGEXP_LIKE(`body`, 'USD\s+\d{1,3}(,\d{3})*(\.\d{2})?') THEN REGEXP_REPLACE(`body`,…

In the base URL, do not include a slash and avoid adding a question mark if you plan to include the entire query string dynamically. When you create the dynamic parameters, do not include an initial question mark nor a slash. Format the dynamic parameters so they start directly after the base URL, something like:…

You can't directly reference a dataset field in the textbox for "Single URL," so you probably need to approach it a bit differently using Dynamic URL with a dataset. In your ETL or DataFlow, concatenate the full URL (including all parameters like Scenario, FiscalYear, $filter=FiscalMonth, etc.) into a single column. For…

GET https://localhost:3000/domo.js net::ERR_ABORTED 404 (not found) This error indicates that the application is trying to load domo.js from localhost:3000, but the file does not exist, resulting in a 404 error. This is a key issue: domo.js is missing or not correctly deployed to your local server. Refused to execute…

If you are using concat to combine text and numeric values on an html card, you won't be able to use Domo's heatmap. But you can implement your own heatmap by assigning your own color ranges based on the number of accounts. Level 1: 0 - 10 accounts → light green Level 2: 11 - 30 accounts → yellow Level 3: 31 - 50 accounts…

You put multiple cards on a dashboard and the filters work across the cards. In this example, the main card is the green outline at the bottom. The three cards at the top are for filtering. They have chart type: filter. Each of the cards use the same single dataset (result of an ETL or an import, etc).

Think of a dashboard as a collection of cards. You can have several cards on the dashboard. They can be text/table cards, charts, etc. Each card would use a single dataset. If you are joining the datasets, you would create a Magic ETL to handle the logic. In this brief example, we would take two datasets, join them and…

The card probably isn't the value going to the alert. That would be the field in the dataset. If you set a field up to represent percentage in the dataset, it should show up as a percentage in the alert. You might even have to do it as a string representation in the dataset.

I see. So some branches and months may not exist and the join won't create rows for missing combinations. Sounds like you need a way to make sure the combinations have all relevant GL accounts, if if they don't exist in the GL Records. You could handle this by creating a master dataset. Complete with all possible branch,…

Glad to hear you got it resolved. For anyone not aware, under Admin > Toolkit, there's a scheme management capability to modify a dataset's field types. But I use it as a last resort; when I can't seem to get Domo to accept my field types on import.

Domo tries to infer the data type based on what it sees in the column of numbers and text. If you import an Excel file, and use formatting in Excel prior to the import, you can get Domo to recognize the proper types to use. For example, if you import a date Domo will probably get it wrong. But format the column to date…

Perform a full outer join or a right join between the GL Records table and the Chart of Accounts table. The key for the join will be the gl_account_id. This will ensure that all rows from the Chart of Accounts table, including "Addons-Repairs," "Restocking Charges," and "Contractor Discounts," will remain in the result…

I wasn't at Domopalooza, but it looks like a very interesting card. I think what you are looking for may be something like the following. rgba - is R (red), G (green), and B (blue)..the colors of light. With an alpha channel as a fourth value. The values go from 0 to 255. Turning the first value to 255 means red is on.…

1. Model Setup with ARIMA (Exogenous Variables) or Random Forest ARIMA with Exogenous Variables (ARIMAX): ARIMA can accept external (exogenous) variables in addition to time series data. You can set up an ARIMAX model using Python in Domo's data science tool (like Jupyter Workspaces or Python tile). In Python, when fitting…

I don't think we can turn off the icon. We can only disable functionality. Which makes no sense to me. All AI appearance and functionality should be off by default.

There's no beast mode command for dealing with commas, but you can achieve it in other ways if desired. CASE WHEN `Category` = 'Revenue' THEN CONCAT('$', CASE WHEN ROUND(`Actual`, 2) >= 1000000 THEN CONCAT(ROUND(ROUND(`Actual`, 2) / 1000000, 2), 'M') WHEN ROUND(`Actual`, 2) >= 1000 THEN CONCAT(FLOOR(ROUND(`Actual`, 2) /…

Um…I did not put those numbers on that code. Hmm.

You should be able to use the Python tile to use Domo inputs or filtering. Run something like from statsmodels.tsa.arima.model import ARIMA y = your_time_series X = your_exogenous_variable model = ARIMA(y, exog=X, order=(p, d, q)) model_fit = model.fit() forecast = model_fit.forecast(steps=10, exog=user_input_exog)

Sorry…I'm not in Domo testing the function. I'll create a quick sample set and test. CASE WHEN `Category` = 'Revenue' THEN CONCAT('$', ROUND(`Actual`, 2)) WHEN `Category` = 'Sales' THEN ROUND(`Actual`, 0) ELSE ROUND(`Actual`, 2) END

How about something like CASE WHEN `Category` = 'Revenue' THEN CONCAT('$', FORMAT(`Actual`, 2)) WHEN `Category` = 'Sales' THEN FORMAT(`Actual`, 0) ELSE FORMAT(`Actual`, 2) END

I would try creating a beast mode field to count how many times each name appears. This will help identify duplicates. Something like COUNT(`Full Name`) OVER (PARTITION BY `Full Name`) Then set conditional formatting on the Domo card. Create a rule where - if the name count is greater than 1, it will apply a background…

In Domo, if you're the owner of a card, it will automatically appear on your "Shared" page because ownership implies that it's part of your content management. Unfortunately, there's no built-in option to retain ownership of a card while removing it from your "Shared" page - this page is designed to display content that…

USDA appears to have documentation on their API online: https://www.ers.usda.gov/developer/data-apis/ It looks like you just register for a key (credentials). You then use a Domo connector to interface with the USDA data. I'm not aware whether there is a USDA specific connector, but you can probably use the generic JSON No…

When comparing the signature from the X-Hub-Signature header with the computed signature, make sure you're using a secure string comparison function to prevent timing attacks. # Example comparison received_signature = 'sha1=received-signature-from-domo' is_valid = hmac.compare_digest(signature, received_signature)…

It appears you are using the wrong hashing algorithm (SHA-512), I believe Domo's webhook uses SHA-1. Try this: import hmac import hashlib # Shared secret key shared_secret = "the-shared-secret-key" # Payload data (body of the request) payload =…

Domoダッシュボードをより使いやすくし、スクロールを減らすために、ダッシュボードの上部にテキストボックスやHTMLカードを使用してフィルターをまとめることができます。これにより、アコーディオンのようにセクションを展開・折りたたみできるようになります。また、すべてのグラフに適用されるページレベルのフィルターを使用すれば、個別のフィルターをスクロールする必要がなくなります。さらに、グラフをコンパクトなグリッドレイアウトに配置し、インタラクティブフィルターを使用することで、ユーザーがスクロールせずにグラフを閲覧できるようになります。HTMLやCSSの知識があれば、本物のアコーディオン機能を実現するためのカスタムコードを埋め込むことも可能です。…

Yes, you can pass query parameters via the URL. But you'll have to code to capture the params. Something like https://instance.domo.com/app/myapp?param1=value1&param2=value2 function getQueryParams() { const urlParams = new URLSearchParams(window.location.search); const param1 = urlParams.get('param1'); const param2 =…

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.