10,729
edits
(Data visibility - new section) |
|||
Line 87: | Line 87: | ||
; User role (profile) | ; User role (profile) | ||
: Your user role does not have | : Your user role does not have permission to view the record. | ||
Tip: It is not possible to use Parent > Child relationships in Sync Filter (Contact.Account is possible, Account.Contacts is not). The same limitation applies to view filters used in online mode. | Tip: It is not possible to use Parent > Child relationships in Sync Filter (Contact.Account is possible, Account.Contacts is not). The same limitation applies to view filters used in online mode. | ||
== Using search strings in filters == | |||
When app users use the filter function in a view, they can use only the fields of the viewed entity as filter criteria. For example, on the Opportunity view, you can filter records by Customer or Estimated Revenue, because both are fields of the Opportunity entity. However, you cannot filter for opportunities whose customer comes from a particular city, because City is a field of a different entity, Customer. | |||
Fortunately, there's a way. Using the '''Edit Filter''', you can define a set of conditions that allow full-text search in related fields. In the following example, while on the Opportunity view, app users can use the Search function: the string is then compared with the topic of the opportunity, the name of the account or the full name of the owner (with account and owner being related entities). The filter uses the search condition; when at least one field matches the searched string, the opportunity is displayed. This is ensured by the string <code>@@filter@@</code> that corresponds to the searched string. | |||
[[File:Filter related entity field.png|600px]] | |||
This special behavior is only possible when using the Search function in the app; it does not work for the filter function. | |||
[[File:Search vs filter.png|300px]] | |||
[[Category:Woodford]] | [[Category:Woodford]] |