Skip to main content

Currently, we are considering GSID of the logged in user (current user) and validating it against the user table to fetch the records in dashboard reports. If a customer would want to query for the records where the filter field is a string and uses the current user, we do not see any data, since a string field currently cannot be matched with the GSID of the current user. 

ASK: A product solution for CURRENT USER to work the same way OTHER USER

Use case:

LinkedIN has a string field ‘LDAP’ in a custom object which they are using in dashboard. Now, when they filter LDAP=‘Current User’ it appears we are considering the login user’s GSID and comparing it with the LDAP. Since LDAP is a string field, it is failing to fetch the records. However, when we use LDAP=‘other user’, we are treating this as a string and comparing it with the LDAP (which is a string field) and hence the data is populating.

For example: a CSM’s LDAP: is ‘sagarcia’ who logged in (current user) we need the ability to relate GSID with the LDAP (a string field). 

Be the first to reply!

Reply