Skip to main content

Notifications

Community site session details

Community site session details

Session Id :
Customer experience | Sales, Customer Insights,...
Unanswered

d365 sharepoint integration for multiple sites

(1) ShareShare
ReportReport
Posted on by 10

When you enable server-based SharePoint integration, you are asked to enter the URL of one SharePoint site where you want the documents to be stored in folders that correspond to records in an entity. But you are able to select multiple entities.

But SharePoint promotes flat IA. We have a Loans site with hundreds of folders, each for a loan deal. And we have a CDS Loan entity - that seems simple enough - for every loan record in CDS, a corresponding folder exists in SharePoint. But we also have a site for "Programs"; each program has its own program documentation, curricula, budgets, etc. And there is a CDS Program entity. Conceptually, loans belong to one or more programs and one account belongs to one or more loan. So Account and Loan are 1:n but Loan and Program are n:n, meaning on the SharePoint side you can't nest loan folders inside of account folders inside of program folders.

As it is, staff go to the Loans SharePoint site to access their loan deal folders - it looks clean and can be filtered by metadata on the folders. Staff go to the Programs SharePoint site to access the folders for each program - looks clean, can be filtered by metadata. These two types of folder cannot be in the same site because the folder metadata is different.

How should this be handled in d365/model-driven power apps? You can't just have one site in SharePoint.

  • Sushma Patole Profile Picture
    244 on at
    RE: d365 sharepoint integration for multiple sites

    Hi Ryn,

    You got anything for this?

  • Don Wisch Profile Picture
    660 on at
    RE: d365 sharepoint integration for multiple sites

    We have all of our customers created as sites on SP then we built MS Teams for each of them.   From there, we created SP site location records for each of them and do not use the OOB site that is assigned.  We take this a step further with SP Doc Location records (see below).  For our support, we created a power automation that creates SP Doc Location records for every support case that is created for our customers.   Below is the hierarchy in our environment which uses multiple SP Sites  What we end up with is basically a document record location at every level that we deal with... from customer to support cases.

    Per Customer , we have established the following parent child records in CRM

    • SP Site - CRM Customer - MS Team
      • CRM Shared Document Location Record
        • CRM General Support Location Record
          • CRM Support Location Record
            • CRM Support Case Record 1
            • CRM Support Case Record 2
            • CRM Support Case Record 3
            • etc. ....

                                   .

    Not sure if this helps or not.    

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Announcing the Engage with the Community forum!

This forum is your space to connect, share, and grow!

🌸 Community Spring Festival 2025 Challenge Winners! 🌸

Congratulations to all our community participants!

Adis Hodzic – Community Spotlight

We are honored to recognize Adis Hodzic as our May 2025 Community…

Leaderboard > Customer experience | Sales, Customer Insights, CRM

#1
Daivat Vartak (v-9davar) Profile Picture

Daivat Vartak (v-9d... 225 Super User 2025 Season 1

#2
Muhammad Shahzad Shafique Profile Picture

Muhammad Shahzad Sh... 106 Most Valuable Professional

#3
Eugen Podkorytov Profile Picture

Eugen Podkorytov 102

Overall leaderboard

Product updates

Dynamics 365 release plans