Announcing Power BI in Microsoft Teams collaboration experiences improvements

-

It’s January and we’re excited to start the year on the right foot by announcing enhancements to the Power BI in Microsoft Teams experiences. Today we’re announcing three new capabilities that are starting to roll out, and a hint about things to look forward to in the coming weeks.

 

Rich preview cards for Chat in Teams

We’re committed to helping users communicate insights faster. The Chat in Teams experience is getting better because we’re updating Chat in Teams links to be easier to read, shorter, and to show rich preview cards.

When you use Chat in Teams for a report or from a visual, you’ll notice the link now looks like a regular Power BI link, not a Microsoft Teams link. The link is still a deep link that takes users directly to the exact data they selected on the specific page of a report. Clicking the link opens the report in a browser window.

The experience gets even better when you have the Power BI app installed in Teams. The link will automatically generate a rich preview card. The card shows the report name, description, workspace, and an open button the opens the report in the Power BI app in Teams for a seamless experience.

Listening and learning from your experiences and needs

On the Power BI team, we cherish user feedback, our community, and strive to improve our products to make it easier, faster, and more delightful for you to get your work done. We always encourage users to ask for features on ideas.powerbi.com, where you can track progress and vote for capabilities suggested by other users. Most Teams users don’t know they can do that.

Now, we’re enabling a new Give us feedback option for Teams, Outlook, and Microsoft 365 users in the Power BI app. You’ll find the new option in the header bar on home.


When you press Give us feedback, we’ll launch a survey dialog.


In the dialog, you can rate your experience and tell us how we can improve the experience.

Users can submit the survey whenever they feel they’d like us to improve something or even to offer us encouragement 😊. Similar surveys are available for Power BI in Outlook and Power BI in Microsoft 365 (office.com).

If you’d like to track your feature suggestions, continue to use ideas.powerbi.com. Remember to mention Microsoft Teams, Outlook, or Microsoft 365/Office.com so we can easily find them.

 

Upgrade for legacy Power BI tabs is coming soon for Channels 2.0

When we first started our Power B in Microsoft Teams journey, we released an early version of the Power BI tab with limited viewing experiences that worked in Team’s channels capability.

Now, with Team’s Channels 2.0 experiences these legacy tabs need to be upgraded. We’re enabling upgrade experiences now so that when channels 2.0 is enabled for your team, you can smoothly upgrade. Once you upgrade, your team will have access to the richer capabilities of the latest Power BI tab.

Don’t worry if you never get prompted to upgrade a Power BI tab. All newly created Power BI tabs already use the latest version of our Power BI tab and won’t need to upgrade. In fact, the vast majority of Power BI tabs in use today are not legacy tabs. This means that most users and teams won’t need to upgrade their tabs.


Source: Microsoft

Comments

Post a Comment

Hi User,
Thanks for visiting My Blog and please provide your valuable feedback and subscribe for more updates. Please don't post any spam content or comments.
Thank You

Popular Posts

Failed to execute the package or element. Build errors were encountered

-
Error: TITLE: Microsoft Visual Studio ------------------------------ Failed to execute the package or element.   Build errors were encountered. For more information, see the Output window. ------------------------------ BUTTONS: OK ------------------------------   Solution: We tried to close SSDT and run it again but, we still got the same error while running SSIS package. Then, we need to follow bellow solution: Step 1: Go to Task Manager–> Details Tab. Step 2: Locate the process “ DtsDebugHost.exe “. Kill this process. There might be multiple instances of this process. Kill all of them. Step 3: Rerun SSIS package
Read more

Exception deserializing the package "The process cannot access the file because it is being used by another process."

-
TITLE: Microsoft Visual Studio ------------------------------ Failed to start project ------------------------------ ADDITIONAL INFORMATION: Exception deserializing the package "The process cannot access the file 'E:\SSASCube\HistoricalDataLoad\HistoricalDataLoad\bin\Development\HistoricalDataLoad.ispac' because it is being used by another process.". (Microsoft.DataTransformationServices.VsIntegration) ------------------------------ The process cannot access the file 'E:\SSASCube\HistoricalDataLoad\HistoricalDataLoad\bin\Development\HistoricalDataLoad.ispac' because it is being used by another process. (mscorlib) ------------------------------ BUTTONS: OK ------------------------------ While running SSIS package i got the error “The process cannot access the file ‘*.ispac’ because it is being used by another process”. I tried to close SSDT and run it again but, I still got the same error while compiling. Then, after searching over internet, I got
Read more

Temporary enable and disable SSRS subscriptions

-
--Code Snippet --To Check Subscription Status. USE ReportServer GO SELECT dbo . Subscriptions . Description ,        dbo . [Catalog] . Name ,        dbo . Users . UserName ,        InactiveFlags FROM dbo . Subscriptions      INNER JOIN dbo . [Catalog]      ON dbo . Subscriptions . Report_OID = dbo . [Catalog] . ItemID      INNER JOIN dbo . Users      ON dbo . Subscriptions . OwnerID = dbo . Users . UserID --Temporary disables subscriptions while data warehouse is unavailable UPDATE dbo . Subscriptions SET InactiveFlags = 1 GO --After this you can find, all the subscription where disabled until you again enable it. --Again enable subscriptions. UPDATE dbo . Subscriptions SET InactiveFlags = 0 GO
Read more