GrantSmith Coach

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:

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. Another alternative is to use child instances to separate all data between users and have users login directly to a child / publish instance.

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. This way they can select whatever date range they want and see the selected. value and the value from…

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 Also, visualizations have a default row limit of 25k for visualization but that can be changed in Analyzer however that will likely…

@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: 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.

Have you looked into a Grouped and Stacked Bar Chart? That seems like what you're wanting:

@Ajita it would help to have more information. What is the error you’re experiencing? What are you seeing versus what are you expecting? I’m not sure if it’s a copy and paste error but you might be missing a space and a.Year

Auto selecting a value on a filter card and giving it automatically update the page isn’t currently possible. I’d recommend adding it to the idea exchange You may be able to add a default page filter and update it daily or weekly or whatever the update frequency is. Not ideal but might get you something close. Adding a…

Do you want users to instantly gain access or should it go through a review? Should the request come through Buzz or via another option? A quick and dirty option is to use the mailto protocol in an HTML hyperlink where you can specify to, subject and message body so you can send it to an automated email box: <a…

I stand corrected. Thanks for sharing @colemenwilson. Time to review all of the new datasets in the Domo Stats.

Currently scheduled reports can't get the background changed. Brand Toolkit (premium) does allow for adding in HTML code for the header and footer in the email templates but the background isn't an option.