speakincode6

Playing with that in Postman a bit now… Returns some info, but not too much. No big deal though, thanks for your help.

@doekenorg Thanks for looking into this! For the time being, I’ve decided to just manipulate the repeater data as an entry after it’s been submitted. I loop over the repeater fields, separate each repeater row into it’s own entry, putting each subfield in it’s own column. This solves the issue of dynamic repeater rows and static csv columns. I can always account for a set number of columns and just put each repeater entry as it’s own row.

May not work for every application, but it’s what was best for my particular project.

So thanks again for looking into this, but I’m good for now as far as this particular project.

@doekenorg Congrats!! Don’t worry about this issue.

I really appreciate you reaching out so quickly. Just enjoy your family. I’ll reach back out in the future if need be.

Take care!

@doekenorg Thanks for the reply.

I’m not using a plugin. I’m using the native Gravity Forms Repeater field, implemented programmatically, as found here:

https://docs.gravityforms.com/repeater-fields

I understand that an export file needs to have a set number of columns and a repeater is dynamic so matching the two up is problematic. My thought is, I can set a maximum limit to the Repeater to say 5 to help with that issue. So the export file can have as many static columns up to the limit of what the repeater will return.

@verhoevenwout Can you share how you accomplished this please? I need to do the same thing.

@danieltj Thank you for the response. For now what I’ve done, is created a JSON object that mirrors what the fields response is after it’s actually saved in the admin area, and I send that JSON to the “fields” key when creating the post, which essentially is populating and updating the ACF fields and it works now.

It’s just unfortunate to have to create my data models twice, once as ACF fields and once as a JSON object to post to them upon creation. I was really hoping there’d be a way to “mimic” clicking that “Update” button and thus saving all the data to the DB at that point.