En este ocasión os dejo un video sobre Vibe Coding en la Power Platform y su evolución con Vibe Power Apps.

Power Platform Analytics is evolving to incorporate insights on the adoption and usage status of Power Apps, Power Automate, and Agents within an organization over the last 28 days. It provides a summarized report by core Power Platform workload, followed by an inventory of Apps, Flows, and Agents:

This new usage Analytics is currently in Preview and, for now, only provides a snapshot of the last 28 days with no option to change the time range.

Este sábado tendré el honor de participar en la edición 2026 del Global Bootcamp de Barcelona en la que realizaré dos sesiones un tanto diferentes. La primera, como no, focalizada en Agentes en el ámbito de SharePoint que en unos días cumple 25 años.

La segunda, como parte del patrocinio de RICOH España, estará orientada a Vibe Coding en la Power Platform.

Agradecer al equipo organizador (Jonathan, Carlos, Toni, entre otros) por contar conmigo en el evento y a mi empresa por hacer posible que participe como Speaker y también se patrocinador platino. Nos vemos este sábado.

El Analytics de Power Platform está evolucionando para incorporar el punto de vista del estado de la adopción y uso de Power Apps, Power Automate y Agentes en una organización durante los últimos 28 días. Se muestra un informe resumido por workload core de la Power Platform y luego un inventario de Aplicaciones, Flujos y Agentes:

Este nuevo Analytics de uso está actualmente en Preview y por el momento da una foto en los últimos 28 días sin posibilidad de poder cambiar el rango de tiempo.

Este miércoles 4 de febrero tendré el honor de volver a participar en la edición 2026 de uno de los eventos de referencia de captación de talento de España: Empleatech 2026. En esta ocasión junto con Enrique Arribas estaré dando una sesión técnica (novedad de este año) sobre Vibe Coding en Power Platform aunque el trasfondo es el cambio de paradigma del desarrollador de software en el presente que tiene que construir software orientado a la especificación sin importar si hablamos de NowCode, Low Code o ProCode. Agradecer a Paco Racionero y a la organización de Empleatech el contar conmigo para las sesiones técnicas del evento.

Azure Local Cluster on‑site working in tandem with Azure Cloud, running Dockerized AI workloads at the edge — is not just viable. It’s exactly the direction modern distributed AI systems are heading.

Let me unpack how these pieces fit together and why the architecture is so compelling.

Azure Local Baseline reference Architecture

A powerful hybrid model for real‑world AI

Think of this setup as a two‑layer AI fabric:

• Layer 1: On‑site Azure Local Cluster
  Handles real‑time inference, local decision‑making, and data preprocessing.
  This is where Docker containers shine: predictable, isolated, versioned workloads running close to the data source.
• Layer 2: Azure Cloud
  Handles heavy lifting: model training, analytics, fleet management, OTA updates, and long‑term storage.

Together, they create a system that is fast, resilient, secure, and scalable

Why this architecture works so well

1. Ultra‑low latency inference

Your on‑site Azure Local Cluster can run Dockerized AI models directly on edge hardware (Jetson, x86, ARM).
This eliminates cloud round‑trips for:

• object detection
• anomaly detection
• robotics control
• industrial automation

Azure Local provides the core platform for hosting and managing virtualized and containerized workloads on-premises or at the edge.

2. Seamless model lifecycle management

Azure Cloud can:

• train new models
• validate them
• push them as Docker images
• orchestrate rollouts to thousands of edge nodes

Your local cluster simply pulls the new container and swaps it in.
This is exactly the “atomic update” pattern from the blogpost.

3. Strong separation of concerns

Local cluster = deterministic, real‑time execution
Cloud = dynamic, scalable intelligence

This separation avoids the classic problem of trying to run everything everywhere.

4. Enterprise‑grade security

Azure Arc, IoT Edge, and Container Registry gives you:

• signed images
• policy‑based deployments
• identity‑bound devices
• encrypted communication

This is critical when edge devices live in factories, stores, or public spaces.

5. Cloud‑assisted intelligence

Even though inference happens locally, the cloud can still:

• aggregate telemetry
• retrain models
• detect drift
• optimize pipelines
• coordinate multi‑site deployments

This is how AI systems improve over time. 

How Docker fits into this hybrid world

Docker becomes the unit of deployment across both environments for DevOps and developers.

On the edge:

• lightweight images
• Hardened images
• GPU‑enabled containers
• read‑only root filesystems
• offline‑capable workloads

In the cloud:

• CI/CD pipelines
• model registries
• automated scanning
• versioned releases

The same container image runs in both places — but with different responsibilities.

My take: This is one of the strongest architectures for real‑world AI

If your goal is:

• real‑time AI
• high reliability
• centralized control
• scalable deployments
• secure operations
• hybrid cloud + edge synergy

…then Azure Local Cluster + Azure Cloud + Docker AI Edge is a near‑ideal solution.

It gives you the best of both worlds:
cloud intelligence + edge autonomy.

Here you find more about Microsoft Azure Local 

Here you find more blogposts about Docker, Windows Server 2025, and Azure Cloud Services :

Windows Server 2025 Core and Docker – A Modern Container Host Architecture

Docker Desktop Container Images and Azure Cloud App Services

The Rise of Free Hardened Docker Images: A New Security Baseline for Developers and DevOps

Containerization has become the backbone of modern software delivery. But as adoption has exploded, so has the attack surface. Vulnerable base images, outdated dependencies, and misconfigured runtimes have quietly become some of the most common entry points for supply‑chain attacks.

The industry has been asking for a better baseline—something secure by default, continuously maintained, and frictionless for teams to adopt. And now we’re finally seeing it: free hardened Docker images becoming widely available from major vendors and open‑source security communities.

This shift isn’t just a convenience upgrade. It’s a fundamental change in how we think about container security.

Why Hardened Images Matter More Than Ever

A “hardened” image isn’t just a slimmer version of a base OS. It’s a container that has been:

• Stripped of unnecessary packages
  Fewer binaries = fewer vulnerabilities.
• Built with secure defaults
  Non‑root users, locked‑down permissions, and minimized attack surface.
• Continuously scanned and patched
  Automated pipelines ensure CVEs are fixed quickly.
• Cryptographically signed
  So you can verify provenance and integrity before deployment.
• Aligned with compliance frameworks
  CIS Benchmarks, NIST 800‑190, and other standards are increasingly baked in.

For developers, this means fewer surprises during security reviews. For DevOps teams, it means fewer late‑night patch cycles and fewer emergency rebuilds.

What’s New About the Latest Generation of Free Hardened Images

