bdavis Contributor

I'm not sure if you're trying to determine if they have the same number of columns and names, or if the data needs to be the exact same in both dataframes. Some sample of your data and output helps a bunch as well. Also R is not Ruby, they're different languages. ;) Now, I don't use R in Domo, but I use it outside of Domo.…

The formatting of the SQL query is a pain in the butt, but I use it frequently. The real limitation to be aware of is that it will cap at 1 million rows. I think there is a way to get CSV results, however it's not from the query API call, but from another one. I can't recall the exact name off the top of my head, but the…

Just as an FYI, I don't believe Workbench is ever limited in functions from what I've encountered. My impression is that Workbench is just relaying the query to the database, so the function usage is limited by the local database system and version.

@Gor_Gonzalez I believe @jaeW_at_Onyx is saying to choose the file that exists today. Then, click edit, remove the filename only and replace it with *.csv (or whatever extension you're using)

Correct me if I'm wrong, but if your rows per ID can technically be an infinite amount, then the only way to do this would be using something like R or Python and the resulting set would need to be constantly overwritten because your schema would change all the time. For example, today the max rows per ID is 12, tomorrow…

If you left join the JOBS set with REVENUE set on location and year, you will end up with a column that shows the same revenue for every row in that location and year. You may be able to use this to show what you want if you want to keep the details about each individual job. If you're only looking for the number of jobs…

There is a solution for this - contact your CSM and inquire about their data stacker. 

Incase anyone sees this, the file was only shared via URL. Once that was changed to Direct Access everything worked.

There's a Domo Governance app that lets you create about 8-12 datasets about pages, datasets, dataflows, cards, etc. We use these to help us create cards showing duplicated names/similar names, datasets that aren't following our naming scheme, orphaned cards, etc. The inputs for dataflows is in there as well.

When this happens to us, I will go into the dataflow that's appending the data and add a transform (SQL) to delete the rows I need to delete, or add a filter (ETL) to filter out the rows I want to remove. Then, after I run the dataflow once, I go in and delete the filter/transform. If the rows that came in for those dates…

We try to attach an employee ID value into every possible system we have. This way when we bring in the data into Domo, we have a key to tie all employee records together. Doing this also allows us to create "error cards" where we can identify mismatching information for an employee that may exist between our different…

Incase this helps anyone coming to this thread, as of 2/5/2020 the version of MySQL in Domo appears to be: 5.6.28-76.1-56 Current version of MySQL available to public: 8.0.19 This way you can check what functions may or may not be available.

There's not much else going on in the dataflow, especially nothing that adds complexity. I don't know if this is an option for you, but have you thought about decreasing the size of the input set? Perhaps increase the frequency of the import and only bring in rows added since the last import? I don't know how wide your…

EDIT: I believe I have resolved this. My class object was data.frame tbl_df and tbl. When I changed this to only data.frame it import correctly.

Domo seems to be running MySQL 5.6 which doesn't have those regex functions. I don't know if they plan to upgrade to MySQL 8.0 which does have native regex support but it may be something you want to talk to your rep about, or at the very least, keep your eye on any patch notes/news releases.

@cwolman wrote:Could you share your sql? Sure! SELECT i.id, i.resolve_time, u.department_id FROM issues i left join users u on i.uid=u.id WHERE i.resolve_time > '!{lastvalue:resolve_time}!' ORDER BY i.resolve_time ASC EDIT: I feel like it's not interpreting the reaplcement value properly, comparing it to the datetime…

This is a workbench job, and I noticed the issue because the source data did change, but the workbench import did not pick up the new rows. 

We're also interested in this. Perhaps it's coming when they unlock the ability to use any color for a background?

FYI this is now available.

No, different results. This is a bizzarre scenario, I'm really stumped. I've done the same steps on a local MySQL installation and I get expected results. I've done it in R and gotten expected results. I'm not sure what's unique about the dataset/dataflow on Domo.

I downloaded the dataset that has the duplicate values, loaded it into R and found duplicate rows (the exact same ones in the daily export). There's certainly no calculated field happening. I truly can't explain it. Hopefully support has an idea.

It's in the full output. I've also seen the previews displaying very incorrect data but generating the proper output. I'm convinced something else had to occur (even though these particular queries are as simple as you get). So I'm going to nuke it all, push the historical data, and recreate the DF again to see if it…