GrantSmith Coach

Currently Domo doesn't have a way to remove the borders. I'd recommend adding it an idea in the idea exchange for the product team to possibly review and have other users vote on.

Start with the calendar dataset from the Domo date dimension connector and left join your dataset to it on the date using a dataset view or ETL. Then use the calendars date field instead of your own. Left join will cause your missing data to be null but still have the dates from the calendar

Are these two users in the same group / need the same access? Have you thought about configuring a group and then sharing the cards with that group instead so any future users will get the access when added to the group?

Likely no, it won't work if it's not a direct link to download the file. You'll have to figure another way of getting the data out of their system (perhaps they have an API you can access?).

In the email connector have you configured it to attempt to download from a link? https://domohelp.domo.com/hc/en-us/articles/360042931954-DataSet-via-Email-Connector#3.1.

Depending on the size of your dataset and the processing needs you can do this in either MySQL (simpler but slower) or MagicETL (more complex, possibly slower depending on dataset size). MySQL dataflow allows for conditional joins so it's a simple query: SELECT a.`ipaddress`, a.`ipnumber`, `Country`, `Region`, `City` FROM…

@Casey_Tsujita Domo doesn't exactly support recursive queries as you've mentioned because they're on MySQL 5.6. For my use cases I ended up utilizing a Magic ETL dataflow and then self-join the dataset to itself to go down the recursive list and did it 20 times to handle up to 20 levels deep. It's not the most elegant…

You can utilize a formula to calculate the most recent Monday for the week: `Date` - INTERVAL (CASE WHEN DAYOFWEEK(`Date`) = 1 THEN 6 ELSE (DAYOFWEEK(`Date`) - 2) END) DAY A week prior: `Date` - INTERVAL (CASE WHEN DAYOFWEEK(`Date`) = 1 THEN 6 ELSE (DAYOFWEEK(`Date`) - 2) END) DAY - INTERVAL 7 DAY DAYOFWEEK returns a…

CASE WHEN `model` IS NULL THEN 'Ignore' ELSE 'Include' END You can then take that beast mode and filter it on your card for Include

Magic ETL isn't performing SQL under the hood so there's no SQL to extract from the ETL. It's all done using Apache Spark. You'd need someone to look through your ETL logic and then write then translate it into SQL.

You can't dynamically tell a page to filter on different values (filter on shift 1 / filter on shift 2) depending on the time of the day. You'd likely need to have a beast mode that calculates the shifts as either "Current" or "Other" and then have a default page filter where shift = Current.

Under Chart Types select Tables from the drop down. You're currently looking at the Popular charts. It'll be under Tables.

You can utilize a custom date dimension / period dataset to calculate the different metrics for each date and then utilize a beast mode to create the columns for last month / last year / quarter etc. I've done a write up on this method here:…

@louiswatson You can utilize a Magic ETL with the Alter Columns tile to convert the datatype of each of your columns and then use that in your cards instead of using beast modes / calculated fields. This way it's only done once and you can build your cards off the converted dataset instead of creating multiple calculated…

Assuming you're using the Phoenix DDX Scatter plot example here but you can specify the colors you're graphing in the options dictionary and then pass that into your Chart call when charting your graph. const customColors = [ '#002159', '#03449E', '#0967D2', '#47A3F3', '#BAE3FF' ]; var options = { colors: customColors,…

You'll need to reach out to Domo Support as this is likely an issue in the back end storing the data after it's received your data.

Did you update the schema via the API or just add the new field to your dataset you're attempting to upload? You need to make sure the dataset schema includes the new field otherwise it'll fail. Domo has an example of this in their pydomo documentation: What program are you using to access the APIs?

I've had an idea in the Idea Exchange for a while to have Domo allow admins to just go directly to the page without having to request access to the page. Feel free to up vote it here: https://dojo.domo.com/main/discussion/53435/add-grant-access-button-to-pages-for-admins

Alternatively just allow admins to automatically load into the page without having to request access or have it added to the page list.

\r and/or \n should work but it appears they don't. You can explicitly pass an enter character in your forumla tile for the time being: REGEXP_REPLACE(`address`, '~', ' ')

Is it the querying that's taking a long time or the data upload to Domo that's taking a long time? Are you joining to another table causing the null values? If so when you removed the null column did you only exclude the field from the query itself, uncheck the columns to upload in the schema or remove the table join as…

In your Magic ETL - Group by the Employee, get the Max Sales, join that to your original dataset based on employee and sales amount. That will get you the date without having to use the aggregate on the date field.

Can you direct users to the same page / dashboard with a dataset containing all of the different users data but apply PDP to the dataset to filter it so that they only see their data and not anyone else's?

You can use a beast mode in analyzer or a formula tile in Magic ETL 2 and the COALESCE function to change NULL values to another value: COALESCE(`dt`, '2022-02-02')

@Jmoreno You can't do a mass update via the UI. If you wanted to write a script to interface with the APIs it would be an option but would require a very technical resource.

Because it's using a client ID and Secret and using the public API endpoints you'll likely need to set host domain to be api.domo.com

Hi @ravikirand You can sync an AppDB to a dataset in Domo. You need to set the syncEnabled value to true and define a dataset ID and schema. You can read up more on it here: https://developer.domo.com/docs/dev-studio-references/appdb

@willrnt The the BATCH_LAST_RUN is built into the API connector code to populate when the data is imported. You'd have to replicate that in your API program. An alternative is to utilize an ETL to update whenever your dataset is updated to automatically add the timestamp.

What browser are you using? Have you tried using a different browser?

The upload-s3 command doesn't support headers and will import the entire file. If you don't want the headers you could either remove the headers from the initial file or utilize an ETL to strip out the header information rows, update the column data types to the correct types and then append it to the main dataset.