Portals support for Microsoft Power Platform CLI - My take on development and deployment

Resources :

Overview of portals support for Microsoft Power Platform CLI

Power Platform VS Code Extension

Nuget package for PowerApps.CLI

Deployment profile for different environments 

Microsoft Power Platform CLI(Command Line Interface) is a simple, single-stop developer command-line interface that empowers developers and app makers to create code components. With portals support for Microsoft Power Platform CLI, you can now use offline-like capability for portals customization by making changes to the portals content. And once all customizations or changes are saved, upload them to the portal.

To make my work simpler, I have create bat file to run the commands with the authentications. 

  • I have provided the path of the pac.exe from the packages to run the command from my solution. 
  •  auth clear - clears the existing authentication profile, if there is any.
  • auth create - create the credentials to connect with D365 CRM
  • paportal download - downloads the portal from Portal Management
  • paportal upload - uploads the portal from local path to D365 Records.
    • you can deploy portal in different environment using deployment profile. refer to above link. 
Portal-Download.bat : downloads the portal content to specified folder

     ..\packages\Microsoft.PowerApps.CLI.1.9.9\tools\pac.exe auth clear

    ..\packages\Microsoft.PowerApps.CLI.1.9.9\tools\pac.exe auth create -u <D365 URL> -id <Client/App Id associated with D365 application user> -cs <Secret> -t <TenantId>

    ..\packages\Microsoft.PowerApps.CLI.1.9.9\tools\pac.exe paportal download --path "<Path to download portal>" --webSiteId <Website Id from CRM> --overwrite <true/false>

    Portal-Upload.bat : uploads the local content to D365  

     ..\packages\Microsoft.PowerApps.CLI.1.9.9\tools\pac.exe auth clear 

    ..\packages\Microsoft.PowerApps.CLI.1.9.9\tools\pac.exe auth create -u <D365 URL> -id <Client/App Id associated with D365 application user> -cs <Secret> -t <TenantId>
     
    ..\packages\Microsoft.PowerApps.CLI.1.9.9\tools\pac.exe paportal upload --path "<Portal Name>"


    My take on portal deployment in different environments.

    One of the main issue i was trying to resolve is how to deploy portal using devops pipeline in different environments. To achieve that i have creates some steps in pipeline. Below are the images and yaml for the steps

    1. Install Nuget 

    Yaml: 

    steps:

    - task: NuGetToolInstaller@1

      displayName: 'Use NuGet 4.4.1'

      inputs:

        versionSpec: 4.4.1


    2. Install Powerapps CLI as custom command in pac directory.

    Yaml: 

    steps:

    - task: NuGetCommand@2

      displayName: 'NuGet custom install Powerapps Cli'

      inputs:

        command: custom

        arguments: 'install Microsoft.PowerApps.CLI -OutputDirectory  pac '


    3. Run command line task to deploy the portal 

      • With in agent, go in to the folder were pac.exe is installed. 
      • Clear and create the authentication profile using "auth" command.
      • upload the portal using "paportal upload" command.   


    Command line


    cd pac

    cd Microsoft.PowerApps.CLI*

    cd tools

    pac.exe auth clear

    echo creating auth

    pac.exe auth create -u $(DestinationCrmUrl) -id $(DestinationClientId) -cs $(DestinationSecret) -t $(TenantID)

    echo portal upload

    pac.exe paportal upload --path "$(System.DefaultWorkingDirectory)/<Directory path which contain all the files for downloaded portal>" --deploymentProfile <profile name>


    Yaml:

    steps:
    - script: |
       
       cd pac
       
       cd Microsoft.PowerApps.CLI*
       
       cd tools
       
       pac.exe auth clear
       
       echo creating auth
       
       pac.exe auth create -u $(DestinationCrmUrl) -id $(DestinationClientId) -cs $(DestinationSecret) -t $(TenantID)
       
       echo portal upload
       
       pac.exe paportal upload --path "$(System.DefaultWorkingDirectory)//<Directory path which contain all the files for downloaded portal>" --deploymentProfile <profile name> 
       
      displayName: 'Command Line Script - Deploy Portal'


    This is my take on development and deployment of powerapps portal. Please leave comments for suggestion and improvement. 

    Comments

    Post a Comment

    Popular posts from this blog

    Run a flow/Automate from a button on entity form. A ribbon workbench alternative coming up. A COMMAND BAR DESIGNER FOR MODEL-DRIVEN APPS(Preview)

    Image
      Run a flow/Automate from a button on entity form. A ribbon workbench alternative coming up. A COMMAND BAR DESIGNER FOR MODEL-DRIVEN APPS(Preview) Remember the days if we have to customise the command bar and we have to poke around ribbon workbench created by  Scott Durow  which is part of the  XRM Toolbo x. It has served a greater purpose of customising the command bar. There was not an easy way provided by Microsoft to customise these command buttons. Till now. Microsoft is finally rolling out a new (preview) feature that is part of the configuration tools in Dynamics 365 which will allows us to configure the command bar/ribbon in model-driven apps. It is still in preview but it will get better from here. Let’s dive in to it. One of the common requirements from the entity form is to run some actions related to that record. Such as sending an email or getting information from external system or create some unrelated complex recorders etc. Flow is the easies...
    Read more