Examkin

Soru

Zorluk: OrtaStandard and Custom Object Management

An administrator at an IT consulting firm is managing a custom object named Client_Project__c, which is currently connected to the standard Account object through a Lookup relationship. The executive team requests two functional changes: first, if an Account record is deleted, all associated Client_Project__c records must be automatically removed; second, account managers must be able to view a calculated total of all related project budgets directly on the Account record. Which action should the administrator take to accomplish both requirements?

  1. Convert the Lookup relationship on Client_Project__c to a Master-Detail relationship after ensuring all Client_Project__c records have an assigned Account, then create a Roll-Up Summary field on Account.Cevap
  2. B
    Create a Roll-Up Summary field directly on the Account object using the existing Lookup relationship to aggregate the budget totals.
  3. C
    Enable the standard Cascade Delete option in Account object settings while maintaining the Lookup relationship.
  4. D
    Assign a custom Record Type to Client_Project__c and configure picklist values to handle automatic deletion and budget aggregation.

Cevap

Convert the Lookup relationship on Client_Project__c to a Master-Detail relationship after ensuring all Client_Project__c records have an assigned Account, then create a Roll-Up Summary field on Account.
Converting the relationship from Lookup to Master-Detail satisfies both requirements: detail records are automatically deleted when the master Account is deleted, and Master-Detail relationships permit the creation of standard Roll-Up Summary fields on the parent object. To successfully perform the conversion, every existing child record must have a populated parent lookup field.

Adım Adım Çözüm

1
Analyze relationship capabilities for data retention and rollups
Identify that automatic cascading deletion and native Roll-Up Summary fields both require a Master-Detail relationship.
Lookup relationships do not support native Roll-Up Summary fields and by default clear the lookup field rather than deleting child records upon parent deletion.
2
Prepare data for relationship conversion
Ensure every existing Client_Project__c record contains a valid populated Account lookup value.
A Lookup relationship can only be converted to a Master-Detail relationship if all existing child records have a value in the lookup field.
3
Change relationship type and create summary field
Convert the field to Master-Detail and build the Roll-Up Summary field on Account to sum the project budgets.
Master-Detail relationships enforce cascade delete automatically and enable Roll-Up Summary fields on the master object.

Anahtar Kavram

Master-Detail vs Lookup Relationship Capabilities and Conversion Requirements
Bu soruyu puanla

Konular

Standard and Custom Object Management

Bu konudan daha fazla soru