ArborRose

Discussions

MySQL Workflow
Can Domo's mysql handle more than 500k records? It shows the import can only go to 500k but I'm assuming that is for previewing data not actual processing. I attempted to output only five rows from a million record dataset and it ran for 30 minutes before I cancelled the process.
CLI move-data needs to move not copy
Using the CLI move-data command, I set up a dummy dataset to move rows. The rows copied but did not remove from the source.
Allow empty datasets with future date ranges
We pull two years transactions plus the current year from an api using JSON connectors. I've found it more reliable and efficient to break the data into smaller pieces. For the past years, I have created a connector for each - refreshed once per month. For the current year, I am splitting the year into Q1, Q2, Q3, and Q4.…

MySQL Workflow
Can Domo's mysql handle more than 500k records? It shows the import can only go to 500k but I'm assuming that is for previewing data not actual processing. I attempted to output only five rows from a million record dataset and it ran for 30 minutes before I cancelled the process.
CLI move-data needs to move not copy
Using the CLI move-data command, I set up a dummy dataset to move rows. The rows copied but did not remove from the source.
Allow empty datasets with future date ranges
We pull two years transactions plus the current year from an api using JSON connectors. I've found it more reliable and efficient to break the data into smaller pieces. For the past years, I have created a connector for each - refreshed once per month. For the current year, I am splitting the year into Q1, Q2, Q3, and Q4.…