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]

yes column!  (sorry about that)

does that make sense?