– save submissions to a comma delisted file
– save submissions to the database using custom table
– write to a log file
– save to a repeater custom field
Saving to the database would be most robust but it would be duplicating a lot of work. I really just need this information *in case* the connection get’s interrupted, which it does some times.
Thanks!
]]>I would think that the best solution would be only storing that information if required. Are you able to integrate with the CRM over an API? Ideally, you could fire off the required information to the CRM and get a success/failure response and then handle that accordingly. Temporarily storing the data if the call failed and create a cron job to try again at some set interval. Then if that fails notify an admin or whatever.
If this isn’t possible I’d go the database route and then write something to display this information somewhere in the admin so I could easily access the information required if a submission was to fail.
Hope that helps some..
Kind regards,
Joey
That helps quite a bit. Thanks for taking the time to write.
I will implement your suggestion of simply emailing myself the submission if there’s an issue!
Harv
]]>