zcameron Contributor

@Domomon - If you're asking about copying actions from one Magic ETL dataflow to another, yes it is possible. Just select multiple actions on your ETL canvas and choose the option for Copy to Clipboard. Then navigate to the target Magic ETL dataflow and hit your normal keyboard paste command. I hope that helps!

For the sake of being thorough, you're grabbing the dataset ID from the URL when viewing the details page of the dataset in Domo, right? Any chance you could post a screenshot of the command and response? Don't post anything showing your connection credentials, of course. Just the export-data command.

Does it do that if you try it with a different, smaller dataset? Also, what type of dataset is the the one you're trying to export (dataflow output, view, connector dataset, etc.)?

Did you create an access token to use with the connect command? You can do that in the admin section of Domo. Once you have that, you can use the connect command like the following example: connect -s myinstance.domo.com -t aflasdkfn0923ro2ffaoafo23oawefoe2 Note that the domain contains ".domo.com". After you're connected,…

The query command will export up to 1M rows at a time. I guess that's still a lot of iterations to get to all your data if you have 257M. Is this a one-time operation or something that will be ongoing? Something else to consider might be the Domo CLI tool. It has an export-data command that can handle larger datasets. I…

I tried the following code this morning with a successful outcome: from pydomo import Domo client_id = '<client_id goes here>' client_secret = '<client_secret goes here>' api_host = 'api.domo.com' dataset_id = '<dataset_id goes here>' outputFileName = 'output.csv' domo = Domo(client_id, client_secret, api_host) data =…

Have you tried using the ds_query function of pydomo? It allows you to run a query against the dataset and return the results. If you have something like a sequential id or a date you could use that to pull sections of the data and export them. It might look something like this: data = domo.ds_query(dataset_id, 'SELECT…

@lb1234 - Unfortunately, I've not created this type of calculation for other time frames. Calculating the start and end days for the quarter version could be pretty complex. I would definitely look at an ETL/join-based solution for that. For the year calculation, you know the total will either be 313 or 312 because there…

@lb1234 - It is a pretty complex calculation, isn't it. I wish it were a little easier to read for you. The calculation is subtracting 2 days for each week in the month to account for Saturdays and Sundays. I believe the equation should work if you were to change the "2"s to "1"s. You could also eliminate the "* 2" part of…

This is super helpful, everyone! I really appreciate the input. I'm adding all of these topics to our discussion pool and will work with my team to plan ways to incorporate them. If other ideas come up, please keep them coming!

I love seeing other users' use cases and innovative ways that Domo is being used. Dojo is a great place to connect with others, learn about Domo, and get questions answered.

I wonder if we're seeing some whitespace after or before the value. What if you added in a check for that like this: ^.*\{\s*"value"\s*:\s*"(.*)",.*\}.*$

Very odd... It worked in my testing with the example you provided. Can you post some screen shots of what you're seeing now, or give some more detail around how it isn't working?

Sorry, my fault... I forgot to escape the curly braces. The RegEx engine that MagicETL uses will require that. ^\{\s*"value"\s*:\s*"(.*)",.*\}$

I would suggest using this RegEx under the term to search for: ^{"value"\s*:\s*"(.*)",.*}$ And put $1 in the Replace field. You'd only need one entry that way. It will capture everything after the colon and quote and before the following quote. Can you give that a try and see how that goes?

Google has a good API for doing this. It's the same one used by Google Maps. https://developers.google.com/maps/documentation/geocoding/start

The help icon I was referring to in the Domo instance, not in Workbench. Sorry for the confusion.

user18108, This sounds like an issue that would need to be investigated by Domo Support. They have workbench experts that could help get to the bottom of it with you. From your Domo instance, click the question mark in the top right and then click the Support link in the top right of the help center. You can create a…

CdrMarks, The simplest way would probably be to create a beast mode that does a distinct count of the client id. For example: COUNT( DISTINCT `client id`) "client id" would be whatever field you are using to aggregate the records in the table into one row per client. You could then use that beast mode in the summary…

hamza_123, The way to do what you're looking for is to include the output of the dataflow in an input to the same dataflow. This is referred to as a recursive dataflow. It takes the output of the previous run of the dataflow and brings it back in as an input. You can then append the new data to the recursive input, filter…