The newest wave of hardened images goes far beyond the “minimal OS” approach of the past. Here’s what’s changing:

1. Hardened Language Runtimes

We’re seeing secure-by-default images for:

• Python
• Node.js
• Go
• Java
• .NET
• Rust

These images often include:

• Preconfigured non‑root users
• Read‑only root filesystems
• Mandatory access control profiles
• Reduced dependency trees

2. Automated SBOMs (Software Bills of Materials)

Every image now ships with a machine‑readable SBOM.
This gives you:

• Full visibility into dependencies
• Faster vulnerability triage
• Easier compliance reporting

SBOMs are no longer optional—they’re becoming a standard part of secure supply chains.

3. Built‑in Image Signing and Verification

Tools like Sigstore Cosign, Notary v2, and Docker Content Trust are now integrated directly into image pipelines.

This means you can enforce:

• “Only signed images may run” policies
• Zero‑trust container admission
• Immutable deployment guarantees

4. Continuous Hardening Pipelines

Instead of waiting for monthly rebuilds, hardened images are now updated:

• Daily
• Automatically
• With CVE‑aware rebuild triggers

This dramatically reduces the window of exposure for newly discovered vulnerabilities.

Read the complete blogpost about a Safer Container Ecosystem with Docker: Free Docker Hardened Images here

Exploring Docker Desktop Dev Environments (Beta)

In the ever-evolving landscape of software development, Docker has consistently been at the forefront, providing developers with tools to streamline their workflows. One of the latest additions to Docker’s suite of tools is the Docker Desktop Dev Environments (Beta). This feature promises to revolutionize the way developers collaborate and manage their development environments. Let’s dive into what makes this new feature so exciting.

What is Docker Desktop Dev Environments?

Docker Desktop Dev Environments is a feature designed to simplify the process of setting up and sharing development environments. It allows developers to create, configure, and share their development setups with ease, ensuring consistency across different machines and team members. This is particularly useful in collaborative projects where maintaining identical environments can be challenging.

Key Features

• Environment Configuration: With Docker Desktop Dev Environments, you can define your development environment using a simple configuration file. This file includes all the necessary dependencies, tools, and settings required for your project. Once defined, the environment can be easily replicated on any machine with Docker Desktop installed.
• Seamless Sharing: Sharing your development environment with team members has never been easier. Docker Desktop Dev Environments allows you to package your environment configuration and share it via a URL or a file. Team members can then import this configuration and have their environment set up in minutes.
• Consistency and Reproducibility: One of the biggest challenges in software development is ensuring that all team members are working in the same environment. Docker Desktop Dev Environments addresses this by providing a consistent setup that can be easily reproduced. This reduces the “it works on my machine” problem and ensures that everyone is on the same page.
• Integration with Docker Hub: Docker Desktop Dev Environments integrates seamlessly with Docker Hub, allowing you to store and manage your environment configurations in the cloud. This makes it easy to access and share your environments from anywhere.

Benefits for Developers

• Simplified Onboarding: New team members can get up and running quickly by importing the development environment configuration. This reduces the time spent on setting up and troubleshooting environments.
• Enhanced Collaboration: By providing a consistent environment, Docker Desktop Dev Environments fosters better collaboration among team members. Everyone works with the same tools and settings, reducing discrepancies and integration issues.
• Improved Productivity: With a standardized environment, developers can focus more on coding and less on environment setup and maintenance. This leads to increased productivity and faster development cycles.

Getting Started

To get started with Docker Desktop Dev Environments (Beta), follow these simple steps:

1. Install Docker Desktop: Ensure you have the latest version of Docker Desktop installed on your machine.
2. Create a Dev Environment: Use the Docker Desktop interface to create a new development environment. Define your environment configuration using the provided templates or create your own.
3. Share Your Environment: Once your environment is set up, share it with your team by generating a URL or exporting the configuration file.
4. Import an Environment: Team members can import the shared environment configuration and have their setup ready in minutes.

In the following steps I will Create a Dev Environment in Docker Desktop for Windows:

Click on Dev Environments and then on Get Started

Give your environment a Name, select your source and choose your IDE,
Click then on Continue

Preparing and creating.

Click on Continue

You’re all set and you can open VSCode or your IDE.

Your Dev Environment in Docker Desktop for Windows.

Your Docker Desktop for Windows Dev Environment in VSCode.

Your Dev environment microservices running in Docker Desktop

 

Conclusion

Docker Desktop Dev Environments (Beta) is a game-changer for developers looking to streamline their workflows and enhance collaboration. By providing a consistent, reproducible, and easily shareable development environment, Docker is once again proving its commitment to making developers’ lives easier. Whether you’re working on a solo project or collaborating with a large team, Docker Desktop Dev Environments is a tool worth exploring.
Here you find more information about Dev environments at Docker.

Happy coding!

In my previous blog about image columns in SharePoint, I explained all you need to know about New Image column type in SharePoint online including how to create an image column, how to add image to a list item, where the Images will be stored, etc.

Last year Microsoft added support for displaying images from SharePoint Online/Microsoft Lists to Power Apps canvas apps. Now, Microsoft is adding support for adding, updating, and deleting images from image columns in SharePoint online/Microsoft Lists using Power Apps canvas apps.

Newly created canvas apps that have a SharePoint data connection and are connected to a list can use controls that can add, update, or delete images from the SharePoint list. To use the same functionality in existing canvas apps, you have to delete the existing SharePoint data connection and then re-add it to refresh the data schema.

Configure SharePoint Form control to add pictures/images

Follow below steps to configure SharePoint Form control in canvas app to add pictures/images to SharePoint lists:

1. Create a SharePoint online list and then create an image column in the SharePoint list.

2. Go to make.powerapps.com, create a blank canvas app and add SharePoint list data source.

3. Add Form control in app from Insert > Forms > Edit form

4. Set Data Source property of form control to SharePoint list data source and DefaultMode property to FormMode.New

5. Select form control from tree view, click on Edit fields option from Properties panel at the right side of screen.

6. Add your image column to form using + Add field option on Fields panel and select Add picture as a Control type as shown in below image. Power Apps will add Add picture control inside the data card for image column.

7. Add a button control in canvas app and set it’s OnSelect property to:

SubmitForm(Form1)

8. Now when you run the canvas application, you can select an image from your computer using Add picture control and save it to SharePoint list using SubmitForm() function used in button control.

Using Patch() function to add/update image column using Power Apps

You can also use the Patch() function to add or update an image in image columns in SharePoint/Microsoft Lists using Power apps canvas apps. You can use similar code as given below on OnSelect property of button control:

