Proposal to Increase Column Limit in Tables from 70

·

I know you’ve probably heard this a bunch already, but increasing the total limit for columns in a table from 70 would be amazing across the board.

Arturo O.
·
·
Hey Devin!! Appreciate the feedback, shared with the team. There have been discussions so perhaps there may be something coming. Of course, we're always interested to learn more to understand this request— could you share a bit more what your workflow looks like and where you're running into this constrain? Appreciate it!
Devin M.
·
·
Two things I see right off the top.
1.
If you’re running a few waterfalls and you want the table to be a template for future projects your columns can quickly run out.
2.
Combine that with outputs from claygent with multiple outputs/json outputs so that you can later combine custom messaging and its pretty easy to hit the 70 column limit pretty quick.
Devin M.
·
·
Think about all the opps for custom messaging just from running a domain waterfall, email waterfall, then the linkedin waterfall. Then enrich from profile. You could have a ton of columns with useful enriched data right there to customize messaging with.
Devin M.
·
·
My workaround so far has been to have a working table, and then write to another table for the major outputs of the enrichment…it could be solved with just more columns in one table.
Arturo O.
·
·
Awesome, really appreciate the breakdown, it will help our team make more informed decisions about this. Hopefully soon enough!
Channeled
APP
·
·
Hi Devin M.! This thread was recently closed by our Support team. If you have a moment, please share your feedback: