Non-Agent API - Some custom fields not inserting

[rhonautics]

I've been using non-agent api for some time now, and it works fine with the default fields. However, when I tried to use custom fields, some of the fields are not inserted into the custom_<list_id> table.

http://www.vicidial.org/docs/NON-AGENT_API.txt

My query string are as shown below:

Code: Select all

custom_fields=Y&ip_address=www.xxx.yyy.zzz&subid=qwerty&subsubid=zxcvb&insertdate=2021-01-08&inserttime=1000H&pain_location=joint


Only ip_address, subid, subsubid & insertdate are stored. inserttime & pain_location is not inserted into the custom_<list_id> table. I've checked the column name on the custom fields table, it matches the query string parameters.

Is there something that I've missed out, or limitations of non-agent api that I'm not aware of perhaps?

[carpenox]

which function are you trying to use?

[rhonautics]

I'm trying to add lead using add_lead function. Default fields works but custom fields are picky.

[carpenox]

does the api user have this enabled? Custom Fields Modify = 1

[rhonautics]

Yes, also these options.

Modify Leads - 1
Custom Fields Modify - 1
Agent API Access -1
API Allowed Functions - All Functions

Still the same.

[carpenox]

msg me on skype ill try to help you troubleshoot it and we can report back the fix afterwards

[rhonautics]

sounds good. I just sent you a message on skype

[carpenox]

wait i just realized that some fields were working and some were not, i didnt pay attention to that at first, im sorry. It has to perhaps be a limitation on the adds lead function

[rhonautics]

I had to dig into the code of non-agent api. It is checking vicidial_lists_fields first before inserting custom fields to custom_<list_id> table.

This is not a limitation of add_lead function.

In my case, I was creating custom_<list_id> manually with a script that I created to make lead lists on a daily basis but unknowingly bypassed the vicidial_lists_fields.

[carpenox]

i messaged you back on skype