Patch(
    'Logo Universe',
    Defaults('Logo Universe'),
    {
        Title: TextInputControl.Text,
        Image: ImageControl.Image
    }
)

Delete an image from SharePoint image column using Power Apps

You can delete an image from SharePoint image column using Blank() value for image column in Power Apps Patch function:

Patch(
    'Logo Universe',
    Defaults('Logo Universe'),
    {
        Title: TextInputControl.Text,
        Image: Blank()
    }
)

Limitations

1. Images up to 30MB in size are supported while adding/updating images.
2. Below image formats are supported currently while using this feature.

Supported Image formats

Below image formats are supported currently while using this feature:

• JPG and JPEG
• PNG
• GIF
• TIF and TIFF
• HEIC and HEIF
• JPE, MEF, MRW, NEF, NRW, ORF, PANO, PEF, RW2, SPM, XBM, XCF

Release Timeline

• Targeted Release: Rollout started in late September 2022 (previously early September 2022) and expected to complete by mid-October 2022 (previously mid-September 2022).

• Standard Release: Microsoft will begin rolling out this feature in mid-October 2022 (previously mid-September 2022) and expects to complete it by late October 2022 (previously late September 2022).

Learn more

• Power Apps can now display images from SharePoint Online/Microsoft Lists
• Add an image to SharePoint Image columns using Power Automate
• Add/Update image columns in SharePoint/Microsoft Lists using PnP PowerShell

I hope you liked this blog. Please give your valuable feedback & suggestions in the comments section below and share this blog with others.

Tech giant Microsoft is introducing Embed web part in SharePoint spaces which will allow users to show SharePoint pages or HTML page embed content as an interactable overlay on a SharePoint space. Space viewers will see a thumbnail image in the 3D space that can be viewed as a fully functional HTML overlay when selected by the user. Space viewers that are using a mixed reality headset will only see the thumbnail when selecting the web part unless they return to the browser to interact with the embedded content.

This new feature release will allow users to add content such as:

• Microsoft Forms
• The PowerPoint embed viewer
• SharePoint Pages
• Power Apps

This message is associated with Microsoft 365 Roadmap ID 70732.

Release Timeline

• Targeted release (selected users and entire organization): Roll out will begin in early November and expect to be complete by mid-November.
• Standard release: Roll out will begin in mid-November and expect to be complete by late November.

How this will affect your organization

SharePoint spaces authors will see a new embed web part available in the spaces web part toolbox while designing a SharePoint space.

SharePoint spaces authors will see embed web part as shown in below image:

What you need to do to prepare

You might want to notify your users about this new capability and update your training documentation as appropriate.

Learn more

• SharePoint spaces
• SharePoint spaces to be available by default in New menu

In my previous blog all you need to know about Image column type in SharePoint online, I explained how to create an image column, adding images to SharePoint list items and where the Images will be stored in SharePoint online site.

At the time I wrote that blog, it was not possible to display the images from SharePoint online/Microsoft lists in Power Apps. But, Power Apps image controls can now display images that are stored in image columns in SharePoint online/Microsoft Lists. The Images in Power Apps can be displayed in four different sizes:

• Small
• Medium
• Large
• Full

This feature is associated with Microsoft 365 Roadmap ID 81986.

How this will affect your organization

New Power apps that use the SharePoint connector to add a list as a data source may display images from the list if they are present in the list. Existing apps can also be updated to show images.

Release Timeline

• Targeted release will begin rolling out in late February (previously early February) and will be complete by early March (previously end of February).
• Standard release to all other cloud environments will begin early March (previously early February) and be complete by mid-March (previously mid-February).

What you need to do to prepare

You might want to notify your users about this new functionality and update your training and documentation as appropriate.

Learn more

• SharePoint Online: All you need to know about New Image column type
• Add, update, or delete images in SharePoint/Microsoft Lists using Power Apps
• Add an image to SharePoint Image columns using Power Automate
• Add/Update image columns in SharePoint/Microsoft Lists using PnP PowerShell

I came into a business requirement where I needed to override two out of the box actions to open a custom page instead of the normal out of the Box Quick create or Main form the two scenarios are as below:

Scenario 1:

Overriding the New Record button from a sub grid which usually opens a quick create but in my case I need to open a custom page.

To achieve this please follow the below steps:

1. Create your custom page and Add to your Model Driven App.
2. Create a new web resource to add the functions that open the custom page sample code is as below:

It depends on your scenario you can pass parameters in my scenario I want to pass the parent record Id, so I am passing the execution context and in the next step I will show how we can pass this parameter through the xrmtoolbox.

function OpenCustomPageDialog(executionContext) {
    let formContext = executionContext;
    //Initiating Web Resource Parameter.
    let pageInput = {
        pageType: "custom",// Set pageType as "custom"
        name: "Prefix_CustomPageName", // Custom Page Name
        entityName: "prefix_entityname", // Entity Name
        recordId:  formContext.data.entity.getId().replace(/[{}]/g, '')
    };
    //Declaring HTML Page Dimensions.
    var navigationOptions = {
        target: 2,
        position: 1,
        height: 800,
        width: 1200,
        title: "Transfer Case"
    };
    //Using navigateTo Client API.
    Xrm.Navigation.navigateTo(pageInput, navigationOptions).then(
        function success() {
            // Run code on success
            formContext.data.refresh();
        },
        function error() {
            // Handle errors
            formContext.data.refresh();
        }
    );
}

3. In this scenario we will need to use the XRMToolbox Ribbon workbench as currently we can’t modify the existing commands using the new command bar.

4. So to do this create a new solution and just add your table in the above example it will be the contact as this is the sub grid we need to override its behavior.

5. Load the solution using the Ribbon Work Bench

6. Then navigate to the sub grid select the Add New Button, Right click and choose customise button

7. Go to the command and then go to Actions and remove the existing Out of the box action choose your web resource and add you JS function name and pass the primary control which will be the execution context of the parent record in my case it is the account.

8. Publish your customisation and then you can open the dialog of your custom page , you can choose the position of the dialog and choose whether you need it inline – centre or on the side.

More details on using the navigate to function you can find here.

Scenario 2:

Overriding the the event when selecting a record to open a custom page instead of the normal Main form

1. For this we need to follow the same steps from the previous scenario step 1 to 5
2. On your sub grid you need now to add a new button and Hide it and the whole idea is to use a magic word in the command of the hidden button that does all the magic
3. On the ribbon select the button from the left navigation and drag to the subgrid

4. Right click on the button and select customise command, Set the Id of the new command to: Mscrm.OpenRecordItem the magic word , choose the javascript in the below step and use the parameter: selectedcontrolallitemsid to pass the selected record Ids

