GrantSmith Coach

Alternatively here's a beast mode version: CASE WHEN MONTH(`dt`) IN (3,6,9,12) AND DAYOFWEEK(LAST_DAY(`dt`)) < 4 AND `dt` = LAST_DAY(`dt`) - INTERVAL (DAYOFWEEK(LAST_DAY(`dt`)) + 3) DAY THEN 'Exclude' WHEN MONTH(`dt`) IN (3,6,9,12) AND DAYOFWEEK(LAST_DAY(`dt`)) >= 4 AND `dt` = LAST_DAY(`dt`) - INTERVAL…

You can't use a variable directly in the items section. You need to use a variable in the beast mode. You can add the variable control to the page and and configure it to be a dropdown to help apply to your different cards which use the varaible.

You'll likely need to reach out to Domo Support as it sounds like some back end wires are crossed with your ETL.

@JasonAltenburg That's how variables are configured to work. With your case here I think your best option is to stack your data in a dataset with different types of metrics / filters with the values to filter on and then have two filter cards, one for the metric type and one for the values. I know this will increase the…

You can use a beast mode for this SUM(`Revenue`) / SUM(`Days`) You can use the same aggregation and logic for the revenue and days

You'd need to write a script in something like Python to query all your datasets and then update the name / descriptions. There isn't an easy way within the UI. You can use the pydomo package to do this. https://github.com/domoinc/domo-python-sdk/blob/master/examples/dataset.py

You can use a formula tile and a regexp_replace function to strip out the numbers. REGEXP_REPLACE(`field`, '^.Purchase Order (\d+).$', '$1') This will get all numbers after Purchase Order until it doesn't see a number so this would extract 12345 and not ' 12345 1235315132' from your second example as there is a space after…

If you're using the pydomo Python package you can utilize the streams property. Here's an example of the stream interactions: https://github.com/domoinc/domo-python-sdk/blob/master/examples/stream.py

You're able to edit comments up to an hour after it's first posted. After that time it's locked. You can try and reach out to a community forum admin ( @GrantStowell / @AnnaYardley ) and see if they're able to use their powers to delete your old comments

Due to how Domo processes grand totals it puts the GRAND TOTAL in the first column that's available even though you're wanting to display the total amounts. To get around the issue you'd need to have another column at the far left to hold the GRAND TOTAL text and allow your LY Retail Sales column to display it's actual…

You can pull this via the Domo Governance Datasets Connector and pull the Dataset Schemas report. It will list all columns in the datasets and the description for each column. I misread your request. The column descriptions aren't available in the metadata datasets. pydomo doesn't return the column descriptions when…

This is caused because your dataset is too large. An option is to put your field in your Optional Group By to consolidate the duplicates and set it to be a MIN or MAX aggregation.

PDP is typically an option to help keep data separated and filtered so other users can't see data within the same dataset. https://domo-support.domo.com/s/article/360042935314?language=en_US Another alternative is to use child instances to separate all data between users and have users login directly to a child / publish…

This appears to be an issue with the Domo connection. You'll need to log a ticket with Domo Support to have them investigate this issue.

You can do a conditional beast mode to calculate your revenue or cost calculations and not use the type as a grouping Revenue CASE WHEN `Description` = 'Revenue' THEN `Actuals` ELSE 0 END Cost CASE WHEN `Description` <> 'Revenue' THEN `Actuals` ELSE 0 END Profit CASE WHEN `Description` = 'Revenue' THEN `Actuals` ELSE 0 END…

Hey @jakebutterfield I recommend restructuring your data model so you can have multiple periods for each date (in your case this year and last year). I've done a write up on this in the past which might be helpful for you.…

If the beast mode is saved to the dataset on all of the subsets with the same name then it should work.

There are some limitations to the columns and rows for a table card. This article helps outline some of those limitations and the limitations of Excel if you're attempting to export the data https://domo-support.domo.com/s/article/360043429573?language=en_US#row_limits Also, visualizations have a default row limit of 25k…

@james_kibugu - Domo is expecting the dictionary keys to be non-empty due to how it processes the data however normal python is ok with having non-empty strings. I'd recommend adding a check in your code to look for empty strings and then set it to a specific value or ignore those records in your dataset.

You can utilize the Domo Brick called "D3 Ranked Animated Bars Brick" as a starting framework to help you update the graph over time. You'll just need to change the type of graph being displayed from a bar chart to a choropleth map instead. You can find it in the App Store.

Are you attempting to delete the all rows policy? What is the filter logic for your PDP you’re removing?

Domo provides an example in their Python SDK you can reference: https://github.com/domoinc/domo-python-sdk/blob/master/examples/dataset.py It does need to be created by the API.

Alternatively you can simplify this with something like the following: case when DATE(`Alarm Received Store Time` - INTERVAL 6 HOUR) = CURRENT_DATE() - 1 then 'Include' else 'Exclude' end

Hi @Aag2023 It sounds like you need a recursive data flow. There is a great KB article on it here: https://domo-support.domo.com/s/article/360057087393?language=en_US

Currently no, annotations are not compatible with table cards. I'd recommend adding this to the idea exchange for others to vote on this option. It'd be great to be able to annotate a specific cell.

@kav_100 Without seeing your SQL code, CURRENT_DATE doesn't exist in MS SQL. You can use GETDATE in it's place. Alternatively use CURRENT_TIMESTAMP

@donna_torrice - Domo stores your job definitions externally so if you're reinstalling Workbench they should re-appear after installation assuming the server information remains the same. If you're still worried about losing your jobs you can export your jobs in workbench before you do an upgrade however if you attempt to…

Assuming you're wanting the numerical value out of the hidTxtGonSearch field you can utilize a regular expression in a formula tile in Magic ETL. REGEXP_REPLACE(`field`, '^.*hidTxtGonSearch=(\d+).*$', '$1')

Are you using a Magic ETL transformation with a formula tile or a MySQL transformation? Is your PRODUCT_KEY field a date field or a text field or a numerical field? Why are you casting it to a string, then to a date, then to a string and finally back to a date again? Assuming you're using a formula tile in Magic ETL: If…

You may need to pre-aggregate your dataset in an ETL as there's too much data for the chart to display.