Hi @jason_metzler
Thanks for sharing your feedback on the feature .
We did discuss the look up field scenario while we were building this feature and decided to not keep it as part of first scope.
Let us consider the below scenario where we have look up from a low volume object to Company object that has look up to User object
Record CSM Company CSM City
1 Prateek Gainsight Bangalore
2 Rakesh Meesho Hyderabad
If an user wants to edit Prateek to Rakesh for record 1 , should we go and just update ‘Prateek’ to ‘Rakesh’ or should system go and change the city name too.
In short which object data system should edit - low volume object or both low volume object and look up objects
(We don’t know what the user intention is when they are updating the CSM value “ Prateek”. It would have needed a complex UI solution for system to understand what the actual ask here is, hence it was not included in the initial scope )
Happy to discuss further on this through any means to arrive at a solution that solves your use case.
I would expect that the field brought into the report is the one that is updated. In my example I have a LVO with a lookup (user) field and I would want that field to be updated. In your example if we have the CSM City on our report, then if we make that editable, it would lookup through the CSM (user) and update their CIty.
I do feel like that Object / Lookup / Field wouldn’t be used very much, and if only the 1 layer deep editing was available it would be great.
@Prateek Parashar @jason_metzler I think I may have a different use case.
I have a lookup field on the Company object that looks up to a Low Volume custom object. I want users to be able to inline edit that field on a report on the Company object to associate the proper Low Volume object record to the Company record. I do not have the desire for users to be able to edit/update fields on records within the Low Volume custom object itself.
I can halfway do this, but only if it is a GSID mapped lookup. And even then - if the user wants to edit the lookup field on the Company record, they must type in or know the GSID and can’t search or type in any other string attributes within that Low Volume custom object.
My request is more functionality that is parity to what User or Company lookups can behave like in inline editing where I can search for the Name. OR parity to how lookups behave in CTA Layouts where an admin can choose which field/attribute on the LVO they want users to search.
@Prateek Parashar would this necessitate a separate Community Idea?
My request is more functionality that is parity to what User or Company lookups can behave like in inline editing where I can search for the Name. OR parity to how lookups behave in CTA Layouts where an admin can choose which field/attribute on the LVO they want users to search.
#productparity
Searching needs to be WAY more user-friendly across the platform.