5. Same way we need to reference a new JavaScript function and we pass whatever parameters accordingly in this case I am going to pass the record Id which is item is passed from the step above as selectedcontrolallitemsid

function OpenExistingCustomPageDialog(item) {
    //let formContext = executionContext;
    //Initiating Web Resource Parameter.
    let pageInput = {
        pageType: "custom",// Set pageType as "custom"
        name: "prefix_custompagename", // Custom Page Name
        entityName: "contact", // Entity Name
        recordId: item[0]
    };
    //Declaring HTML Page Dimensions.
    var navigationOptions = {
        target: 1,
        position: 1,
        height: 800,
        width: 1200,
        title: "Update Transfer Case"
    };
    //Using navigateTo Client API.
    Xrm.Navigation.navigateTo(pageInput, navigationOptions).then(
        function success() {
            // Run code on success
            //formContext.data.refresh();
        },
        function error() {
            // Handle errors
         //   formContext.data.refresh();
        }
    );
}

6. On the command we need to add an enable rule as below to make sure that the button is always hidden.

7. Now go back to the button and rename the button Id to Mscrm.OpenRecordItem and choose the command we have just created in step 5:

8. Publish customisation and watch the magic happens!

Thanks to the amazing Scott Durrow for the amazing ribbon work bench as well as the details youTube Video on achieving the above, I have just blogged it for easy reference mainly to myself.

Some useful link below:

Pass data from a page as a parameter to ribbon actions

Override the default open behavior of data rows in an entity-bound grid

The new Power Apps PDF Function can generate a PDF document from any screen or control. It makes the task of creating PDFs very simple and only requires a standard license. Once the PDF is generated we can then view a PDF and download a PDF from directly inside of the app itself. In this article I will show you how to use the Power Apps PDF Function.

Table of Contents
• Introduction: The Work Orders App
• Setup The SharePoint List
• Insert A Vertical Container
• Add A Power Apps Form To The Vertical Container
• Enable The Power Apps PDF Function Experimental Feature
• Generate A PDF Of The Power Apps Form
• View The PDF In Power Apps
• Create A SharePoint Document Library To Store PDF Files
• Build A Flow To Download PDF Files From A SharePoint Document Library
• Download The PDF Directly From Power Apps

Introduction: The Work Orders App

The work orders app is used by employees at a plumbing services company to track job details. An employee can view a PDF of the Work Order form on their device and download a copy of the PDF.

Setup The SharePoint List

Create a new SharePoint list named Work Orders with the following columns:

• Map (image)
• Address (single line text)
• LastName (single line text)
• AppointmentStart (date only)
• IssueReported (single line text)
• MaterialsRequired (single line text)

Add a new row to the SharePoint list with this data. We will display it on the Work Order PDF.

Column	Value
Map
Address	67 River Road
LastName	Jones
AppointmentDate	3/28/2021
IssueReported	Water is dripping from the upstairs bathroom into the basement. Homeowner believes it is coming from the bathtub. Only happens when the tub is turned on.
MaterialsRequired	5 – PVC Pipes 1 – Tube Of Sealent 10 – Screws

Insert A Vertical Container

A PDF cannot be generated for a Power Apps Edit Form so we must use a workaround. We can place an Edit Form inside of a container and create a PDF of container’s contents instead. Open Power Apps Studio and create a new app from blank. Insert a vertical container onto the screen.

Make the vertical container fill the screen by giving the following properties these values.

Height: App.Height
Width: App.Width
X: 0
Y: 0

Set the LayoutAlignItems property to this value to make them fill the width of the container.

LayoutAlignItems.Stretch

Add a label to the container to use as a title bar. Give it the text “Work Order” and apply a dark blue fill.

Add A Power Apps Form To The Vertical Container

Next we will create a Power Apps Edit Form to display Work Order information. Open the Data tab from the left navigation menu and add the Work Orders SharePoint list as a data source.

Insert a Power Apps Edit form into the vertical container. Select the Work Orders SharePoint list as the data source.

Update the Edit Form to use a vertical layout with only 1 column.

Use this code in the Item property of the form to display the first record in the SharePoint list. In this tutorial the user will not have an ability to select another record.

LookUp('Work Orders', ID=1)

Change the DisplayMode property of the the Edit Form to View.

DisplayMode.View

Enable The Power Apps PDF Function Experimental Feature

The Power Apps PDF Function is an experimental feature and is not enabled by default. To use it, go to the Settings menu, select upcoming features, then toggle on the PDF Function setting.

Generate A PDF Of The Power Apps Form

When the user clicks on a PDF icon it generates the PDF and navigates to a screen with PDF viewer. Add a PDF icon to the app’s titlebar.

Then write this code in the icon’s OnSelect property.

The first argument to the Power Apps PDF Function tells it which screen or control to generate a PDF from. The second argument can be used to pass in optional values to control the PDF’s size, orientation, margins & DPI. Here we will use the ExpandContainers parameter to ensure the container expands to show any hidden or off-screen controls.

Set(
    varWorkOrderPDF,
    PDF(
        con_WorkOrder,
        {ExpandContainers: true}
    )
);
Navigate('PDF Viewer Screen');

View The PDF In Power Apps

We need to make another screen to display the PDF. Create a new screen named PDF Viewer Screen. Add a dark blue label for a titlebar and insert a left arrow icon in the top-left corner.

Use this code in the OnSelect property of the left arrow icon to navigate back to the previous screen.

Set(varWorkOrderPDF,Blank());
Navigate('Work Order Screen');

Add the PDF Viewer control the screen. Position the PDF Viewer control so it fills the remaining space on the screen.

Use this code in the document property of the PDF. The PDF document will now display in the PDF viewer.

varWorkOrderPDF

Test the feature we built to generate and view a PDF from Power Apps. It should look like this.

Create A SharePoint Document Library To Store PDF Files

We want to create the ability to download the PDF file directly from Power Apps. To do this, we need a place to temporarily store the PDF file. Make a new SharePoint Document library named Exported PDFs. No additional setup is required beyond creating the document library.

Build A Flow To Download PDF Files From A SharePoint Document Library

To download the PDF file we must make a flow to store the PDF file in SharePoint and then return a file download link to the app. Open Power Automate, create a new flow named Download PDF From Power Apps and setup the flow as show in the image below.

Use this code in the File Name property of the SharePoint – Create File action.

triggerBody()['file']['name']

A link to the PDF file in SharePoint opens it in the SharePoint document viewer. However, we want to perform a direct download of the PDF file instead. We can use this special URL to bypass the SharePoint document viewer and download the file. Fill in any tags <> with your own values.

