Restricting other app lookup fields
I'm not sure if I'm using the correct terms here but I'll give it my best shot: We have an app that tracks tickets. We have another app that tracks feature requests with two tables Modules and ...
Forum Discussion
Drew,
I strongly suggest removing the multi select fields from the application. Put in a new table and drive everything with a relationship.
The multi select is a bit faster to start the app building process. However you will run into issues later as your workflows get more sophisticated. It is also a huge deal in reports. If you change the spelling or correct a multi select in anyway all your reports are broken. If you use Related Parent is equal to the record id value then you can change the table continuously and everything will work.
I learned the hard way and had to remove many fields......
------------------------------
Don Larson
Paasporter
Westlake OH
------------------------------
I strongly suggest removing the multi select fields from the application. Put in a new table and drive everything with a relationship.
The multi select is a bit faster to start the app building process. However you will run into issues later as your workflows get more sophisticated. It is also a huge deal in reports. If you change the spelling or correct a multi select in anyway all your reports are broken. If you use Related Parent is equal to the record id value then you can change the table continuously and everything will work.
I learned the hard way and had to remove many fields......
------------------------------
Don Larson
Paasporter
Westlake OH
------------------------------
We kind of need the multi selects.
Sometimes a ticket isn't JUST about one module. Sometimes it can affect multiple and we need to be able to select which ones?
Does anyone have any other work around for this?
Ticket type Dropdown
Dependent Module Dropdown (only displays when a certain ticket type selected)
Dependent Tag Dropdown (Only displays tags based on the previous Module selection)
This is how we are categorizing our records.
------------------------------
Drew Woods
------------------------------
- Drew,
How many multiselect fields do you have in a single table? That will limit how many you can associate with the record. Another way to do this and have unlimited amounts of associated items is to make a many to many between the Ticket and the Types. Here is a picture:
When your users add a record to Ticket Modules the CDD that @Mark Shnier (YQC) described will limit them to Modules that have the same Ticket Type as the Ticket.
You can have as many Ticket Module records as they want to add.
This describes having many Modules but would not address the Tags that belong to Modules. Do I have the first business case correct or will you have one Ticket Type, then only one Module followed by many Tags?
------------------------------
Don Larson
Paasporter
Westlake OH
------------------------------
