Make XRef Link Non-Navigatable?
I'm wondering if anyone has removed (or has ideas on how to) the ability to navigate into a cross reference field? I have a cross reference field that displays another cross reference in it (call it field 2), and I'm wanting to remove the ability to actually navigate into the record that is linked in Field 2.
Picture a user on a Risk record that has an xref to Controls. In that Controls xref there is another field called Control Category. I want the user to be able to select a Control Category via inline edit, but then not be able to go to the category record.
The sledgehammer approach would be a customer object that strips that field of it's hyperlink properties. Trying to think of a more graceful way to accomplish, I don't immediately come up with anything...
Not sure, but what if you put non key field in the Control CR.
Otherwise, over custom object, but if you want fully limit access to the record, it would not be possible as they could navigate over Global Search or Report.
I don't think a non-key field will work, as they need to lookup a record via grid inline edit. I'm not worried about them getting to the records via searching/reporting. I just want to force them to stay on the record when editing it.
To comment on what Ilya stated, you can hide data from within a record, but that doesn't remove a user's access to pull the "hidden" data another way. Your request is to allow a user to be able to select a Control Category, which requires them to have at least Read Access to the Control Category application. Since they have Read Access, they will see the record data. Access is Boolean, either yes or no, with additional layers of access on top to filter what type of access.
I've had similar requests come in from clients before. The only option I ever came up with was to set all of the fields that were not be accessible to that user/group to private fields. Anything else will still allow them to pull the data via search/report. Most clients go with the obfuscation option and just hide the data via DDE since the data was not ‘eyes only' or something confidential.
You could always have this group pick from a Values List and have someone else (or a data feed) actually populate the cross-reference later, but that is not a very practical approach.
If someone comes up with a resolution, simple or not, I'd love to look into it
Rather than a data feed to populate the values, maybe a calculated cross reference would work here? You could put the same global values list on both applications and then calculate with the field value match option.