https://<tenantname>.sharepoint.com/sites/<site collection title>/_layouts/15/download.aspx?SourceUrl=/sites/<site collection title>/<file path with the library name>

My completed URL looks like this.

https://matthewdevaney.sharepoint.com/sites/MatthewDevaneyBlog/_layouts/15/download.aspx?SourceUrl=/sites/MatthewDevaneyBlog/Exported PDFs/WorkOrder_20230423081046.pdf

Download The PDF Directly From Power Apps

Now that the Power Automate flow is completed go back to Power Apps Studio and add the Download PDF From Power Apps flow to the app.

Insert a save button icon in the top left corner of the PDF Viewer Screen.

Then add this code to the OnSelect property of the save icon. The Download function downloads a file from the internet to the user’s device. We get the file’s web address returned in the path property of the Download PDF From Power Apps flow.

Download(
    DownloadPDFFromPowerApps.Run(
        {
            name: $"WorkOrder_{Text(
                Now(),
                "yyyymmddhhmmss"
            )}.pdf",
            contentBytes: varWorkOrderPDF
        }
    ).path
);

Test the completed download PDF from Power Apps feature. It should work like this:

Questions?

If you have any questions or feedback about Power Apps PDF Function: Create, View & Download PDFs please leave a message in the comments section below. You can post using your email address and are not required to create an account to join the discussion.

The post Power Apps PDF Function: Create, View & Download PDFs appeared first on Matthew Devaney.

Are you struggling to create a tabbed form in Power Apps? Check out this complete step-by-step tutorial on how to create multiple tabs form in power apps

Recently, we got a requirement to build a tabbed form within the Power Apps while working with the Power Apps’ customized SharePoint form.

That means we will create an app within the Power Apps having multiple tabs such as Personal Details, Education, and Projects. When the user clicks on the ‘Personal Details’ tab, the respective form with fields will be visible. Similarly, when the ‘Education’ tab is clicked, the respective fields will be displayed as shown below:

Create multiple tabs form in power apps

Here, we will see how to create a Power Apps tabbed form. To work with the above scenario, follow the below step-by-step guide:

• We have a SharePoint list named ESP Job Portal having columns such as:

Column Name	Type
Full Name	Single line of Text
Email	Single line of Text
Mobile	Number
DOB	Date
Gender	Choice
Address	Multiple lines of text
Highest Qualification	Choice
Course Name	Choice
University	Choice
Passing Year	Choice
Academic Project	Single line of Text
Project Type	Choice
Project Group	Choice
Skills	Single line of Text

• Let’s integrate the above SharePoint list into Power Apps to create a customized form. For this, on the SharePoint list, click on Integrate > Power Apps > Customize forms.

• It will redirect to the Power Apps by creating customized forms as shown below:

• Add a rectangle to the above custom form and add a text label control to the rectangle. Also, give a name to the label control (Ex: ESP Job Portal).

• Add a blank horizontal gallery to the above screen and place it on the rectangle.
• Insert the below expression on the horizontal gallery’s Items property to create a table.

Items = Table({ID:1, label:"Personal Details"}, {ID:2, label:"Education"}, {ID:3, label:"Project"})

Where, we have created 3 tabbed such as Personal Details, Education, and Project whose IDs’ are 1,2, and 3 respectively.

• Add a button control to the horizontal gallery. Set the Text property as below to display the labels.

Text = ThisItem.label

• Next, we will create a variable using the table’s ID. Using that variable and ID, we will arrange the tabbed form. To create the variable, insert the below expression on the button’s OnSelect property.

OnSelect = Set(VarTabClicked, ThisItem.ID)

Where VarTabClicked is the name of the global variable and ThisItem.ID is the value of the variable.

• Now, select each data card and use the variable to insert the following expression on the Visible property and set an ID.
• For example, if we set the Visible property of the Title data card to ‘VarTabClicked = 1‘, the card will only appear when the Personal Details tab is clicked. Similarly, if we set ‘VarTabClicked = 2′, the data card will only appear when the Education tab is clicked.
• As per the requirement, the client wants to display the Title (Full Name), Email, Mobile, DOB, Gender, Address, and Attachments in the first tab i.e., Personal Details. For this, insert the below expression on each data card’s Visible property as below:

Title's Visible: VarTabClicked =1
Email's Visible: VarTabClicked =1
Mobile's Visible: VarTabClicked =1
DOB's Visible: VarTabClicked =1
Gender's Visible: VarTabClicked =1
Address's Visible: VarTabClicked =1
Attachment's Visible: VarTabClicked =1

Below, we are displaying a screenshot where we have set the DOB data card’s Visible property as VarTabClicked =1.

• Similarly, set the visible property of the Highest Qualification, Course Name, University, and Passing year’s Data card with the below expression.

Highest Qualification's Visible: VarTabClicked =2
Course Name's Visible: VarTabClicked =2
University's Visible: VarTabClicked =2
Passing year's Visible: VarTabClicked =2

As per the above expression, the above-mentioned data card will only appear when the Education tab is clicked.

• Again, insert the below expression on the Visible property of the rest data cards (i.e., Academic Project, Project Type, Project Group, and Skills).

Academic Project's Visible: VarTabClicked=3
Project Type's Visible: VarTabClicked=3
Project Group's Visible: VarTabClicked=3
Skills's Visible: VarTabClicked=3

As per the above expressions, the above-mentioned data cards will appear only when the Project tab is clicked.

That’s it! We can see when the user clicks on any tab, the respective data cards will appear as shown below:

• Finally, we will add a Save icon to the above form and insert the below expression on the icon’s OnSelect Property. As a result, when the user clicks on the icon the inserted data will be saved to the specified SharePoint list.

OnSelect = SubmitForm(SharePointForm1)

Where SharePointForm1 is the name of the SharePoint customized form.

• On the SharePoint list, let’s rename the Title column as Full Name and refresh the data source on the Power Apps. We can see that the Title name is renamed to Full Name as shown below:

Now preview the app and click on each tab to insert the respective data with values. Press the Save icon.

This is how to build a tabbed form within the Power Apps.

Along with this, as we have created this tabbed form by integrating the SharePoint list, we can see this tabbed form within the SharePoint list while creating a new item.

This is how to display a Power Apps customized form within the SharePoint list.

Power Apps tabbed form using canvas app

In the above section, we have seen how to create a tabbed form from the SharePoint customize form within Power Apps. Now, we will see how to create a Power Apps tabbed form using the Canvas app.

For this, we are going to use the above SharePoint list and the following steps are:

