--- schema_version: "1" id: 477fecfc2c465f0f3d17c7556880456ec76f0e318724eabf33f373b3acacb190 title: Values in a Predicate Expression collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/analytics/264-0-0/bi_security_datasets_predicate_values.md canonical_url: https://help.salesforce.com/s/articleView?id=analytics.bi_security_datasets_predicate_values.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: 18a447976647594b11417726f3ef5df3b2cd374477a5e56e5c54a6bbca019172 description: The value in the predicate expression can be a string literal or number literal. It can also be a field value from the User object in Salesforce. products: - CRM Analytics - Cross Cloud release: "264" --- # Values in a Predicate Expression The value in the predicate expression can be a string literal or number literal. It can also be a field value from the User object in Salesforce. Consider the following requirements for each value type.

Value Type Requirements Predicate Expression Examples

string literal

Enclose in double quotes and escape the double quotes.

Value Type	Requirements	Predicate Expression Examples
string literal	Enclose in double quotes and escape the double quotes.	`'Owner' == "Amber"` `'Stage Name' == "Closed Won"`
number literal	Can be a float or long datatype. Do not enclose in quotes.	`'Expected_Revenue' >= 2000.00` `'NetLoss' < -10000`
field value	When referencing a field from the User object, use the $User.[field] syntax. Use the API name for the field. You can specify standard or custom fields of type string, number, or multivalue picklist. When you define a predicate for a dataset, you must have read access on all User object fields used to create the predicate expression. However, when a user queries a dataset that has a predicate based on the User object, CRM Analytics uses the access permissions of the Insights Security User to evaluate the predicate expression based on the User object. Note By default, the Security User does not have access permission on custom fields of the User object. To grant the Security User read access on a field, set field-level security on the field in the user profile of the Security User.	`'Owner.Role' == "$User.UserRoleId"` `'GroupID' == "$User.UserGroupId__c"` Note Supported User object field value types are string, number, and multivalue picklist. Other types (for example, boolean) are not supported.

'Owner' == "Amber"
'Stage Name' == "Closed Won"

number literal

Can be a float or long datatype. Do not enclose in quotes.

'Expected_Revenue' >= 2000.00
'NetLoss' < -10000

field value

When referencing a field from the User object, use the $User.[field] syntax. Use the API name for the field.

You can specify standard or custom fields of type string, number, or multivalue picklist.

When you define a predicate for a dataset, you must have read access on all User object fields used to create the predicate expression.

However, when a user queries a dataset that has a predicate based on the User object, CRM Analytics uses the access permissions of the Insights Security User to evaluate the predicate expression based on the User object.

Note

By default, the Security User does not have access permission on custom fields of the User object.

To grant the Security User read access on a field, set field-level security on the field in the user profile of the Security User.

'Owner.Role' == "$User.UserRoleId"
'GroupID' == "$User.UserGroupId__c"

Note Supported User object field value types are string, number, and multivalue picklist. Other types (for example, boolean) are not supported.