Hello again drrobotnik,
Good point – we’ll have to look into the best way to present the submission data in the CSV file. Do you have a specific preference in mind?
Separating out the name fields into a meta element on each contact is something we are working on in a coming version as well. It seems trivial on the surface but actually takes a bit of engineering to setup correctly because LeadIn hooks into most forms without requiring configuration for specific ones.
Thanks for all your feedback so far and please do keep it coming. I’ll leave this ticket marked unresolved and circle back with you after we look into the exporting feature in the coming week.
– Andy
Hi Andy,
Thanks for the insight. Yeah it does get a bit complex and I have a feeling different folks may want this different ways. This became apparent with mail service integrations.
In our case we want to parse out the information similarly to how it’s displayed on the dashboard. The only change I’d prefer is for checkgroup field types, instead of parsing these into their own fields with the values checked/unchecked, merge these into one comma separated key/value.
For example: ( checkgroup )
Alcohol Preference
[x] Rum
[x] Bourbon
[ ] Rye Whiskey
[ ] Single Malt
Could merge to Alcohol Preference: Rum, Bourbon
Interesting suggestion and something we will consider. I’m going to add it to our idea list and will circle back with you on what we decide to do.
Also, thanks for the feedback and feature ideas so far 🙂
Do you mind sending me an email directly with a little more background on how you’re using LeadIn? Hearing how you’re using the plugin will help us come up with better designs as we build more – andy@leadin.com
Cheers and thanks again!
I’m going to close out this support ticket because I added the feature to our backlog of product ideas. If we add in the future, I’ll make sure to circle back here and let you know.
