You are here:
User Locale and Visit Engagement Fields
Your users' locale settings affect which fields appear on the Visit Engagement page. This visibility is independent of page layouts, field-level security, and related-list configurations.
You are here:
Your users' locale settings affect which fields appear on the Visit Engagement page. This visibility is independent of page layouts, field-level security, and related-list configurations.
| Available in: Lightning Experience |
| Available in: Enterprise and Unlimited Editions with Life Sciences Cloud, Life Sciences Cloud for Customer Engagement Add-on license, and the Life Sciences Customer Engagement managed package. |
If fields such as Product ID, Production Batch ID, or Requested Quantity don't appear on the Visit Engagement page on the desktop site but appear correctly in the mobile app, check the user's locale setting. Verify this setting before investigating page layouts or permissions. Certain unsupported locale variants can cause fields to render incorrectly on the web interface.
Salesforce supports locales in Language (Region) format, such as English (United States) or English (India), but doesn't support Language (Region, Currency) variants—for example, Spanish (Spain, Euro) or French (France, Euro)—which cause certain fields to appear incorrectly on the Visit Engagement page in the desktop site. The same fields appear correctly when the user accesses the page on the Life Sciences Cloud mobile app.
Assign Life Sciences Customer Engagement users a locale in Language (Region) format, such as English (United States) or English (India). Salesforce doesn't support locales in Language (Region, Currency) format, which cause field display issues on the Visit Engagement page.

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.