#Salesforce Admin371 diskutieren mit

In our Salesforce org, we are seeing the following notification: 

We checked our Einstein Activity Capture (EAC) settings and noticed that Google G Suite

is currently connected. We do not have a Microsoft Outlook account connected to EAC. 

Based on this configuration, we have a couple of questions:

1. Since our EAC configuration is using Google G Suite, do we still need to upgrade the authentication method from Exchange Web Services (EWS) to Microsoft Graph API?
2. Since Outlook Integration & Sync is enabled, does this require us to migrate from EWS to Microsoft Graph API even though Google G Suite is the connected account in EAC?
3. If the Microsoft Graph API upgrade is still required, what is the recommended authentication level/permission level that should be configured for the Salesforce app in Azure?https://help.salesforce.com/s/articleView?id=sales.activity_capture_graph_api.htm&type=5#:~:text=App%20ID%20for%20Microsoft%20Graph%20Authentication 
4. Is there any impact on our current EAC functionality if we continue using Google G Suite and do not have Microsoft Outlook connected?

I have attached screenshots of our current configuration for reference. 

Any guidance from someone who has already handled this EWS retirement transition would be greatly appreciated.

#Einstein Activity #Einstein Activities Capture #EAC #Salesforce Admin #Salesforce Developer 

In our Salesforce org, we are seeing the following notification:

We checked our Einstein Activity Capture (EAC) settings and noticed that Google G Suite is currently connected. We do not have a Microsoft Outlook account connected to EAC.

Based on this configuration, we have a couple of questions:

1. Since our EAC configuration is using Google G Suite, do we still need to upgrade the authentication method from Exchange Web Services (EWS) to Microsoft Graph API?
2. Since Outlook Integration & Sync is enabled, does this require us to migrate from EWS to Microsoft Graph API even though Google G Suite is the connected account in EAC?
3. If the Microsoft Graph API upgrade is still required, what is the recommended authentication level/permission level that should be configured for the Salesforce app in Azure?
4. Is there any impact on our current EAC functionality if we continue using Google G Suite and do not have Microsoft Outlook connected?

I have attached screenshots of our current configuration for reference. 

Any guidance from someone who has already handled this EWS retirement transition would be greatly appreciated.

Hi everyone,

I'm working on a Revenue Cloud implementation with two sandboxes (both refreshed from the same production org, at different times). In Sandbox A, activating an Order correctly creates Asset records from the OrderItems. In Sandbox B, the exact same flow (Quote → Contract → Order → Activate) leaves the Order in Status = 'Activated' with zero errors, but no Asset is ever created — and querying Asset in that sandbox returns 0 records, period, in its entire history.

What I've already ruled out (identical between both sandboxes):

• RevenueManagementSettings, OrderSettings (all flags match, including enableEnhancedCommerceOrders=true, enableAutoAddDerivedAsset=true)
• PermissionSetLicense for Revenue Cloud User / Fulfillment User / Billing / Business Rules Engine — all Active
• Extended ContextDefinition mapping for Order/OrderItem vs Quote/QuoteLineItem — byte-for-byte identical counts
• No custom Apex triggers or Flows on Order in either org — it's the pure standard "Activate" action
• No AsyncApexJob/BackgroundOperation errors around the activation — nothing seems to even attempt the asset generation step
• TransactionProcessingType: the broken sandbox had zero records while the working one had one marked default (Business Rules Engine). I created a matching record via Tooling API, but the issue persists.

Has anyone run into a case where Asset-Based Order Management (or whatever gates Order→Asset generation) is silently disabled at the org level in a way that doesn't show up in any Settings metadata, Tooling API object, or PermissionSetLicense? Is there a one-time, irreversible enablement step (like "Enable Contract, Asset, and Subscription Management") that a sandbox refresh could leave off even when everything else looks provisioned?

Any pointers on where else to look (or whether this needs a Support case) would be hugely appreciated — this is blocking QA testing for a client go-live. 

Hi everyone,

I need an architectural sanity check on a security requirement. I want to avoid hitting platform limits down the road and would appreciate some feedback on whether this can be safely achieved using Schedule-Triggered Flows or whether Scheduled Batch Apex would be required.

Context

• We are changing the Organization-Wide Defaults (OWD) of the standard Quote object from Controlled by Parent to Private.
• We receive an integration feed from an external system that creates or updates up to approximately 80 Quotes per Account per day. Quotes can also be created manually in Salesforce.
• Quotes contain two custom Account lookups: Sold-To and Bill-To.
• We have both Quotes with and without Opportunities.

Requirement

• The Account Owner of the Sold-To Account and the Account Owner of the Bill-To Account must have Read-Only access to the related Quote.
• When the Account Owner changes, access to the related Quotes must be updated accordingly, including removing the previous owner's access and granting access to the new owner.
• The required access is managed through QuoteShare records with RowCause = Manual.

Architectural Question

Given the expected Quote volume and the need to automate the insertion and cleanup of QuoteShare records following Account ownership changes:

• Is this approach feasible using a standard Schedule-Triggered Flow, or would Scheduled Batch Apex be required to ensure scalability and avoid governor limits?
• What would be the cleanest architectural pattern for handling the cleanup and creation of Manual QuoteShare records when Account ownership changes?

Thanks for your guidance!

Customer is unable to access

Impact: Unable to view/manage users.

Request:

Please help on the continuous loading issue on the Users page and advise on any permission, configuration, or backend errors causing the behavior. Screenshot attached for reference.