• On the Power Apps, create a blank canvas app and give a name to the canvas app. (Ex: Power Apps canvas app tabbed form)
• Connect the above SharePoint list(‘ESP Job Portal‘) to the canvas app.
• On the blank Power Apps screen, add a rectangle and add a text label control. Give a text to the label control i.e., ‘ESP Job Portal’.

• Add a blank horizontal gallery to the screen and place the gallery under the header of the form.
• Insert the below expression on the horizontal gallery’s Items property to create the items.

Items = ["Personal Details", "Education Details", "Project Details"]

Where Personal Details, Education Details, and Project Details are the name of the tabs that we are going to use.

• Add a Power Apps button control into the horizontal gallery and insert the below expression on the button’s Text property.

Text = ThisItem.Value

• To check whether the button(tab) is clicked or not, insert the below expression on the respective properties of the button control.

Fill = If(ThisItem.IsSelected,Color.LightBlue,RGBA(0,0,0,0))
HoverFill = Color.LightBlue
RadiusTopLeft = 25
RadiusTopRight = 25

As a result, now the button control will look like as below:

• Using the button’s text, let’s create a global variable on the button’s OnSelect property. Later we will use the variable for each data card that will appear when the respective tab is clicked.

OnSelect = Set(VarTabClicked, Self.Text)

Where VarTabClicked is the name of the global variable and Self.Text indicates the respective button’s name that has been clicked.

• Now, we will add an edit form to the above Power Apps screen. Connect that edit form to the Sharepoint list and add all the fields to the form.

• As per the requirement, when the user clicks on the Personal Details tab, then the respective certain fields will appear. Such as Full Name, Email, Mobile, DOB, Gender, Address, and Attachments.
• For this, select each above-mentioned data card and insert the below expression on the Visible property.

Full Name's Visible: VarTabClicked = "Personal Details"
Email's Visible: VarTabClicked = "Personal Details"
Mobile's Visible: VarTabClicked = "Personal Details"
DOB's Visible: VarTabClicked = "Personal Details"
Gender's Visible: VarTabClicked = "Personal Details"
Address's Visible: VarTabClicked = "Personal Details"
Attachment's Visible: VarTabClicked = "Personal Details"

Now, we can see all the above-mentioned fields will be visible only when the Personal Details tab is clicked.

• Similarly, let’s set the below expression on certain fields’ Visible properties that should appear when the Education Details tab is clicked such as Highest Qualification, Course Name, University, Starting Year, Passing Year, and Mark Secured in Percentage.

Highest Qualification's Visible: VarTabClicked = "Education Details"
Course Name's Visible: VarTabClicked = "Education Details"
University's Visible: VarTabClicked = "Education Details"
Starting Year's Visible: VarTabClicked = "Education Details"
Passing Year's Visible: VarTabClicked = "Education Details"
Mark Secured in Percentage's Visible: VarTabClicked = "Education Details"

• Again set the rest data cards’ visible properties as the below expression. As a result, when the Project Details will click, the respective fields will appear. Such as Academic Project, Project Summary, Project Type, Project Group, Skills, and Your role in Project.

Academic Project's Visible: VarTabClicked = "Project Details"
Project Summary's Visible: VarTabClicked = "Project Details"
Project Type's Visible: VarTabClicked = "Project Details"
Project Group's Visible: VarTabClicked = "Project Details"
Skills's Visible: VarTabClicked = "Project Details"
Your role in Project's Visible: VarTabClicked = "Project Details"

Now, for a better look, we’ll change the Edit form’s Column property to 1 and DefaultMode to New.

That’s it! Let’s save and publish the app for now. Play the app in preview mode and we can see that when we click on a certain tab the respective fields will appear as shown below:

• Now, we will add two button controls to the above-tabbed form and rename the buttons as Save and Cancel respectively.
• Insert the below expression on the Save button’s OnSelect property to save the inserted data to the SharePoint list.

OnSelect = SubmitForm(Form1)

Where Form1 is the name of the Power Apps edit form.

• Similarly, insert the below expression on the Cancel button’s OnSelect property to cancel or reset the form.

OnSelect = ResetForm(Form1)

Let’s fill in the fields and click on the Save button. We can see the inserted data will save into the SharePoint list.

This is how to build a tabbed form within the Power Apps canvas app using a SharePoint list.

Power Apps tabbed form with required fields

In this section, we will see Power Apps tabbed form with the required fields.

Suppose, there are certain required or mandatory fields available in the above SharePoint list.

Let’s refresh the SharePoint data source list on the above-mentioned Power Apps canvas app tabbed form. Once the data source is refreshed, we can see the required fields (data cards) will appear with the small asterisks symbol.

Also, we can see on the above screen, by default a required message is appearing under the required fields.

In Power Apps, it doesn’t allow saving the inserted data without filling in these fields. We also, observe that the required message automatically disappears once the field is filled as shown below:

Once mandatory fields will fill, we can able to save the data to the data source. This is how to work with Power Apps tabbed form with the required fields.

Conclusion

From this Power Apps Tutorial, we learned how to build a create multiple tabs form in power apps from a SharePoint list based on different scenarios. Such as:

• Build a tabbed form within Power Apps
• Power Apps tabbed form using canvas app
• Power Apps tabbed form with required fields

You may also like the following Power Apps tutorials:

• Get Value from Text input in Power Apps
• How to Get Gallery Item By ID in Power Apps
• Power Apps Set ThisItem Value

Do you know how to upload a file or an image in a Dataverse row using Power Automate? No worries! In this Dataverse tutorial, we will see how to work with Power Automate Dataverse Upload a File or an Image.

In a recent assignment, I had to use Power Automate to upload a file to a certain Dataverse row. And we’ll put it into practice through this tutorial to see how it functions.

Also, Read: Power Automate Dataverse Add New Row

Power Automate Dataverse Upload a File or an Image

Here, we will take one scenario and explore how to upload a file or an image into a Dataverse row using Power Automate.

Example:

• There is a Dataverse table called IT Issue Resolutions. This table has the fields below with different data types. Such as:

1. Sender = This is the Dataverse Primary column with a single line of text data type.
2. Issues = Single line of text data type
3. Report Date = Date Data type
4. Status = Choice Column having some choices like Approved, Rejected, Pending, etc.
5. Attachments = This is a File column. To know more details about the Dataverse file column, read: How to Create Dataverse File Field

• I want to create a flow right now where the sender sends an email with an attachment (file). The relevant file will attach in the specific dataverse row if the sender email contains the given Dataverse sender name.
• For instance, if Sonam sends an email with an attachment (Sonam@tsinfotechnologies.onmicrosoft.com), then the sender’s name will be filtered.
• If the email address is the same as the Dataverse sender name, then the specific file will upload in Sonam’s attachment field as shown below if the requirement is met.

