#Data Management110 personnes en discutent

The native and recommended way to do this would be to use Transaction Security Policies as they would allow you to create realtime policies that block users from for seeing data you define in list views and reports 

Note: This requires the org either having Event Monitoring or Salesforce Shield (which bundles in Event Monitoring), which is an add-on product 

https://help.salesforce.com/s/articleView?id=xcloud.enhanced_transaction_security_policy_types.htm&type=5

https://developer.salesforce.com/docs/platform/platform-events/guide/platform-events-objects-monitoring.html

https://trailhead.salesforce.com/content/learn/modules/enhanced_transaction_security/enhanced_transaction_security_basics

Hi Katie,

The duplicate value error you are encountering (csp__Unique_Key__c) happens because that custom field is marked as Unique (likely enforced case-insensitively or case-sensitively) in your schema settings, and both contact records currently hold conflicting or populated values that clash during the merge operation. When Salesforce attempts to merge the records into the winning record, it briefly retains or evaluates the unique keys of both records simultaneously, triggering the block.

Here is how you can resolve and complete the merge: 

1.Clear or Modify the Unique Key on the Losing Record:

Field Modification. 

Navigate to the losing contact record, edit the csp__Unique_Key__c field, and either clear out the value entirely or temporarily change it to a distinct placeholder string. You can verify success when saving the edited record without a duplicate value validation error. 

2.Perform the Contact Merge:

Execute Merge. 

Return to the contact merge tool and execute the merge while selecting the correct master record. You can verify success when the merge completes without throwing the ConMergeException block. 

3.Verify the Winning Record's Unique Key:

Post-Merge Cleanup. 

Check the winning contact record to ensure its csp__Unique_Key__c matches the correct integration ID needed by Classy. You can verify success when the integration key on the surviving record is accurate and uncorrupted.

Short answer: you generally cannot (and do not need to) write QuoteAccountId into the standard Quote.AccountId field. On the Quote object, AccountId is a system-derived, read-only reference that Salesforce fills from the related Opportunity's Account. It is not createable/updateable through the UI, Flow, Apex or the API, so an update like AccountId = QuoteAccountId will be rejected or ignored. For quotes created without an Opportunity, QuoteAccountId (label "Account for Quote") is the field Salesforce intends you to use as the account relationship. 

For your future Order process this is already covered: Salesforce's documentation for quotes without opportunities says associating the quote to an account is optional but recommended, because an account is required to convert the quote to an order. When you create an Order from such a quote, the account comes from the quote's account (QuoteAccountId), so you don't need Quote.AccountId populated. 

Practical recommendations: 

1. Make QuoteAccountId required (validation rule, e.g. ISBLANK(OpportunityId) && ISBLANK(QuoteAccountId)) so every quote can be turned into an Order. 

2. After enabling the feature, open Object Manager > Quote > Fields > Account for Quote and grant field-level security to your profiles/permission sets. It is hidden by default, which is why it often looks unavailable in Flow, reports and Apex. 

3. In reports, flows, sharing logic and Apex, use one source of truth, for example a formula field BLANKVALUE(QuoteAccountId, Opportunity.AccountId), so logic works for quotes with and without an Opportunity. 

4. If you create Orders yourself via Flow/Apex (rather than the standard Create Order action), set Order.AccountId = Quote.QuoteAccountId and Order.QuoteId = Quote.Id. 

References: 

Enable Quote Creation Without a Related Opportunity:

Release note, Create Quotes Without a Related Opportunity:

Quote object reference:

Assumption: the statement that Quote.AccountId is read-only is based on the Quote object reference field properties and commonly reported org behaviour; please confirm in a sandbox (e.g. attempt the update in a Flow or Developer Console) before designing around it.

To migrate from Rackspace to Gmail

, you can manually transfer emails using an IMAP-supported email client like Outlook or Thunderbird. However, moving large mailboxes folder by folder can be time-consuming. 

For bulk migration, use

. It lets you select specific folders, apply date filters, transfer multiple Rackspace accounts & preserve emails, attachments, formatting & folder hierarchy while moving data to Gmail. 

Steps: Add your Rackspace account → select folders → choose Gmail as the destination → sign in to Gmail → start the migration.