From the Microsoft Power Platform blogs: Adding tabs to forms; Environment variables; Automate business PDFs; Copilot Studio and deep reasoning

In this review of the Microsoft Power Platform blogs:

• Power Pages: Adding tabs to forms using web link sets
• Power Platform environment variables, default vs current values
• How Copilot Studio leverages deep reasoning for intelligent support operations
• Automating business PDFs using Azure Document Intelligence and Power Automate

Power Pages: Adding tabs to forms using web link sets

On the Engineered Code blog, Nicholas Hayduk wrote that over the years, Microsoft has changed its approach to showing tabs in model-driven Power Apps and Microsoft Dynamics 365 Customer Engagement. 

He pointed out that sometimes tabs are available, and sometimes they’re not. He noted that Power Pages, however, has stayed consistent. It does not use tabs, and all sections appear in one long form.

In his blog post, Hayduk showed you how to create your own tabbed interface in Power Pages using web link sets.

Hayduk added that while web link sets are one way to do this, another option would be to create a parent page, with each of the tabs being a child page of the parent page. He stated that you can then craft Liquid code to loop through the child pages in a similar manner.

Power Platform environment variables, default vs current values

Writing on his blog, Pieter Veenstra stated that when you use multiple environments in the Power Platform, you will almost always need environment variables.