The ability for users to edit fields, especially en masse, has been expanding. Instead of just being limited to fields in areas like CTAs, Success Plan, etc., fields can also be edited on Mass Edit Scorecard reports, some 360 attribute areas, and more recently My Portfolio and even in-line editing.
While these can make both admin and user lives easier, they unfortunately lack some pretty standard capabilities across areas of the product to make using it viable. There are so many admin restrictions and caveats, and so little ability for us to put guardrails consistently these benefits are sometimes rendered completely unusable.
One main area is any kind of data validation when making lookup fields editable. There are a few places where this is possible, but even those are not done particularly well (see this post).
However, we should be able to put the same filter validations anywhere we make a lookup editable (there may be some exceptions for certain system things).
Example:
- If you add a lookup field to a CTA where you allow the user to edit it, you have the ability to set up filters to limit the results. This is super helpful if you want to make sure a user can only add a record related to that company:
If you have a lookup on the Company object, there does not appear to be any way to add this kind of filter either at the field level, or in the report setup when you want to allow in line editing to change what record the lookup is associated to.
What this means, is that if you have say, a look up to the CTA object and you want to associate a particular CTA via that lookup, you cannot restrict the search to CTAs just for that company or relationship. You get every CTA under the sun. You might even be limited in the search fields you can display, to even show what company the record is associated with in the first place.
This just makes an overall poor and inconsistent experience for both admins and users.
Please allow us to set up filter/validation restrictions on lookups throughout the platform, if we are asking for user input.
