Custom Form not saving data

All installation and configuration problems and questions

Moderators: gerski, enjay, williamconley, Op3r, Staydog, gardo, mflorell, MJCoate, mcargile, Kumba, Michael_N

Custom Form not saving data

Postby maddata » Wed Nov 20, 2013 5:12 pm

Goautodial ISO 3.0 CE - CentOS 5.9
Vici VERSION: 2.7-401a
BUILD: 130508-2256

Single server

HP Proliant Gen8 Quad Core w/ 16GB RAM

I think I covered most of whats asked about the install / hardware so please forgive me if I missed something.

I am using a custom form with several custom fields. I can see the tables in the DB, I get the form to populate from the standards fields, but while I have the agents able to modify fields in the user settings, as well as editable by campaign settings, any information typed into the custom form does not save when the call is transferred to the closer.

Any ideas?
maddata
 
Posts: 3
Joined: Wed Nov 20, 2013 5:04 pm

Re: Custom Form not saving data

Postby williamconley » Wed Nov 20, 2013 9:40 pm

are you using the vicidial agent web interface or the modified goautodial agent web interface? if you're using goauto ... try the stock vicidial one. it's amazing how many tiny little things will go wrong with an ajax-based web interface with tens of thousands of lines of code when it's customized. using the non-modified one can be quite helpful (certainly for testing ...).
Vicidial Installation and Repair, plus Hosting and Colocation
Newest Product: Vicidial Agent Only Beep - Beta
http://www.PoundTeam.com # 352-269-0000 # +44(203) 769-2294
williamconley
 
Posts: 20258
Joined: Wed Oct 31, 2007 4:17 pm
Location: Davenport, FL (By Disney!)

Re: Custom Form not saving data

Postby maddata » Thu Nov 21, 2013 12:49 pm

I have tested from the Vici agent screen and the Goautodial interface, same issue, yet I dont see an error. Its almost like there should be a "Submit" button somewhere I am missing
maddata
 
Posts: 3
Joined: Wed Nov 20, 2013 5:04 pm

Re: Custom Form not saving data

Postby maddata » Thu Nov 21, 2013 3:27 pm

Found the issue - it was between the keyboard and the chair. The "NULL" statement is required for any "select" field or it will not execute the SQL. Found the error finally on a non-production box.
maddata
 
Posts: 3
Joined: Wed Nov 20, 2013 5:04 pm


Return to Support

Who is online

Users browsing this forum: Bing [Bot] and 80 guests