A discusses that their understanding is that option B is incorrect. They provide a link for more details on app design. Another response discusses that option E is not correct because data import does not consider field dependencies, and any value can be imported regardless of controlling field values. Option B and D are suggested for creating a sharing rule to share with a public group. Option C is also discussed.
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0 ratings0% found this document useful (0 votes)
355 views66 pages
App Builder SP21 - 2
A discusses that their understanding is that option B is incorrect. They provide a link for more details on app design. Another response discusses that option E is not correct because data import does not consider field dependencies, and any value can be imported regardless of controlling field values. Option B and D are suggested for creating a sharing rule to share with a public group. Option C is also discussed.
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 66
A D E
A--As per my understanding. B is incorrect
Also please refer the link for more details
https://help.salesforce.com/articleView? id=sf.design_your_app.htm&type=5 Correct Answer: A B C---E is not correct because The Data Import Wizard doesn’t consider field dependencies. You can import any value into a dependent picklist regardless of the value imported for a controlling field. BD A ,B
https://help.salesforce.com/articleView? id=fields_about_roll_up_summary_fields.htm&t ype=5 D C A B, D-----create a sharing rule and then share with a public group B B D D B C B