vicidial.org

Hi

We use most of our standard agent interface fields in our custom fields. However, we have to insert the information in the custom fields when taking a client's details. If we do it like that it updates the standard fields but if we do it the other way around the information does not save in any of the fields.

Within the campaigns without custom fields the information saves in the standard fields without a problem.

I really cannot follow what you are saying. Please explain step by step in greater detail what exactly your problem is.

I have created some campaigns with custom fields. Almost all of the standard fields I also use within my custom fields. For example "comments", "title", "middle_initial" are all duplicated in my custom fields as well.

In a campaign with custom fields I HAVE TO capture the data in the custom fields for it to save. If I capture it in the standard agent fields the data does not save at all. For example, if I capture "comments" in the standard interface it saves in neither the standard interface nor the same field in the custom interface. When I do it the other way around it works though - when I capture in the "comments" field in the custom interface it does save and also updates the standard "comments" field.

In the campaigns without custom fields all data captured in the standard agent fields saves correctly.

i'm not using custom fields right now (no time), but i'm thinking you probably shouldn't have custom fields with the same names as the standard fields. i'd just avoid that possible conflict entirely.

If you are using custom list fields with the same field labels as the standard fields(which is allowed) then you will loose anything entered into those fields on the standard main screen. You should only have your agents use the standard fields as you have defined them in the FORM tab, not the main tab.

It would help if you have the FORM auto-launch at the call arriving at the agent.

Thanks Matt, that answers my question.

I know this is an old thread, but I am having a similar issue. An in-group that uses custom fields are not saving the first and last name. It does save the comments. I do not really use the other fields for this campaign. None of my custom fields are used for first or last name (or any other standard field) and there is no naming conflict. The only place I reference the standard fields is in a mailto link in the agent script. The agent clicks 'Refresh' on the script then clicks the mailto link to generate an email with the information collected on the call. This email generates properly with all the standard and custom fields.
If I go to the lead through the Admin and enter the first and last name, the information is then saved.
The problem seems to occur when there is no caller ID so the lead phone_number is blank.

ClearCall wrote:I know this is an old thread, but I am having a similar issue. An in-group that uses custom fields are not saving the first and last name. It does save the comments. I do not really use the other fields for this campaign. None of my custom fields are used for first or last name (or any other standard field) and there is no naming conflict. The only place I reference the standard fields is in a mailto link in the agent script. The agent clicks 'Refresh' on the script then clicks the mailto link to generate an email with the information collected on the call. This email generates properly with all the standard and custom fields.
If I go to the lead through the Admin and enter the first and last name, the information is then saved.
The problem seems to occur when there is no caller ID so the lead phone_number is blank.

"seems to occur" needs to go away. Test the theory. If the problem can be reproduced by having no caller ID on an inbound call, that's useful troubleshooting information.

Perhaps it would be good to upgrade to the latest SVN before you decide there's a bug, though.