GrantSmith Coach

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.

Currently there isn't a dataset with this information. I'd recommend adding it as an idea to the idea exchange.

If you can have all of the records from your top dataset in your output dataset then you can do a left join on your dataset instead of an inner join. Then in your card do a count of the id file from your TEST dataset to get the total records that match if you just want the entire count then I’d recommend running your TEST…

This KB article may be of help where it outlines the different functions and their formats: SUBSTRING(`Column`,[START POSITION],[NUMBER OF CHARACTERS TO EXTRACT])

I'd recommend structuring your data with a date dimension so you can easily determine the last year's value. I typically do this with the Domo date dimension dataset. I've written up on how to do this before here:

You can utilize the STR_TO_DATE function and a date format string to convert it to a date. STR_TO_DATE(CONCAT(`Year`, '-',`Month`), '%Y-%m') I'm adding in a concat to add the year and month together as a string to then format. From the documentation: STR_TO_DATE Converts strings (that Domo does not recognize as dates) from…

Have you tried setting the update method on the connector dataset to be Append instead of Replace so it'll append each day's run to your dataset? Alternatively if you're worried about duplicated records you could utilize a recursive dataflow (KB Article: ) to filter out duplicated records based on the logic you have.…

Are you including the 'api' portion of your url in your request?

this isn’t possible as all the filters are shown. You could do the filtering in the cards for the values you don’t want displayed in the filter bar but you would lose the flexibility to filter on those values on the page if you ever needed to

You can create separate beast modes for your different values and drag each of them on your graph CASE WHEN `engagement_status` = 'ES_user' THEN `value` END

You can do a running total over time using a window function. Something like this in a beast mode might work for you. SUM(SUM(`field`)) OVER (PARTITION BY `fiscal_year` ORDER BY `date`)

You can use a CASE statement with a LIKE operator to determine if the word Delivery is in your string: CASE WHEN `field` LIKE '%Delivery%' THEN 'True' ELSE 'False' END If you want to have it case insensitive you can use ILIKE instead of LIKE

When ingesting data Domo assumes UTC and when it gets to a visualization (in a card or on the dataset data tab) Domo will then convert your data to the Timezone company setting. Are there any other transformations happening on your data during processing or just converting it to a timestamp? Have you tried using the…

Use a Magic ETL with a formula tile to make the value null if it's -3: case when `field` <> -3 then `field` end You can then feed that into an alter column tile to change the type

I don’t believe the beta works with dataset views as an input data source which is why you’re seeing that error message. I’d try outputting it to an actual dataflow dataset and try again. I’d also recommend giving the feedback to the beta team as well as I’m sure they’d find that valuable