Refer to the screenshot below.

To achieve this above requirement, follow the steps below.

Step – 1: [Create a new automated flow]

• Open Power Automate and Sign in with your valid Microsoft credentials.
• Go to My flows (from the left navigation) -> Expand + New flow -> Select Automated cloud flow under the Build your own from blank section.

Step – 2: [Provide Flow name and Choose the trigger]

• The window shown below will then display, asking you to enter the flow name and select the flow trigger.
  • Flow name = I have given the flow name as Extract Names from Email.
  • Choose your flow’s trigger = Search or select the trigger from the list below to create a flow. In my case, it’s When a new email arrives (V3).
• Click on Create.

Step – 3: [Select Include Attachments]

• Once the flow has been created, the trigger will appear as shown in the screenshot below. Expand the trigger and select Yes under the Include Attachments field.

Step – 4: [Add Get Attachment]

• Click on the + icon and Add an action to insert a new step below the trigger (When a new email arrives (V3)).
• Search Get attachment in the search bar -> Select Office 365 Outlook -> Click on Get Attachment (V2) under the Actions tab.

• Expand the Get Attachment action and enter the below field values as:
  • Message Id = Select the field and click on the Message Id under When a new email arrives (V3) from the Dynamic content. When you will select the Message Id, then the Apply to each action and its value (Attachments) will add automatically.

• The below screenshot represents the Attachment Id.
  • Attachment Id = Select the field and click on the Attachments Attachment Id under When a new email arrives (V3) from the Dynamic content.

Step – 5: [Insert List rows action]

• Then, under the Get Attachment (V2) action, click on the + icon and add a Microsoft Dataverse List rows [PREMIUM] action.

• Once the List rows action has been added, just select the Dataverse Table name (IT Issue Resolutions) from the dropdown menu.
• In the Filter rows field, apply the code below:

contains(crf9a_sender, 'From')

Where,

1. crf9a_sender is the logical name of the Sender (Dataverse column).
2. From, you can take this under the When a new email arrives (V3) action from the Dynamic content.

Check out: Microsoft Flow Error “Could not find a property named ‘crf9a_Sender’ on type ‘Microsoft.Dynamics.CRM.crf9a_itissueresolutions’”

Step – 6: [Upload a file or an image action]

• To upload a file of the specific sender, Click on the + icon and add an action called Upload a file or an image [PREMIUM] action under Microsoft Dataverse.

• Expand the action and fill in the field details below:
  • Table name = Provide the Dataverse table name (IT Issue Resolutions) from the dropdown menu.
  • Row ID = Select the field and click on the IT Issue Resolutions under the List rows action [from Dynamic content].
  • Column name = Select the Dataverse File column name (Attachments) from the dropdown.

• Also, the below fields are there:
  • Content = Select the field and click on the Content Bytes under the Get Attachment (V2) action [from Dynamic content].
  • Content name = Select the field and click on the Attachments Name under the Get Attachment (V2) action [from Dynamic content].

Refer to the screenshot below.

Step – 7: [Save and Test the flow]

• Finally, Save the flow. Click the flow checker as well to see if there are any problems.
• If so, fix it. If not, move on to testing the flow. Select Test.

• Select Manually and click Test as shown below in the Test Flow pane. You must send a new email to your inbox to check whether the flow is functional or not.
• For this, I used Sonam, a different account, to send a message (with an attachment) to my inbox, as shown in the screenshot below.

Step – 8: [Flow ran successfully]

• At the top of the flow, a statement such as “Your flow ran successfully” will appear when the flow eventually completes successfully.

Step – 9: [Refresh the Dataverse table]

• Return to the relevant Dataverse table (IT Issue Resolutions) at this point and perform a single refresh. The image below shows the email attachment that has been added to Sonam’s Attachments space.

Step – 10: [Save the File]

• If you want to save the Dataverse file in your local system, then select the record and click on the Edit row using Form from the top bar.
• In the Dataverse form, click on the file link -> Choose a location to save the Dataverse file -> Click on Save as shown below.

This is how to Upload a File or an Image in Dataverse using Power Automate.

Furthermore, you may like some more Dataverse and Power Apps tutorials:

• Power Automate Get Display Name From Email
• Power Automate Dataverse Update Multiple Rows
• How to Patch Dataverse Number Field in Power Apps
• Dataverse Power BI [Complete tutorial]

In this Dataverse tutorial, we discussed how to work with Power Automate Dataverse Upload a File or an Image.

As part of our continued efforts to improve customer experience in Viva Goals, we are bringing in a few changes to how members of organizations and teams are listed in the admin pages in Viva Goals. 

In March 2023, we rolled out a feature that allowed Viva Goals team admins to add an AAD group as members to a team. As part of this feature, org admins can also add multiple groups as members to an organization. As groups can now be added as members of an organization/team, we will soon be launching an updated members listing page that will list both individuals and groups as members of an organization or team.

This message is associated with Microsoft 365 Roadmap ID 117470

When this will happen:

Standard Release: We will begin rolling out in mid-May 2023 and expect to complete rollout by late May 2023.

How this will affect your organization:

• With the launch of the improved members listing pages, organization admins will be able to view and manage all individual members and groups that are added to their Viva Goals organization in a single list in the Admin > Members page.
• Team admins will also be able to view and manage the individual members and groups added to their teams in a single list in the Team Members page.
• Admins will be able to expand the groups by clicking on them to see all members in a group. Alternately, they can also search for a member (even those who are part of a group) from the search bars in the respective members pages.
• Searching for a member will return all search results directly from AAD (Similar to the search function in MS Teams). Upon clicking on more options, admins will be able to know whether a particular member is already part of the organization or team or not. 

At the team level, if a user in the search result is already part of the team, the more options button will let team admins make the user a team admin or remove the team member from the team. If the user is not part of the team, the team admin can then add the user to the team.

What you need to do to prepare:

At the organization level, if a user in the search results is already part of the organization, the more options button will also let admins perform actions such as assigning admin role, changing user type from observer to regular and vice versa, removing a user and deleting a user. If a user is not part of the organization, the more options button will let admins add the user to the organization. 

Please reach out to your Viva account representative if you have any questions. If you do not have a Viva account representative assigned to you, you can reach us by creating a support ticket in Microsoft Admin Center.

Message ID: MC543873

The post Viva Goals: Changes to Members’ Listing in Organization and Team Administration pages appeared first on M365 Admin.

The new Microsoft Whiteboard app in Teams allows you to create, collaborate and share right within Teams, outside of Teams meetings.

