Edit

Limitations and known issues

  • Article

Note

Currently, Collaboration controls are available only in public developer preview.

Following are the limitations for Collaboration controls:

  • Components can't be used in Canvas apps.

  • Components only support full tab views.

    The screenshot shows the tasks.

  • The subgrid view selected isn't honored. All tasks, meetings, or notes for the collaborative record are displayed.

    The screenshot shows the subgrid view of the tasks.

  • Activities added to the timeline control don’t appear in the components, tasks, meetings, and notes created in the components aren't included in the timeline control.

  • New records must be saved before accessing the components, otherwise you'll see an empty screen.

  • The components don't inherit theming from the form or app they're added to.

  • Localization is only available when running the app inside Microsoft Teams.

  • Microsoft Edge strict mode isn't supported and cross-site cookies are required.

Admin Center does not update when installation or upgrade is complete

When following the installation steps in install Collaboration controls, you're redirected to the Power Platform admin center. A banner is displayed when installation starts, but it isn't updated when installation completes. The status is listed during installation and when it's completed it might not be available in the list. You can view the solutions list at https://make.powerapps.com/ to confirm that installation is complete.

View during installation: The screenshot shows the process during installation.

View after installation: The screenshot shows the completion of the installation.

When upgrading the controls to a later version, the same installation started banner displays, but the control status remains installing even after the upgrade is complete. You can confirm the upgrade is complete by checking the solutions list at https://make.powerapps.com/, it must take approximately 15 minutes.

You can also see in the history for specific solutions that the later version was installed and then the previous version was removed: The screenshot shows the history for specific solutions of the versions that are installed and removed.

Bookings Meetings

The Meetings control supports one on one meetings when using Bookings to engage with users outside of your organization. One to many meetings aren't supported at this time using Collaboration controls.

Meeting attendee status is incorrect

When an attendee RSVPs to a meeting, their response status might not display correctly in both the agenda view and the meeting details. Selecting the decline button might return an error message on screen.

Tasks

Tasks: Filter "clear" text is not translated

The text on the “clear" button displayed on the Tasks filter isn't translated.

Tasks: Grid context menu appears cropped

When the Tasks grid is populated by a low number of Tasks the grid context menu may appear cropped and require use of scrollbars.

Tasks: Keyword search filter use “BeginsWith” operator for “Guest” tasks

When search Tasks using the keyword text filter, “Guest” tasks are returned using the “BeginsWith” operator. “Member” tasks are returned using the “Contains” operator.

Files

When navigating into the Archive folder after archiving files, users might experience duplicate archive folders. Navigating from the archive folder(s) to the files main view resolves the issue, and files that are archived won't be removed.

Controls

Controls fail to save

If a control fails to save a task or meeting, the likely cause is misconfigured Group ID or Channel ID.

Solution 1: Confirm the IDs are correct and the settings are applied as per the settings exercise.

Solution 2: Ensure that the Power Apps environment and Teams environment are on the same tenant.

Controls fail to load or show an error

If the controls fail to load or show an error, it might be a transient issue.

Example:

Screenshot shows the control sync fail.

This would render in the console log as:

Screenshot is an example of control fail from consol log.

Solution: Refresh your browser or if in Teams app, reload the tab.

If you want to change the app name, icon, or description after uploading it to Teams, see customize appearance of apps

Error logging

The controls provide the following methods to debug your application.

  1. Trace logging of plugin events when an API is invoked. This information is stored in your Dataverse environment.

    1. To enable trace logging follow these steps in logging and tracing.

  2. Browser logging for UI controls. This is standard console logging.

    1. It's supported when using a browser to run the Collaboration Manager app via Power Platform and Teams web.
    2. Within the console tab, you can search for errors using the Collaboration Manager error message or searching for Collaboration Manager control names such as Tasks.

Tip

If an error occurs in a Teams desktop client, try to replicate in Teams web to capture the error log.

FAQ


What are the Collaboration controls (Preview)?

Collaboration controls (Preview) enable you to add Microsoft 365 capabilities to your Power Apps line of business custom applications to simplify user workflows when collaborating on business processes in Teams or Power Apps.



What is the benefit of the Collaboration controls (Preview) for makers?

With these new controls, you as a maker can drag-and-drop controls that bring Microsoft 365 collaboration to your app.



What is the benefit of the Collaboration controls (Preview) for users?

Your users can experience productivity gains and stay in their flow by collaborating on approvals, files, meetings, notes, and tasks without leaving the context of your app.



How do I get access to the Collaboration controls (Preview)?

Request that your Power Platform administrator install the controls from AppSource to your Power Apps environment.



How do I add the controls to a Model Driven App?

Go to Form Designer and drag the controls from the Component pane onto a form.