You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have 1 use case for sure. and an idea for the second.
The one i have is we have a related table, with the field sets. Would be cool to be able to add a lookup field to the field set, and or the table. Where the user is created a list of services, and there's a lookup to service providers, which is just a lookup to account with a filter on record type "service provider", and they could search this and select an existing record. I would not want them to create new though, but could do this through the permissions
The other use case would be an input type that would be a lookup field. Let's say for an address, and they need to put in county, and we have a related object called county, so they could pick from the county records.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I have 1 use case for sure. and an idea for the second.
The one i have is we have a related table, with the field sets. Would be cool to be able to add a lookup field to the field set, and or the table. Where the user is created a list of services, and there's a lookup to service providers, which is just a lookup to account with a filter on record type "service provider", and they could search this and select an existing record. I would not want them to create new though, but could do this through the permissions
The other use case would be an input type that would be a lookup field. Let's say for an address, and they need to put in county, and we have a related object called county, so they could pick from the county records.
Beta Was this translation helpful? Give feedback.
All reactions