Universal Containers has a Lightning record page that supports both the mobile app and desktop. An app builder has downloaded a custom Lightning component from AppExchange, but users are unable to view the component on mobile devices.
What can be the issue?
The most likely reason why users are unable to view the custom Lightning component on mobile devices is that the component has been developed for Desktop Pages only. Some components are not supported on mobile devices or have different behavior on mobile devices. An app builder should check the component documentation or metadata to see if it is compatible with mobile devices.
Ursa Major Solar (UMS) has a custom object where they track Galactic Vendors. The object has four custom fields for the Galactic Vendors's location:
The UMS's leadership wants these fields to be concatenated into a single formula field on two lines.
Which formula fulfills this requirement?
A)
B)
C)
D)
This formula concatenates the four custom fields for the Galactic Vendor's location into a single text value, separated by commas and spaces. The formula also uses the BR function to insert a line break after the second field, creating two lines of text. Option A, B, and D are not formulas that fulfill the requirement.
An app builder has a custom component they want to make available on the utility bar, but the component is unavailable.
How should the component be tagged?
To make a custom component available for the utility bar in Salesforce, the component needs to be explicitly tagged for use in the utility bar. Salesforce components require specific configurations to be available in different parts of the application, such as the utility bar, record pages, or app pages.
Option C: For use on the utility bar: When a custom Lightning component is developed, it must include a specific target tag in its .js-meta.xml configuration file that marks it as usable in the utility bar. This is done by setting the target to 'lightning__UtilityBar'. Without this tag, the component will not appear as an option to add to the utility bar in the App Manager.
Example of how the component is tagged in the meta.xml file:
xml
Copy code
<targets>
<target>lightning__UtilityBar</target>
</targets>
Option A: For use on record pages: This tag makes the component available only on record pages, but not the utility bar. The component would have a target for lightning__RecordPage in this case.
Option B: For use in Lightning App Builder: This option would allow the component to be used in the Lightning App Builder, but it wouldn't make the component available for the utility bar. App Builder placement is typically for page layouts.
Option D: For use in App Manager: This is incorrect, as App Manager is used for managing apps and not for tagging components for availability.
In summary, to make the component available for the utility bar, it needs to be specifically tagged for that purpose using the lightning__UtilityBar target in the component's metadata file.
Cloud Kicks wants to display 10 key fields at once in a separate section at the top of opportunity records on the desktop.
Which component should an app builder add to the record page to enable this functionality?
Highlights Panel. This is correct because the highlights panel component displays key fields from a record at the top of the page, and it can be configured to show up to 10 fields.
The CRM Manager at Universal Containers has requested that a custom text field be converted to a picklist in order to promote better data hygiene. What needs to be considered before changing the field type? Choose 2 answers
