I have a table ("Resources" (e.g., employees)) in a table ("Staff Resources"). I would like to have our staff relate the "Resources" to a table ("Properties") in another application ("RMIS"). However, I do not want our staffer to have access to confidential information in RMIS. Is it possible to relate a Parent ("Resources") to a Child ("Properties") across applications without sharing any further rights? See diagram for clarity.
The ultimate goals:
1. Relate Resources (Parent) to Properties (Child)
2. Enable staff to edit Resources-Properties relationship from existing Properties records. (New Properties records can be setup by a different staffer in RMIS)
3. Enable reporting of Incidents as grandchild to Resources
So... this issue has confused me after some serious blueprinting of options and limitations in Quickbase. I had setup another conversation and just posted much more detail on the issue:https://community.quickbase.com/quickbase/topics/using-formulas-actions-or-other-means-to-auto-relat...
I created diagrams (see comments in the other conversation) of each scenario I could think of which might get me closer to the goal but without adding significant workload/data/relationship management.