Premium

Salesforce Developer Certifications Questions and Answers (Dumps and Practice Questions)



Question : Roll up summary field and Cross object formula field can be created only for master detail relationship.
  : Roll up summary field and Cross object formula field can be created only for master detail relationship.
1. True
2. False

Correct Answer : 2

Explanation: Roll-up summary fields are used to aggregate child information on the master object.
The roll-up summary uses special functions such as SUM, MIN, MAX, and COUNT.

In the roll-up summary field, unlike the formula field, the field is placed on the
master object. The values are aggregated in the object. The values are stored in the
field and calculated periodically.

You can convert a master-detail relationship to a lookup relationship as long as no roll-up summary fields exist on the master object.
You can convert a lookup relationship to a master-detail relationship, but only if the lookup field in all records contains a value.
Roll-up summary fields work as in two-object master-detail relationships. A master can roll up fields on detail records; however, it can't directly roll up fields on subdetail records. To achieve this, the detail record must have a roll-up summary field for the field on the subdetail record, allowing the master to roll up from the detail's roll-up summary field.

In a many-to-many relationship, a user can't delete a parent record if there are more than 200 junction object records associated with it and if the junction object has a roll-up summary field that rolls up to the other parent. To delete this object, manually delete junction object records until the count is fewer than 200.

Cross-object formulas are formulas that span two related objects and reference merge fields on those objects. Cross-object formulas can reference merge fields from a master ("parent") object if an object is on the detail side of a master-detail relationship. You can reference fields from objects that are up to 10 relationships away. Cross-object formulas are available anywhere formulas are used except when creating default values.
Note
If you create a formula that references a field on another object and display that formula in your page layout, users can see the field on the object even if they don't have access to that object record. For example, if you create a formula field on the Case object that references an account field, and display that formula field in the case page layout, users can see this field even if they don't have access to the account record.








Question : Select the correct statement which is true for cross object formula field?


 :  Select the correct statement which is true for cross object formula field?
1. Cross object formula field helps to access field of parent from child
2. Cross object formula field helps to access field of parent from child in both master detail relationship and lookup relationship
3. It can be used in a formula field on child Like CustomObject1__r.Details__c where Details__c is a text field on the parent object CustomObject1
4. 1 and 2
5. 2 and 3


Correct Answer : 5

Explanation: Cross object formula field helps to access field of parent from child in both master detail relationship and lookup relationship. It can be used in a formula field on child
Like CustomObject1__r.Details__c where Details__c is a text field on the parent object CustomObject1.

One of the most powerful features of the Force.com formula are the cross object
formula fields. In cross object formula fields we can navigate up to five levels of
child-parent-grandparent relationship. Formula fields are calculated on the run time
according to the formula stored in the fields.
Record owner and activity fields cannot be used in a cross object formula fields. Let
us create the cross object formula field for the customer object.






Question : Field level security and record types work at
  : Field level security and record types work at
1. profile level
2. record level
3. 1 and 2 both
4. None of above


Correct Answer : 2


Explanation: The fields that users see on detail and edit pages are a combination of page layouts and field-level security settings. The most restrictive field access settings of the two always apply. For example, if a field is required in the page layout and read-only in the field-level security settings, the field-level security overrides the page layout and the field will be read-only for the user.
Important
Field-level security doesn't prevent searching on the values in a field. When search terms match on field values protected by field-level security, the associated records are returned in the search results without the protected fields and their values.
You can define field-level security in any of the following ways:
" For multiple fields on a single permission set or profile
" For a single field on all profiles
After setting field-level security for users, you can:
" Create page layouts to organize the fields on detail and edit pages.
Tip
Use field-level security as the means to restrict users' access to fields; then use page layouts primarily to organize detail and edit pages within tabs. This reduces the number of page layouts for you to maintain.
" Verify users' access to fields by checking the field accessibility.
" Customize search layouts to set the fields that display in search results, in lookup dialog search results, and in the key lists on tab home pages.
Note
Roll-up summary and formula fields are always read-only on detail pages and not available on edit pages. They may also be visible to users even though they reference fields that your users cannot see. Universally required fields always display on edit pages regardless of field-level security.
The relationship group wizard allows you to create and edit relationship groups regardless of field-level security.






Related Questions


Question : Apex sharing reason can be used for
  : Apex sharing reason can be used for
1. Manual sharing of records or one-off sharing which is done on a record basis
2. General sharing rule
3. Both of above



Question : 'Status' is a picklist of the Account object having value 'Open' or 'Closed'.
It is possible to create a sharing rule to share only those Accounts whose 'Status' is 'Open'.
  : 'Status' is a picklist of the Account object having value 'Open' or 'Closed'.
1. True
2. False



Question : Organization wide default (OWD) and sharing rules are applied at the

  : Organization wide default (OWD) and sharing rules are applied at the
1. profile level
2. object level
3. record level
4. 1 and 2
5. 2 and 3




Question : Organization wide default (OWD) is the first check used for determining access to records a user does not own.
  : Organization wide default (OWD) is the first check used for determining access to records a user does not own.
1. True
2. False





Question : Automating business processes is possible using
  : Automating business processes is possible using
1. workflow
2. approval processes

3. both of above

4. None of above



Question : Which are the actions available with workflow rules

1. send email
2. send outbound message
3. field update
4. set task
5. use existing action

  : Which are the actions available with workflow rules
1. 1,2,3
2. 2,3,4,5
3. 1,3,4,5
4. 1,2,3,4,5