#Salesforce Admin331 personnes en discutent

Hi Pranav - yes, you can add the extra sites, and the pattern is one External Data Source per SharePoint site rather than reconfiguring the existing one. 

For each new site: 

1. Setup - External Data Sources - New. Type: 'Files Connect: Microsoft SharePoint Online'. Set the Site URL to that site collection's URL (a sub-site collection URL works too). 

2. Reuse your existing Authentication Provider - if the new sites are in the same Microsoft 365 tenant you do not need a new Azure AD app, just select the same Auth Provider in the lookup. (A different tenant would need its own Auth Provider.) OAuth is the only supported auth for SharePoint Online. 

3. Pick the Identity Type per data source: Named Principal (one shared service credential for everyone) or Per User (each user authenticates and inherits their own SharePoint permissions). 

4. Grant access: add each new External Data Source to the relevant Permission Sets/Profiles so users can see it. 

5. Save, then validate/sync - users will see the new site alongside the existing one under External sources in Files and can attach from it. 

So it is the same overall process, just a new External Data Source per site, sharing the Auth Provider wherever the tenant is the same. 

If this helps, please mark it as the Best Answer so it helps the next person - thanks :)

You have it right, Magic Mover COPIES attachments into Files, it does not move-and-delete, so storage temporarily doubles (both the Attachment and the new File exist). That is by design: it leaves the originals so you can verify the conversion before anything is removed. The 'option to delete' not appearing is a common snag, depending on the version that delete step either sits behind a setting or just is not surfaced in the UI you are on. 

To actually reclaim the storage, do it as a deliberate second step AFTER you have confirmed the Files exist: 

1. Verify the conversion. Confirm the new Files (ContentDocument / ContentVersion) exist and are linked to the same records, a quick report on Files or a spot-check of a few records' related lists, before deleting anything. 

2. Delete the original Attachments yourself. Since the tool is not giving you the delete option, the reliable route is Data Loader: export the Attachment object (filter to the ones already converted), then run a Delete on those Attachment Ids. Test on a small batch first. 

3. Empty the Recycle Bin. This is the part that actually frees storage, deleted Attachments sit in the Recycle Bin for about 15 days and still count against your limit until it is purged. Purge it (or they auto-purge after ~15 days) and only then does the storage number drop. 

So: the doubling is expected, the delete is a separate step you drive yourself, and storage only drops once the Recycle Bin is emptied. Run one small test batch end to end (convert, verify, delete, purge) so you are confident before doing it across everything. 

If this helps, please mark it as the Best Answer so it helps the next person. Thanks :)

Good - since it is CPQ, that actually settles the design. Keep the Commercial (operating) account as the transactional account CPQ points its Quotes, Contracts and Orders to, and use the Legal Entity as a bill-to / contract-party lookup rather than moving the transactions onto it. 

The reason: CPQ hangs Contracts, Subscriptions and Assets off the account, and renewals, amendments and asset combination ('Combine Asset Quantities' is an Account field) all key off that same account. So for existing customers, if you migrate them onto a new Legal Entity account you risk breaking the renewal and contracted-price lineage. Safest pattern: apply the two record types from day one for net-new, and for existing accounts keep CPQ pointed at the Commercial account and just add the Legal Entity link. 

If this helps, please mark it as the Best Answer - thanks :)

@Curtis Hale and @Kundan Kumar Jha  

I had a case in for this issue. Here is the response from Salesforce Support: 

 "Based on our investigation, the current behavior appears to be working as designed following a recent product update. We confirmed that this is not related to user permissions, profiles, or configuration changes in your Salesforce org. 

The update introduced changes to the My Feed experience, including: 

The red “X” previously used to dismiss individual feed items is no longer displayed. 

The Open Count is also no longer shown. 

Users can continue to view and filter their My Feed notifications; however, the option to manually dismiss individual items is no longer available in the updated experience. 

This behavior is consistent across users and has also been observed in other Salesforce orgs following the update. Based on the information currently available, it does not appear to be an org-specific issue or product defect. 

Additional information about the related product changes is available in the Salesforce Release Notes: 

https://help.salesforce.com/s/articleView?id=release-notes.rn_sales_sales_engagement_on_core.htm&release=262&type=5

We understand that the removal of the dismiss option affects how your users manage their daily notifications, and we appreciate you bringing this change to our attention." 

@Sahil Gupta

 is cancel option showing besides Lightning Login in Brochan's user record? 

If this is also the same, then I think the setup is correct. Not sure why the challenge is failing. 

Last option would be to sign up for a new org from the 

link -> Change Brochan's email to your email and also set the password -> Enable the Lightning Login option from setup -> Create the two PS as asked in the module: Lightning Login User 

MFA Authorization for Break Glass Admin 

-> Assign both the PS to Brochan -> Enroll Brochan to Lightning Login and login as passwordless 

Try to validate the challenge again. Just validate the specific module where you are stuck, no need to validate the previous steps which are passed already. These are the steps I followed yesterday and it passed the challenge. Good luck. 

Thanks. 

Abhishek