GrantSmith Coach

Sorry, trying to write regexes on mobile is not a good idea :D REGEXP_REPLACE(`PRODUCT`, '^.*?([0-9]+[^ -]*\s?.*?)(?= - ).*$', '$1') Adding a ? after your \s will make the space optional so it then also works with your examples of Cocktail 16X14OZ - Packed or Cherry Tomato 12x1pt - Packed @ChrisGaffan Also I utilize a…

You'd use a formula tile to calculate a new field in Magic ETL. If your end delimiter is ' - ' then we can tweak it to be something like: REGEXP_REPLACE(`Production`, '^.*([0-9]+.*) - .*$', '$1') This simplified version looks for numbers followed by any number of characters until it finds a space-space delimiter. Will…

Because you're sorting on your event date it can't aggregate your mon_adjust calculated date. If you sort based on your mon_adjust column instead it may resolve your issue.

Will it always be one more more number followed by x and then one or more numbers followed by some extra characters or will that format possibly change? REGEXP_REPLACE(`Production`, '^.*([0-9]+x[0-9]+[^ ]*).*$', '$1') This regex follows that pattern where it's looking for one or more digits preceeding the x character and…

There isn't a specific dataset that would track this information. You'd have to get the card definition yourself to see if there is a field rename happening utilizing something like the java CLI with the backup-card command but that will only get your the JSON definition in a file and not as a dataset.

It's how the publication is interpreting your options. You could log a ticket with Domo Support to see if the development team can look into the issue or alternatively you could put your default option first in your list.

Your regex is is actually only checking if the first digit contains a number ^ - Start of string [0-9] - Any single digit between 0 and 9 You'll want to match the entire string: ^[0-9]+$ + - Match one or more of the prior expression (in this case digits between 0 and 9) $ - match the end of the string

I've had issues in the past with the PPT plugin not pulling smart text properly. I'd recommend logging a ticket with support to have the development team take a look at it for you.

You can use an Oracle Database Writeback connector to write data from Domo into a table in Oracle. https://domo-support.domo.com/s/article/360042932434?language=en_US

Workbench is used to ingest data into Domo. If you want to export data from Domo to Oracle I'd recommend looking into a writeback connector.

variables are unique per instance and not per dataset like beast modes are. You won’t be able to have one with the same name. You’d need to create a new one

dates and times are still represented as timestamps. If you really just want the text values you’ll need to convert it to a string but will lose the ability to do date operations

Do you have anything selected for your Region filter? If you don't then it uses the default text setting on your smart text which is blank by default. If you change it to All Regions it will then show that. As for the previous month it's not possible with that type of interaction however you may be able to select the…

I've utilized Python and the pydomo package to export data from Domo and then utilize the pandas package to export the different datasets to an excel file. It's a bit technical and involved but gave me the greatest flexibility.

I'd recommend logging a ticket with support as they own the connector code and could help diagnose your issue better.

This isn't available in the governance datasets. You can get this information through internal API calls to the card definitions but you'd have to go through all of your cards to get this information using a scripting language like python.

You can use a filter with something like: `Ship Date` <= CURRENT_DATE() AND `Ship Date` > CURRENT_DATE() - INTERVAL 4 WEEK

this is because of how Google sends back the data. When you query the data via the API it is sampled so the numbers don’t line up correctly but the directionality of the data would be the same. This is to save in processing time and resources due to the large amount of data

You can either use SPLIT_PART or a regular expression: SPLIT_PART(`field`, ':', 2) REGEX_REPLACE(`field`, '^.*(\d+)$', '$1)

a REGEX version would be: REGEXP_REPLACE(`field`, '^.*(\d+)$', '$1')

if you’re use a dataset view to profile your dataset and then feed it into a magic Etl dataflow that will decrease processing time. This won’t create a new dataset but have a virtual one as the input. This will allow for less data to be transferred to the Etl platform decreasing the amount of time needed to process the data

The rule I have is that if the beast mode doesn't need to be affected by filtering, I'll put it into the ETL instead of a beast mode as it's more efficient and allows the card to load faster. In the past Domo interpreted all beast modes but some time ago converted it to only process the ones that are being used. I'll…

Yes, you need to go through Admin > Content > Dashboards search for the dashboard you want and select the checkbox. In the upper right will be an option for Edit, select Add Users & Groups and add yourself since you're an Admin.

Instead of using the string '1' just use the number 1.

Hi @seth_fuller You can switch off the abbreviation in the mutli-value card under the chart properties > Value Options and uncheck the Auto Abbreviate option.

you can try and use a fixed function with a filter none. Try something like SUM(SUM(`Total`) FIXED (FILTER NONE))

The Major Domo classes that Domo offers as part of the certification do a really good job reviewing the concepts and content to prepare you for the certification. I'd recommend reviewing those before you take the certification test.

You can apply programatic filters on your embed to filter your data to only the clients data you're interested in assuming you know which client is logged in and have the filter information.

Alternatively, because CASE statements will exit on the first condition that's true, you can go in reverse order to simplify your beast mode as the prior conditions are implied as false. CASE WHEN `Sale Liability` >= 500000000 THEN '$500M+' WHEN `Sale Liability` >= 250000000 THEN '$250M-$500M' WHEN `Sale Liability` >=…

The issue is that you have multiple values for the same week so using a LAG window function won't work in your case. When I'm dealing with period over period analysis I'll utilize my own date dimension table and utilize beast modes to calculate the period over period (in your case week over week). You can read more on this…