New Version Release of Collaboration Manager 365: Full Provisioning Engine for Teams and more!

On April 29, 2019 we released an update for our provisioning solution Collaboration Manager 365. 

Here you can find an overview of the new features and bug fixes.

Features:

  1. New provisioning engine for Microsoft Teams. It supports creating, saving, deleting and uploading Teams Templates as well as creating, deleting and synchronizing Teams Workspaces. We also provision the built-in tabs of templates (e.g. pre-configured Planner, Stream, Forms, OneNote). See limitations; this functionality will be published as a BETA feature

  2. Templates of type “Modern Site without Group, Group, Microsoft Teams and Communication Site” now show a banner which indicates that the site collection is a template. This feature requires the Collaboration Manager 365 to be reinstalled and existing templates to be saved again

  3. Improvement to the capability of installing apps from the App Catalog. SharePoint Framework Webparts and SharePoint Hosted Apps from the App Catalog will be installed faster than with the old logic for app installation. Other app types such as Provider Hosted or apps from the SharePoint store won’t be affected by this update. This feature only applies for templates of type “Modern Sites without Group, Group, Microsoft Team and Communication Site” 

  4. New Template Description column in the Templates list. Column will be filled in during template creation. Existing Templates must be updated manually 

  5. New Team Url column in the Templates list. Templates of type “Microsoft Team” will fill in this column when Teams are successfully created. Existing Templates must be updated manually 

  6. New Template Type column in the Templates list. All Template types will fill in this column during template creation. Existing Templates must be updated manually 

  7. New Team Url column in the Workspaces list. Workspaces of type “Microsoft Team” or “Group” will have this column filled in when a new Team is created or a Group is converted into a Team. Existing Workspaces must be updated manually 

  8. Supporting provisioning of Listitems for Templates of type “Microsoft Team, Group, Modern Site without Group and Communication Site”. This functionality will be released as a BETA feature. See limitations

  9. Supporting provisioning of Folders for Templates of type “Microsoft Team, Group, Modern Site without Group and Communication Site”. This functionality will be released as a BETA feature. See limitations 

  10. Supporting provisioning of Documents for Templates of type “Microsoft Team, Group, Modern Site without Group and Communication Site”. This functionality will be released as a BETA feature. See limitations

  11. Supporting Collaboration Manager 365 installation in Modern Sites (Group), Communication Sites and Modern Sites without Group 

  12. Supporting Top links provisioning for Templates of type “Microsoft Team, Group, Modern Site without Group and Communication Site”

Bug Fixes:

  1. Renaming applied to Microsoft Graph consent button. Button name changed from “Allow modern sites” to “Grant Graph permissions” 

  2. Renaming applied to Private field description in the Workspaces list. Description changed from “You cannot change the privacy setting after the group is created.” to “You can change the privacy setting after the group is created.” 

  3. Collaboration Manager 365 Log page now shows the content correctly 

  4. Members and Owners can now be added to Team during Workspace creation 

  5. SPFx web parts can now be provisioned in modern pages. Consider synchronizing affected workspaces in order to solve the problem 

  6. Workspace creation for Teams template does no longer end up with error when Titel does not equal Mailnickname 

  7. Navigation entry for Notebook now refers to the correct Group workspace notebook (instead of the template’s notebook). Consider synchronizing affected workspaces in order to solve the problem 

  8. SharePoint permission groups are now longer in usage in workspaces of type classic site when they have been deleted in template. Fix only applies to new workspaces 

  9. Collaboration Manager 365 installation no longer breaks with Access Denied error

There are some known issues as well as limitations. You can find more details on those here:

 

Visit our Knowledge Base to learn more about Collaboration Manager 365.

If you have any questions regarding the update or our products, don’t hesitate to contact us: support@solutions2share.net

Simplify Teams app package creation with Gulp

Our senior developer Jarbas Horst created a gulp task for creation of Teams app package!

Since SharePoint Framework v1.7 it’s possible to implement Microsoft Teams tabs using SharePoint Framework. Software houses can now support both SharePoint and Teams with the same SPFx web part. In order to simplify the Teams tab development, SPFx v1.7 creates a Teams folder in the solution structure. During development, you must create the Teams app package. Since the process of app package creation isn’t automated, our senior developer Jarbas Horst created a gulp task which does it for you. In his new blogpost, he shows you how to use it!

 

>>Visit Jarbas’ blog to learn more!<<

Hide Site Designs in SharePoint menu

Our senior developer Jarbas Horst has created a SharePoint Framework Extension which hides the Site Designs menu entry of all SharePoint site collections.

Site Design in SharePoint is a powerfull tool which has been available not just for administrators but for certain users since December 2018 as well, allowing these users to apply new Site Designs by themselves. At the moment it is not possible to disable the Site Designs or remove the Site Designs menu entry. For companies this can be problematic for various reasons.

On his blog, Jarbas takes a look at which users are able to see this menu entry at all and explains his SPFx Extension in detail.

>>Visit Jarbas’ blog to learn more!<<

 

Provisioning sites using Hub Sites and Site Design

In August 2018 Microsoft announced improvements and new features for SharePoint hub sites, among them „Adjust sites automatically when they get associated to a SharePoint hub site“. In his new blogppost, our senior developer Jarbas Horst focuses on the capability of provisioning content using site design during hub site association and summarizes the benefits of the new features.

Prospectively, we are planning to connect Collaboration Manager 365 with Hub Sites.

>>Visit Jarbas Blog to learn more!<<

 

Failed to enable remote debugging Exception from HRESULT: 0x89710023

While trying to debug Azure Websites remotely I got the Error “’Failed to enable remote debugging Exception from HRESULT: 0x89710023‘“.

Solution –> Just open the ports 4016 and 4018.

The remote event receiver callout failed.

At the app installation process i got the error “The remote event receiver callout failed.”
After retracting, cleaning and reinstalling i got the same error.

image

Solution –> Restart Visual Studio