Allow edit to an S3 Dataset Task in Bionic Rules

  • 1
  • Idea
  • Updated 2 weeks ago
Apparently once you create an S3 Dataset task, load the column details, and save it - you cannot edit it.

So if you realize you failed to include a column in the file you are attempting to import, you have to delete the dataset task and create a new one - unless I'm missing something key?

Sure would be easier if I could edit the existing one, re-load the column details and re-save.


Photo of Jeff Kirkpatrick

Jeff Kirkpatrick, Champion

  • 21,314 Points 20k badge 2x thumb

Posted 3 weeks ago

  • 1
Photo of Jitin Mehndiratta

Jitin Mehndiratta, Product Manager

  • 2,328 Points 2k badge 2x thumb
Hi Jeff,

The rationale behind not allowing the user to edit the S3 file configuration once configured, is to freeze the S3 file format details as the edit might lead to rule failures if the format doesn't match. We have plans to update the S3 dataset task feature to allow the user to be able to add a new column (if that was missed in the first go) or to delete an existing column. Let me know if that will be helpful. Would love to hear more thoughts on that.

Regards,
Jitin
Photo of Jeff Kirkpatrick

Jeff Kirkpatrick, Champion

  • 21,314 Points 20k badge 2x thumb
Thanks for the explanation Jitin. I appreciate you wanting to prevent admins from shooting themselves in the foot, but I think it’s more important to leave it to the admin’s judgment and allow the flexibility to adjust criteria as needed. A good admin will do the due diligence to ensure everything syncs up. Very similar with being unable to edit Query Builder in advanced outreach.