Streamlining Output Settings for Ocean.io: A Request for Easy Toggle Feature

Dom Michel · 2024-09-27 05:37:31.7816+00

When you have multiple outputs such as in you will have choose each setting for each output. It would be amazing if the settings put in for the first output can be toggled on for every other entry. Right now its faster for me to not do all of this, but export the whole file and have GPT create a separate CSV and import this to a table

Streamlining Output Settings for Ocean.io: A Request for Easy Toggle Feature | Clay

7 comments

· Sorted by Oldest

Daniela Debebs (Clay)
·
·
Hey Dominique! Thanks for sharing✨. We're always looking to make the product better and this feedback is super helpful for us. We're going to pass this over to our product team so they can better evaluate things and see if/where this might fit into the roadmap as a future improvement. Just to confirm, you'd like the selection for the first entry to auto-populate for every other entry? Can you share a bit more info about how you currently export those fields? For context, each output still gets returned if not selected and can be written to a new table for export, with the Write to table integration. We want to ensure your current process is as seamless as possible.
Dom Michel
·
·
"Just to confirm, you'd like the selection for the first entry to auto-populate for every other entry? Can you share a bit more info about how you currently export those fields?" yes, precisely. As far as I know, I have 2 options:
1.
I write all of them from Table 1 to table 2, and then do a lookup value, if I want to reuse them in table 1
2.
I choose for each company found, that I want a new Column to be created with lets say Name, Domain, Linkedin
Both options take a long time, while option 1 be a bit faster it still requires the creation of a new table and is not precisely elegant :)
Channeled
APP
·
·
Hey there - just wanted to check in here to see if you needed anything else! Feel free to reply back here if you do.
Dom Michel
·
·
yes if you got a better solution than mine, please show me 😄
Daniela Debebs (Clay)
·
·
Hey Dominique! Thanks for the reply. Got it. We passed this along to the product team to evaluate. In the meantime, for your workflow, the write to table integration is still the best way to automate each record being mapped out into separate rows and columns in a table. Once setup, that workflow can be duplicated for new tables in your workspace. Can you confirm which values you currently need to run Lookup for in table 1 and why those records need to be reused in table 1?
Channeled
APP
·
·
We haven't heard back from you in a bit, so we're going to go ahead and close things out here - feel free to let us know if you still need something!
Channeled
APP
·
·
Hi Dom Michel! This thread was recently closed by our Support team. If you have a moment, please share your feedback:

Daniela Debebs (Clay)
·
·
Hey Dominique! Thanks for sharing✨. We're always looking to make the product better and this feedback is super helpful for us. We're going to pass this over to our product team so they can better evaluate things and see if/where this might fit into the roadmap as a future improvement. Just to confirm, you'd like the selection for the first entry to auto-populate for every other entry? Can you share a bit more info about how you currently export those fields? For context, each output still gets returned if not selected and can be written to a new table for export, with the Write to table integration. We want to ensure your current process is as seamless as possible.
Dom Michel
·
·
"Just to confirm, you'd like the selection for the first entry to auto-populate for every other entry? Can you share a bit more info about how you currently export those fields?" yes, precisely. As far as I know, I have 2 options:
1.
I write all of them from Table 1 to table 2, and then do a lookup value, if I want to reuse them in table 1
2.
I choose for each company found, that I want a new Column to be created with lets say Name, Domain, Linkedin
Both options take a long time, while option 1 be a bit faster it still requires the creation of a new table and is not precisely elegant :)
Channeled
APP
·
·
Hey there - just wanted to check in here to see if you needed anything else! Feel free to reply back here if you do.
Dom Michel
·
·
yes if you got a better solution than mine, please show me 😄
Daniela Debebs (Clay)
·
·
Hey Dominique! Thanks for the reply. Got it. We passed this along to the product team to evaluate. In the meantime, for your workflow, the write to table integration is still the best way to automate each record being mapped out into separate rows and columns in a table. Once setup, that workflow can be duplicated for new tables in your workspace. Can you confirm which values you currently need to run Lookup for in table 1 and why those records need to be reused in table 1?
Channeled
APP
·
·
We haven't heard back from you in a bit, so we're going to go ahead and close things out here - feel free to let us know if you still need something!
Channeled
APP
·
·
Hi Dom Michel! This thread was recently closed by our Support team. If you have a moment, please share your feedback: