Personalized Community is here!
Quickly customize your community to find the content you seek.
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2020 Release Wave 2Discover the latest updates and new features to Dynamics 365 planned through March 2021.
Release overview guides and videos Release Plan | Preview 2020 Release Wave 2 TimelineWatch the 2020 Release Wave 1 virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
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.
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
Not sure if this helps or not.
Business Applications communities