In-Group Entry List ID versus In-Group List ID

[dspaan]

On the modify DID screen you have these two fields. I believe in older versions the In-Group Entry List ID did not exist.

In-Group List ID

If IN_GROUP is selected as the DID Route, then this is the List ID that leads may be searched through and that leads will be inserted into if necessary.

In-Group Entry List ID

If IN_GROUP is selected as the DID Route, then this is the Entry List ID that a new lead will be populated with if a new lead is added. Default is 0 for disabled.

Does the second field override the first one? I would suggest updating these help texts so it's clear how these fields work together.

In the manager manual it says additionally for the In-Group Entry List ID:
(This feature has to be enabled in Admin → System Settings).

And in System settings it says:
Enable DID Entry List ID

This setting if enabled will allow a manager to define an entry list id to use on the DID modify screen. Default is 0 for disabled.

My confusion is that the In-Group List ID field is also used for inserting new leads into a list.

[mflorell]

The "Entry List ID" is related only to the set of custom list fields that are used for a lead. It does not have to be the same as the List ID. We have many clients that use this to define only one set of custom fields for inbound leads while still having them spread out across dozens of lists.

[dspaan]

Oh that's a great feature actually. Does this also exist for outbound?

[mflorell]

In the Non-Agent API, yes, it does exist.

[dspaan]

Ok but no option i can configure that is used when manually loading leads through the web interface and setting one set of custom fields for all lists under a campaign or system wide? Because that would reduce maintenance and creation of new lists a lot.

[mflorell]

That's correct, there is currently no option to use a separate set of custom list fields in the Web Lead Loader like you can do in the Non-Agent API. Adding that for the web lead loader would probably be 4 hours of dev work.

As for setting one set of custom fields system-wide, that would require coding in dozens of scripts all over the place and could be dozens of hours to code and test.

[dspaan]

By system setting you mean that all campaigns in the system use the same set of fields?

When I would also want the custom fields to show up on exporting leads reports would that be part of the 4 hours project or dozens of hours?

[mflorell]

The 4-hours project I mentioned only touches the Web Lead Loader, and it's just for adding one new option to it.

As for one set of custom fields to be used by default system-wide, and the options/features that would entail, you would really need to define everything that you want involved in that and submit a comprehensive set of requirements, because that will be a large project and it sounds like it will take a while just to come up with the quote for it.