Comments
-
You might be able to leverage pfilters to pass in your filters in your URL to recreate the filtered view you're looking at. https://domo-support.domo.com/s/article/360042933114?language=en_US
-
Try this: REGEXP_REPLACE(`string`, '^.*(\d{2}-[A-z]{3}-\d{4}).*$', '$1') You need to replace the entire string not just the substring. This is why there's ^.* and .*$ to match anything before and after the date value respectively.
-
You could also utilize a regular expression to modify your string and automatically insert the HTML code. Something like this might work assuming your values are actual colors (untested) REGEXP_REPLACE(`RAG History`, '.*((Yellow)|(Red)|(Green)).*', '<div><span style="color: $1">$1</span></div>')
-
You could utilize an HTML table and utilize HTML code to colorize each value in your string. You'd need to CONCAT the HTML code together with your values and conditionally set the color. I've done a previous writeup on this here:…
-
Since you can't do conditional joins within Magic ETL 2.0 what you can do is add a constant to both datasets in your ETL and call it Join Column with a value of 1. Then do a join on both datasets on the join column. Then feed that into a filter tile to filter where company_holiday_date is BETWEEN your date_start and…
-
You're not able to see what API script was called to import the data into Domo.
-
You can update the schema (specifically the dataset name) using the update method and updating the schema. There's an example in pydomo: https://github.com/domoinc/domo-python-sdk/blob/dacdee87d9e798f4c83f270b38c8ea2b1b6c7923/examples/dataset.py#L32
-
For another option: STR_TO_DATE(`y` + 1, '%Y') - 1 '%Y' - defaults to the first of the year +1 Add a year -1 Subtracts a day y here is the year in integer format. In other words, it's converting the given year to be the first day of the next year then subtracting 1 day to get the last day of the given year
-
You could attempt to utilize a MySQL dataflow which would give you a bit more flexibility in this case but will execute slower. Here's an example I found which you could use as a template: https://stackoverflow.com/questions/5041537/mysql-csv-row-to-multiple-rows
-
This appears to be a bug. I'd recommend reaching out to support and submit your issue.
-
There isn't a way to programmatically do this but you can utilize the SPLIT_PART function in a formula tile to pull the specific one you want. You'd need to have multiple formula tiles to pull the different number out then stack everything back together with an append rows tile. You'd need to do this for as many different…
-
You can move the cards by going under Admin - Cards and then filtering for a specific page you want to take cards from, select all the ones you want to move and then select to move them from the wrench in the upper right.
-
I believe the Alpha Vantage connector is no longer usable as it's fully paid now and not accessible via Domo. You'd need to get stock information from a different source. You could utilize a Google Sheet and then use the GOOGLEFINANCE function to pull in the associated stock information into the sheet and then pull that…
-
Currently there isn't an option to update the frequency using PyDomo.
-
You can utilize the RANK window function in a beast mode. Something like: RANK() over (PARTITION BY `List` ORDER BY SUM(`All Total`))
-
You'd need to take a daily snapshot of the domo stats to calculate the row count each day and then use those values to graph the row size day over day. You can use a recursive dataflow to handle this or alternatively set the stats dataset to append and use the _BATCH_LAST_RUN_ field as your timestamp date. To get the…
-
You can use the HOUR function to return a value between 0 and 23 to filter on (in your case 9-17). CASE WHEN HOUR(`Timestamp`) BETWEEN 9 AND 17 THEN 'Keep' ELSE 'Exclude' END If you want to convert the times in a 12 hour format you can use the DATE_FORMAT function with a specific format string DATE_FORMAT(`Timestamp`,…
-
You might be able to utilize the Domo ODBC driver. https://domo-support.domo.com/s/article/360043437693?language=en_US
-
If you're speaking to trellis charts that option is still there (this is from a bar chart)
-
You'll want to put in the name of your instance and not your website. Enter your customer name. Your customer name is the part in the URL that before .domo.com. Ex: If your Domo instance is located at https://some-customer.domo.com, then your customer name is some-customer.
-
No, I think it's been out since Dashboards have been out.
-
If you Edit Dashboard, you can select from the Edit Content menu - select Change filter exceptions and uncheck the box that says Allow global date. This will prevent the page data filter from filtering your card.
-
Alternatively you can use can type ``` and a code block will pop up for you.
-
I'd recommend using an ETL for things like this as you already have your original values. You just need to filter them where your value isn't null then join them together based on the 1st column in your example.
-
That's how dates data types are formatted within Domo. If you're wanting to change the format you can use a DATE_FORMAT function in a beast mode to convert it to a string by passing in the appropriate formatting string. See https://www.w3schools.com/mysql/func_mysql_date_format.asp As for calculating the differences…
-
It's because your data is on two separate rows. You'd need to either do it in a beast mode on the card or utilize an ETL to combine the data together so you have both records on the same row.
-
You can use the LEAST function to select the smallest value of dates LEAST(`Observation Date`, `Admit Date`) If the observation date is null then you'll want to default it to the admit date via a COALESCE or IFNULL: LEAST(COALESCE(`Observation Date`, `Admit Date`), `Admit Date`)
-
Looks like you're not passing in the domain with the URL correctly. Without seeing your code I can't tell you exactly but look at where you're specifying which instance / domain you're using to connect to.
-
Yes as it's not in the exclusion list
-
Regular expressions are your friend in this case. You could ignore any non-alphanumeric characters in your string with something like this with a formula tile: REGEXP_REPLACE(`field`, '[^a-zA-Z0-9]', '') [] = Group of possible characters ^ = NOT a-zA-Z any letter 0-9 = any digit