GrantSmith Coach

Sorry, forgot to have you pass in the 'm' and 'n' flags to the regexp_replace function to tell it to match newline characters with the . reference. m: Multiple-line mode. n: The . character matches line terminators. REGEXP_REPLACE(`text`, '^.*card_name: (.*)\nmeasureable_id:.*', '$1', 'mn')

Yes. That would affect the regular expression as there's a newline character prior to your measure_id. Try this version: REGEXP_REPLACE(`alert.message`, '^.*card_name: (.*)\nmeasurable_id: .*$', '$1')

Magic ETL formula tile should allow this: REGEXP_REPLACE(`alert.message`, '^.*card_name: (.*) measurable_id: .*$', '$1')

You can use a formula tile in Magic ETL to do a regular expression replacement REGEXP_REPLACE(`Team`, '( - EMEA)|( - AMERICAS)|( - GLOBAL)|( - APAC)', '') Alternatively you can chain REPLACE functions together in a Beast Mode: REPLACE(REPLACE(REPLACE(REPLACE(`Team`, ' - EMEA', ''), '- AMERICAS', ''), ' - GLOBAL', ''), '-…

So you just want to drop the last section after the last hyphen?

If your format is split by a hyphen you could use SPLIT_PART to get the first part of your string: SPLIT_PART(`Team`, ' - ', 1)

You'll need to share the dataset with the user so they can see it. PDP is applied after they access the dataset but need it shared to see it in the list first.

Has the dataset been shared with the user?

You can utilize the DENSE_RANK window function and a MOD function to calculate alternating lines and then conditionally set your row coloring. MOD will return either 0 or 1 depending if it's even or odd to allow you to identify alternating rows. MOD(DENSE_RANK() OVER (ORDER BY MAX(`User Pseudo ID`)), 2) Sort your table…

Try pivoting your data so that you have a year column, month column and a value column. Then you can use the Month as your x-axis and the year as your series with the value as your y axis.

Views aren't scheduled to run, they're run when they're accessed. They're not materialized / saved in an actual dataset. If you're looking to materialize the view and store the contents of the view on a daily basis you can use it as an input in a dataflow and just write out the contents to a dataflow dataset.

You wouldn't want to order by your header as that'd have all the 0s first then the 1s so likely your row is at the end of your dataset. Try sorting based on your Row_Number field instead.

Try using a formula tile to set the value of a column to be 1 if it's = 'market' and 0 if it's not (or whatever logic you need to mark it as the start). Then use the rank & window to do a running total of the column.

You need to pass in the correct format string when converting your string to a date STR_TO_DATE(`date`, '%c-%e-%y') There a lot of references on format string codes on the internet but this is one you can reference:…

You can use the SPLIT_PART function. SPLIT_PART(`Name`, ' | ', 1) This will get the first value in your string split by the ' | ' delimiter.

You can write two beast modes and then join the data back on itself to get previous month and 2 months ago. You'll need to format you data in a long format instead of a wide format like you have in your example. Something like: Company | Month Date | Value A | 2023-01-31 | 1 B | 2023-01-31 | 7 Last Month: LAST_DAY(`Month…

Currently there isn't a publicly facing supported API which would allow you to programmatically edit a Magic ETL. You could inspect the network traffic as you're editing and saving the API and attempt to replicate it

Is 12-1-21 the value of your `Month Date` column? Is this a date column or a string column in your dataset?

You can also use a formula tile and a regex to do this as well: REGEXP_REPLACE(`Field`, '.', '')

Errors like these don't give much customer facing information. I'd recommend reaching out to Domo Support as they can look in the back end and get more information about the error.

You can utilize a formula tile in a magic ETL dataflow or just use a beast mode. I'd recommend utilizing the Magic ETL as that will take most of the processing and allow cards to load faster.

You can use DAYOFMONTH instead of DAYOFWEEK First of the current month: CURDATE() - INTERVAL (DAYOFMONTH(CURDATE()) - 1) DAY

How are you utilizing the beast mode? Are you attempting to convert the value somewhere to a boolean? Because you're using the first of the week you could simplify the beast mode to something like: CASE WHEN `Week Date` = (CURDATE() - INTERVAL (DAYOFWEEK(CURDATE) + 6) DAY) THEN 'Last Week' ELSE 'NOT' END

@NathanDorsch I'm referring to the Java CLI tool that Domo provides.

Try something like this: CASE WHEN (`Week Date` + INTERVAL (7-DAYOFWEEK(`Week Date`)) DAY) = (CURDATE() - INTERVAL (DAYOFWEEK(CURDATE)) DAY) THEN 'Last Week' ELSE 'NOT' END The first part is is adding days to the week to get the last day in the week. The second half is calculating the end of the week based on the current…

Ah, in that case you'd want to use the fixed function to be able to ignore filtering. Which date field is driving your chart? Is that the Milestone date? In your beast mode you're missing the order by which makes it a running total. Without it it's just a grand total of your entire dataset (or partition if you have one…

Did that user have access to the data fusions / was the data fusion shared with them? "Everyone with DataSet access" should include everyone who has the dataset shared with them.

You can utilize a window function to do this: SUM(COUNT(`Issue ID`)) OVER (ORDER BY `Milestone Date`)

I've done a writeup in the past about custom period over period which you could utilize in this case. I'd recommend filtering for just the first of the month instead of all date and grouping your data on a monthly basis before doing the joins but you can read up more on this here:…

You'll need to reach out to support to have the connector team look into this.