Comments
-
I've outlined an alternative method here: You'd need to use 0 instead of NULL when calculating your column field.
-
You can join your original dataset to the new dataset based on your ID. Then use a formula tile to see where the status fields differ and then populate the updated date using CURRENT_TIMESTAMP() function.
-
You could implement your own visualization utilize a Domo Brick some Javascript packages. Alternatively have you thought about utilizing drill paths to narrow down your tables?
-
Hi @SarahR365 I'd recommend starting with as it outlines the Sandbox process and how you can promote connectors and share with users from your current dev instance to your new prod instance.
-
what you’re referring to is the special lastvalue parameter in a workbench query. Some basic information can be found here as an example you can ignore the fact that this is OLAP Cube documentation but just search for lastvalue to see the documentation on it. This way you can track the latest id you’ve pulled in and have…
-
what is your setting for the regex body? Are you putting anything in the body when sending the email? Does it work if you put in NONE for the regex body setting?
-
You can attempt to do your DATE_FORMAT call but encompass it inside of an IFERROR call to filter out the rows where you're note able to convert to a date with your format. IFERROR(EXPR1,EXPR2) If the evaluation of expr1 does not produce an error, IFERROR() returns expr1; otherwise it returns expr2.
-
@Sean_Tully - I've used that method as well to convert a string to an integer. I've found it works well.
-
The DomoStats connector offers a Workbench report you can pull which has a lot of the job metadata assocaited with it.
-
CASE WHEN `ItemName` LIKE '%A%' OR `ItemName` LIKE '%B%' OR `ItemName` LIKE '%C%' OR `ItemName` LIKE '%P%' THEN 'Ignore' ELSE 'Keep' END You can use the LIKE statement to see if your string contains other characters. Alternatively you can use a REGEXP_REPLACE in Magic ETL formula tile: CASE WHEN REGEXP_LIKE(`ItemName`,…
-
You'd need to write the changes to your dataset back to Google Sheets so the orginal source is updated. You can leverage a Google Writeback connector within a Dataflow.
-
You're deafaulting to Normal if the Donors is null. You can add an additional clause in your case statement to handle NULL values: case when value < lower_bound or value > upper_bound or value is null then 'Outlier' else 'Normal' end
-
Summary numbers can accept some simple HTML coding so you can change the font size using HTML.
-
REGEXP_REPLACE(`field`, '^.* ([^ ]+)$', '$1') * 1 this should find the last value in your string after the last space. Multiplying it by 1 will convert it to a number. Will the numbers be always at the end or anywhere in the string preceded by AUD?
-
this is because when you’re concatenating everything together it ends up being a string and it loses the formatting. You’ll need to implement your own formatting as part of your beast mode.
-
Typing on mobile is hard :) removed → recommend.
-
You can utilize the onFiltersUpdate function within your domo brick to capture the event when the filters are changed.
-
it’s likely a backend issue where Domo is having issues saving your dataset due to the schema changes. I’d removed logging a ticket with support
-
If you want to filter on the actual numbers that it needs to be part ofyour dataset. An alternative method for doing period over period is to restructure your data calculate the period over period in a beast mode save it to the dataset and then filter that value. I’ve done a write up how to do this here:
-
you can change the interaction of the card on your dashboard to drill in place to allow users to drill but keep them on the dashboard. Just edit the dashboard and for each affected card change the interaction from the cards wrench menu to be drill in place
-
Are you including the user_type parameter that's outlined in the GoHighLevel API Documentation?
-
There's several functions which aren't listed in the function list but do still exist. Hopefully Domo gets it updated.
-
CONCAT(SPLIT_PART(`url`, '/', 1), '/', SPLIT_PART(`url`, '/', 2)) SPLIT_PART will get the values with the data split out by a specific character. It's undocumented in the UI but is accessible. Concat then takes those two values and combines them together with the / inbetween
-
due to how Domo processes data it needs a record for each day of the subscription. Can you get a record for each date and the aggregate the totals in an ETL per day or do you need to filter your data?
-
Another potential alternative is to convert your dates into unix timestamp (TO_TIMESTAMP) which would be a number, this would then allow you to run a median on the number and then just convert the median back to a date (FROM_UNIXTIME)
-
You can have a bit more flexibility if you restructure your data using a date dimension table with custom offsets so you can then filter on any time frame and get the 12 months ago for the exact same timeframe instead of just the current timeframe. I've done some write-ups in the past about how to get this configured and…
-
Correct, you'd likely want the full page URL to accomplish this.
-
I'd recommend logging a ticket with Domo support to have them look into the connector and see if they know why their connector wouldn't be pulling in the data.
-
In Google Analytics, a landing page is the first page that a visitor or audience lands on when they visit your website. It can be any page on your site, such as a help page, contact page, home page, or blog post. The landing page is where a user initiates a session on your website. The full page URL is the page that the…
-
This is a great idea. I'd add it to the Idea Exchange.