Forum Discussion

Qrew Member

3 years ago

Too many entries in multi-select text field. Need solutions, please?

I have an app for project managers. When they create an activity, they can assign that activity to a project team member or other resource. The Assigned To field in the Activities table is a multi-sel...

Relationships

Tables and fields

MarkShnier__You

Qrew Legend

In the long run, a better approach is to have a many to many relationship. One Resource has many Resource Activity Assignments. And one Activity has many Resource Activity Assignments. There is a technique that I could help you implement which would allow you to quickly add resources to a particular activity.

------------------------------
Mark Shnier (YQC)
mark.shnier@gmail.com
------------------------------

PaulEaston

Qrew Assistant Captain

2 years ago

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
------------------------------