GrantSmith Coach

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.

Correct, Magic ETL has network restrictions with the exception of Writeback tiles. You'd need to import your data using a connector first and then process it with Magic ETL

You'll need to reach out to Domo Support to have them possibly remove these.

@RocketMichael If those are your only records in your dataset you can utilize a Magic ETL to add a constant to your dataset (Join Column, value 1), then filter your data for just 'Current Week'. Take that filter and join it back to your original dataset with the constant and join both on the constant. This will join each…

How is your rank value being calculated in your dynamicRank table?

Currently it's not supported with a Date type variable. It'd be a great idea for the idea exchange.

Are you using a beast mode or an ETL to calculate your rank? Could you post the code?

Should be DAYOFMONTH

`Date` - INTERVAL (DATOFMONTH(`Date`) - 1) DAY

Have you tried using an unpivot in an Etl to convert your columns to rows then group by your metric column and count the number of values?

When you’re filtering and including a and b your lag function will pull data from metric a and b. You’ll want to add PARTITION BY ` metric ` to your lag statements to make sure you’re not jumping metrics with the lag

If you go to the bottom of the post there's an updated version (under Addendum) of JSON code you can copy and then paste into the ETL canvas area to automatically populate the necessary tiles and logic. You'll just need to name the output dataset and select the correct datasets for the input datasets. There are two…

You could use a Magic ETL 2.0 dataflow and group your data on the start_date, model and inventory_units and select the MAX ob_modified_date then do an inner join from your original input dataset and the output of the group by based on the start_date, model, inventory_units and ob_modified_date.

You can use the aggregation on your value field in the Single value card and set it to maximum:

pydomo/ds_update doesn't support append at this time. You could configure a recursive dataflow to append your data.