Based on your form, I'm not sure why you require a list field as it looks like you are trying to accomplish the same thing with the related list on the same form as the list field. There aren't really that many advantages to using a GlideList field over a related list (there are actually several factors in favor of the related list). In that case, option #1 of created a Meeting Organization Information reference field on the AIR Issues table would be a simple way to relate multiple air issues to a meeting. This option is the closest to actually having a foreign key into another table.
But if for historical reasons you need to, you can create the relationships on both sides. Navigate to System Definition->Relationships and click new. We are going to create 2 new relationships
Name the first Air Issues (or whatever), with the applies to table of Meeting Organization Information and a queries from table of Air Issues.
In the query with script field add the following:
(function refineQuery(current, parent) {
// Add your code here, such as current.addQuery(field, value);
current.addQuery('sys_id', 'IN', parent.u_air_issues_list_field_name)
})(current, parent);
Navigate to the Meeting Organization Information table, Configure->Related lists and you will see a new option available named 'Air Issues' (or whatever we named it). It will not have the '->' as it is not a natural relationship from a reference(foreign key) field. The result is a related list that matches what is in the list field. But you can't edit this list directly as it is just reflecting what is in the field. To add or remove items, you would need to edit the field.
On the other side, create another new relationship named 'Meeting Organization Informations' (or whatever) with the applies to table of Air Issues and a queries from table of Meeting Organization Information.
In the query with script field add the following:
(function refineQuery(current, parent) {
// Add your code here, such as current.addQuery(field, value);
current.addQuery('u_air_issues_list_field_name', 'CONTAINS', parent.sys_id);
})(current, parent);
Navigate to the Air Issues table, Configure->Related lists and you will see a new option available named 'Meeting Organization Informations' (or whatever we named it). The result here will be a related list with all the meeting informations that reference this Air Issue. Again, modifying this list requires modifying the underlying field that it uses in the query.
Hopefully, this helps.
