Breaking news from around the world
Get the Bing + MSN extension
Now Available in Community - MBAS 2019 Presentation Videos
Catch the most popular sessions on demand and learn how Dynamics 365, Power BI, PowerApps, Microsoft Flow, and Excel are powering major transformations around the globe. | View Gallery
2019 release wave 2 Discover the latest updates to Dynamics 365Release overview guides and videos Release Plan | Early Access Availability
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 | Talent TechTalks | Upcoming TechTalks
I got a requirement to create folders on a Sharepoint Online site whenever a record is created. The downside of that is, it's not just the folder for the CRM record, I have to create two subfolders.
One of them is public and everyone can see them and the other one (that's my problem) is private and only the creator can see them and people who are in an access team of the specified CRM record.
Is this possible to do with an Azure function? If not, what should I use and how can I do that?
You could do this with the help of Flow.
With the Copy folder action of the SharePoint connector you're able to copy a folder structure to a target location.
Or you could create to 2 dummy files (Create file action) to create the subfolders and then delete the files again.
Setting permissions on the folder can be done:
The challenge is to get the users of the access team in Flow.
Setting permissions is now part of the SharePoint connector:
This turned out to be much easier than I first thought, especially with the new actions of the SharePoint connector in Flow.
I've written a blog post about it with a solution:
Thank you Stefan. this helped me a lot and I used it successfully.
I might even add I had 2 access teams and I just used a condition to see which one is which and created a folder with subfolders.
For example the recordbasefolder had a subfolder 1 and a subfolder 2. Users of access team A could see both subfolders and members of access team B could only see subfolder 2 and couldn't see subfolder 1 like it never existet.
Business Applications communities