Forum Discussion
I think I would keep this out of the Join table and instead have a Multi select field on the Physician table where you can select their Advanced Privileges. Of course you can position that multi-select field near the embedded table of Physician Credentials.
But to keep nth form tidy and not clutter up the Phsician form, I would go to the relationship between Physicians and Physician Credentials and make a summary checkbox field for if any of the Physician Credentials is the type that gets these Advanced Privileges.
Then have a form rule to show that multi-select field if the Physician has that specific Credential.
The challenge with adding Advanced Privileges to the Physician Info table is that it primarily contains biographical information, making it an unsuitable place for them. Advanced Privileges are more closely aligned with credentialing but are unique to the individual and the credentialing program, which is why I’m feeling a bit stuck.
- MarkShnier__You5 days agoQrew Legend
You said that these Advanced Privilege "Differ from person to person." I interpreted that to mean that the actual possible values vary from person to person so having say 10 checkboxes on a Join table record would not make sense. How about if you put that same suggested multi-select field on the join table record and show it for only the relevant Credential.
If you go that route, I find that he appearance of a multi select field is pretty horrible in View mode or on a report., so I make a formula text field with the formula below to show the selections as a vertical list.
SearchAndReplace(ToText([my multi select field]), " ; ", "\n")
So you would add this field as a column on the embedded report.
- DonLarson4 days agoQrew Elite
Can you give a few examples of an Advanced Privilege. The context can help with a solution.