Hello,
I have two custom tables in a custom screen (Preferred Technician) that I will use for recording clients' technician preferences.
Custom Table A – Parent
Custom Table B – Child
A custom global code table – Technician Ranking (1-5)
Scenario:
In the custom screen (Preferred Technician), In the header (Table A will be used here), I have, for example, the "Set#", "Product Family", and "Client ID" fields. I can select the product family and client ID, then click SAVE, and a Preferred Technician Set will be created.
I will then go to the Preferred TECH to add the preferred Technician for this Set#. All the preferred Tech lines will be saved in Table B. Each Set# can have max five preferred technicians, and these technicians should be ranked.
The same technician cannot be reused within the same Set#, nor can the ranking number be reused. Therefore, I cannot set the Ranking field to "is unique" in Table B, as it would prevent reuse of the same ranking number in other sets. I have tried the "is key" checkbox, but it did not help.
I know I can use a BR or client script to check these ranking but still I would like to know if there are any other options, aside from using BR or client scripts, that can solve this issue? Is it possible to solve this with metadata config?
Thanks in advance😊