You can now easily access all your whiteboards in one single place inside Teams, pre-prep a board for your next meeting or add a whiteboard tab to your favorite chat/channels to collaborate with your team asynchronously. 

When this will happen:

Rollout begins in mid-April and will be completed by the end of April.  

How this will affect your organization:

There are no changes required, the Whiteboard app comes pre-installed in Teams to supercharge your visual collaboration with a seamless experience. 

What you need to do to prepare:

There is no action required. You have an option to pre-pin the Whiteboard app for users in your tenant. To pre-pin Whiteboard, a setup policy can be created and assigned to the users in Teams Admin Center. 

Please click Additional Information to learn more.

Message ID: MC543868

The post Introducing Microsoft Whiteboard App in Teams appeared first on M365 Admin.

We will be retiring the ability to filter by ‘select file name’ from Microsoft Defender for Cloud Apps. 

When this will happen:

We will begin rolling out this change in mid-May.

What you need to do to prepare:

You are receiving this message because our reporting indicates you may have activity policy using the filter ‘select file name’. You can continue using the ‘select folder name’.

Users will no longer be able to use ‘select file name’ in activity policy, when this change is implemented.

What you can do to prepare:

You may consider updating your training and documentation as appropriate.

Message ID: MC543389

The post Activity policy – filter by file name appeared first on M365 Admin.

In this Power Apps Tutorial, we will see how to get value from text input in Power Apps.

Recently, we were asked by one of our clients to get value from text input. That means when the user inserts any data within the text input control and clicks on a button control, the item will be getting by a data source (Whether it is a collection or SharePoint list). Follow this tutorial, to get the solution.

Along with this, we will cover the below topics based on the Power Apps text input control. Such as:

• Get value from Power Apps text input using a filter function
• Get value from Power Apps text input using the search()
• Get password value from Power Apps text input

Also, Read: How to Get Gallery Item By ID in Power Apps

Get Value from Text input in Power Apps

In this section, we will see how to get the value from a single text input control to a data source.

Here, we are going to use a collection that will display the value that we got from the text input control. To work with these scenarios, the following steps are:

• On the Power Apps screen, we have created a collection ‘CollName’ on the screen visible property.

OnVisible = ClearCollect(
    ColName,
    {UserName: "Johney"},
    {UserName: "Marly"}
)

Where ColName is the name of the collection and UserName is the name of the collection header.

• Add a gallery to the screen and connect it with the collection to show the collected data. For this, set the collection name (ColName) on the gallery’s Items property.

• Next, add a text input control to the above Power Apps screen and give a name to the text input control i.e., UserName_txtInput.
• Add a button control to the Power Apps screen and insert the below expression on the button’s OnSelect property.

OnSelect = Patch(
    ColName,
    Defaults(ColName),
    {UserName: UserName_txtInput.Text}
);
Reset(UserName_txtInput)

As per the above expression, when the user clicks the button the item will store in the collection.

That’s it! We can see that when we insert any item in the text control and click on the button, the collection (that is connected to the gallery) will get that value from the text input. After that, the text input control will be reset to blank.

This is how to get an item from the Power Apps text input control.

Check out: Power Apps Set ThisItem Value [With Real Examples]

Get value from Power Apps text input using filter

In this section, we will see how to get value from Power Apps text input using the filter function. That means when the user inserts any text in the text input control the item will be within a gallery and will be filtered as per the inserted text value.

To achieve this requirement, the following steps are:

• We have a SharePoint list named Products List having different types of columns such as single line of text, date column, choice column, image, etc.
• On the Power Apps screen, we have created a horizontal gallery using the above SharePoint list as shown below:

• On the above screen, add a Power Apps text input control to insert the product’s company and give a name to the text input control.
• Insert the below expression on the horizontal gallery’s Items property.

Items = Filter(
    'Products List',
    Company.Value = Company_txt.Text
)

Where Company_txt is the name of the Power Apps text input control. As the company is a choice column, it is denoted as Company.Value.

• Let’s preview the app and insert a specific company name from the list. We can see the galley will display only the data whose value match to the text input value.

This is how to get value from Power Apps text input control using a filter function.

Have a look: How to Select First Item in a Power Apps Gallery

Get value from Power Apps text input using the search()

In this section, we will see how to get the items from the Power Apps text input control using the search function.

That means, when the user inserts any text input control, it will search the items that contain that given text and display those items within a Power Apps gallery.

To work with this scenario, we are going to use the above Power Apps gallery and the following steps are:

• On the Power Apps screen, insert the below expression on the horizontal gallery’s Items property.

Items = Search(
    'Products List',
    Products_txt.Text,
    "Title"
)

Where Products_txt is the name of the Power Apps text input control and “Title” is the name of the SharePoint list column name.

Let’s preview the app and insert a text within the text input control. Now, we can see that the gallery will display only those items whose title contains the specified text from the text input control.

This is how to get the value from a Power Apps text input control using the search function.

Get password value from Power Apps text input

In this section, we will see how to get password value from a Power Apps text input control. That means, when the user inserts their password via Power Apps text control, it will retrieve that password value from the text input control and collect them on a collection.

To work with this scenario, the following steps are:

• On the Power Apps screen, add two text input controls for inserting the user’s ID and password.

• On the second text input control, set the Mode as Password.

• Add a button control to the above Power Apps screen that will store the data in a secondary storage or collection. Also, give a text to the button control i.e., Save.
• Next, insert the below expression on the button’s OnSelect property.

OnSelect = Collect(
    ColUser,
    {
        UserID: UserID_txtInput.Text,
        Password: Password_txtInput.Text
    }
)

Where,

• ColUser is the name of the collection to store the users’ names and passwords.
• UserID_txtInput and Password_txtInput are the names of the text input controls for the user’s name and password respectively.

• Let’s add a data table control to the above Power Apps screen and connect that data table to the ColUser.
• Add the fields (i.e., User ID and Password) to the data table.
• Save, publish, and preview the app for now. Insert a user ID, and password into the text input control and press the button control.
• We can see that the data table is showing the user ID and password as shown below:

This is how to get the password value from the Power Apps text input control.

Furthermore, you may like some more Power Apps tutorials:

• How to get selected value from gallery in Power Apps?
• How to add text input to Power Apps collection?
• Power Automate Dataverse Update Multiple Rows
• How to format a currency column in Power Apps?
• Power Automate Dataverse Upload a File or an Image

Conclusion

From the above Power Apps Tutorial, we learned how to get value from the Power Apps text input control based on different scenarios such as:

• Power Apps get value from text input
• How to get value from a Power Apps text input using a filter function
• How to get value from the Power Apps text input using the search()
• How to get a password value from Power Apps text input