I have a need to limit users to what they can see in built-in dropdown lists on a form UI (for example, customer or transaction, etc). We can do this of course with custom list/record fields by setting filtering, but we do not have access to this filtering mechanism for built-in lists (such as the customer list/record field on a transaction).
Here is the scenario:
I want to limit the user/employee to seeing only customers and transactions of certain partners they are assigned to. We make this assignment in their employee record via a multi-select partner list/record.
We force a partner to always be set (beforeLoad) for various forms such as customer, transaction, case, etc using either the available built-in partner list/record field if available, or a custom partner list/record field when not available on the specific record/form.
I have set up saved searches that include the employee filtering criteria for all the records we care about (customer, transaction, case, etc) and force it to the user role (works like a charm).
However, if a user/employee creates a transaction for example, when they click on the built-in customer list/record field on the form (little 'List' icon to the right of the field), they get the entire list of customers in the system. There is no saved search view that I know of that I can set for this or anyway to tell this field to filter against the partner field setting, so this defeats what we are trying to do. The only workaround at the moment is to add our own custom customer list/record and hide the built-in customer field and set the hidden one via script when the user selects something in our custom field. This is a complete hack.
Ideally I am looking for a way to do one of the following:
1. some way to set filtering on built-in list/record fields (e.g. like a nlobjField.setFiltering() API that can be set during load or client-side init).
2. some way to force this pop-up list to use a specific saved search that I can set filters to.
Is there a way to do this now? If not, is this something that can be added relatively easy (e.g. 2010.1)? It is the one security flaw I see. Filtering using the role restrictions is too restrictive (at least from everything I have tried) and does not allow for a configurable option (they way we are doing it through the employee record for example).
Any one have a better approach than what I describe above or know of a reasonable solution to the problem?
Thanks.
-Steve