Re: Too many entries in multi-select text field. Need solutions, please?
Sorry for the thread necro, but I'm running into a similar issue. I have a Requests table and the end-users want to be able to associate a request with prior requests. So I created a multi-select text field that looks up from the Request ID# field.
I understand that the kludge recommended here is not considered best practice, but when I'm only dealing with one table, how would I set this up properly? Do I have to create Request Numbers table that uses pipelines to populate all existing Request ID#s? Then another table to allow for many-to-many? It feels more complicated and result in duplicate data that is only created to create a lookup field?
------------------------------
Paul Easton
------------------------------
I understand that the kludge recommended here is not considered best practice, but when I'm only dealing with one table, how would I set this up properly? Do I have to create Request Numbers table that uses pipelines to populate all existing Request ID#s? Then another table to allow for many-to-many? It feels more complicated and result in duplicate data that is only created to create a lookup field?
------------------------------
Paul Easton
------------------------------