List Collector Choices, when to use them?

[AngelP83]

Hello Everyone,

I am not sure which one to use about the following:

My team has a Record Producer for customers to submit tickets. I was tasked to add a Region in the form.

So, the other fields for example: Sports

The Table is INCIDENT, the Column is u_sport..

I am not sure why the previous developer did the following, but he did the following:

The Record Producer shows the field Sports, which points to the table Incident, and the u_sport column, but the reference is pointing to a List Collector Choices.

Now I wonder, why does it have to point to a List Collector Choices? why not straight to the column?

-------------------------------

Here is my problem. The table INCIDENT, contains a Column name REGION (u_region). (which contains 4 Choices).  I dont know if that column is being used by another team, also we do not like the names they were given, so I was thinking to create a new Column with the name of my team u_myteam_region and assign them 6 different region names.

• Should I use the existing u_region and from my Record Producer point/reference to a List Collector Choices? (with my 6 region names that i will have to create).

OR

• Should I create the new column "u_myteam_region", add the choices, and grab those choices from the Record Producer? (without using list collector)?

I guess I am having problems understanding why we use List Collector Choices (I thought it is for other people to make changes to the list (in this case regions), without touching the table > column itself.

[juan9]

Hi Miguel

Here are the answers to your questions ( I hope )

Now I wonder, why does it have to point to a List Collector Choices? why not straight to the column? :: every developer codes/configures different,

• Should I use the existing u_region and from my Record Producer point/reference to a List Collector Choices? (with my 6 region names that I will have to create). :: do not create a new column use what is in the system already

I guess I am having problems understanding why we use List Collector Choices :: we use list collectors to display/capture/include multiple values or records for a given record.

The list collector and be configured so that it aims at a table or contains localized choices.

The reason why I dont recommend creating a new field is that we dont know how many dependencies there are in the system.

Why pick a localized list vs a reference list? if the data is in the system already, try to use reference. if the choices are not in the system already, create local choices over consuming a table.

If my answer helped even a little, please mark it as helpful, and happy Sunday!

Here is a really good videos about list collectors :: https://www.youtube.com/watch?v=5rT8ZeKbYck

[AngelP83 · Accepted solution]

Thank you for the information!

so for what I am understanding... I should use the existing Table > Column (u_region) and create a New List Collector with the names I want.  

Ckeck "MAP IT FIELD" 

FIELD: u_region

Type Specifications: point to the new List Collector

Right?

[juan9]

use the same list collector unless you are 100% that no other script references that field. 

[AngelP83]

you meant Column? use the same Table > Column?