Menu Close

Blog

Slide 1

Microsoft Business Applications Blogposts, YouTube Videos and Podcasts

Helping Businesses with Technology

Slide 2

Microsoft Business Applications Blogposts, YouTube Videos and Podcasts

Helping Businesses with Technology

Slide 3

Microsoft Business Applications Blogposts, YouTube Videos and Podcasts

Helping Businesses with Technology

previous arrow
next arrow

{How to} Install Power Platform Pipeline for Power Platform Managed Environments

Hello Everyone,

Today i am going to show how to install Power Platform Pipeline in Power Platform for Managed Environments.
Lets gets started.
There are some prerequisites:

 

  • Microsoft recommends four Power Platform environments like dev, uat, pre prod, production.
  • But can be implemented with atleast 3 environments to create the power platform pipeline.
  • Must have Dataverse Database.
  • Microsoft Dataverse for teams isn’t supported currently by Microsoft.
  • Should have Power Platform Administrator, or Dataverse system Administrator role.
  • All environments including dev and production used in the Pipeline should be enabled as managed environment.
In Microsoft terminology they recommend as
Host environment – Production
Dev Environment – Development Environment
Target Environment – UAT, Integration Testing, Production.
In a nutshell: Each environment should have unique name for environments.
So install the Pipeline application in the Host environment(Production).
Open the Production environment and click on the “Resources” and enlarge it and click on the “Dynamics 365 Apps”
Refer to below screen shot.
Then a list of Dynamics 365 Apps displayed on the screen and look for Power Platform Pipeline, click on the “…” and click install.

 

New pop up will appear on the righthand side of the screen.

choose the “Environment” and agree terms and conditions. Click Install.

Installation started, refer to the above screen.

Then copy all environments id’s which are participating the Power Platform Pipeline.
Then check the Deployment pipeline in the environment you have enabeld the Pipeline.

List of Power Apps will be displayed.

Open the “Deployment Pipepline Configuration” App from the Apps – Dynamics 365

Then create the the new environment records from the Model Driven App.

Similarly create environment record for the target environment

Then select the “Pipepline fron the left navigation pane.

Create a new deployment pipeline:

 

Additionally when we install Pipeline for the environment, new security roles created and users who are going to administration needs to have these roles assigned.
1. Deployment Pipeline Administrator
2. Deployment Pipeline User
Assign “Deployment Pipeline User” role to Power Apps makers, it doesn’t allow to create, edit, delete pipelines
Read previlege will be sufficient for makers on Pipeline record.
Makers must also have previlege to export solutions from source development environments, as well as privileges to import solutions to the target test and production environments for which the pipeline deploy to. By default system customizer and environment maker roles have these privileges.
You can also share with pipeline administrators, they should have access to all the environments with in the pipeline.
Finally we can manage all in one place and monitor deployments.
I hope this helps
Malla Reddy(@UK365GUY)
Share this:

{How to} enable Managed Environments in Power Platform Admin Center and its use case scenario.

Hello Everyone,

Today i am going to show to enable Managed Environment and Its use in Power Platform Admin Center.
Lets gets started.
Head over to Power Platform Admin Center.

 

Click on the environments on the lefthand of the PPAC and then set of environments related to your tenant will be displayed.
Now we have to enable managed environment for one the environment from the list.
In my use case, i have chosen GMR IT SOLUTIONS2 and clicked on the “Enable Managed Environment”.
A new window will appear on the righthand side of the screen.
Once enabled to view licensing details all Power Apps, Power Automate or Dynamics 365 License with Premium use rights to use the repective resources in this environment.
See below screenshot to see licensing reporting:

 

Limit Sharing:
 
Suppose you have many Canvas Apps and you want to set restriction on sharing.

 

Check the “Limit total individuals who can share to” set the number 1 or 5 or 10, depending upon your organisation citizen developers or Power Platform Dev team.
Solution Checker(preview):
 
Solution checker is in managed environment have 3 stages
1. None
2. Warn
3. Block
Solution Checker will check in managed environment during solution import will check the security and its reliability validations during each stage.

 

Also when the solution is at block stage it will notify the admins when its checked.
Usage Insights:

 

With the Usage Insights we will get insights of top apps and flows being used in the environment within the tenant.
Maker welcome content(preview):
 
 


Maker welcome screen is in preview so you can start using it in development purpose once it is in general availability you can into production.
So in maker welcome you can show customized page for makers.
You can show learn more url by placing url in the learn more URL area.
Data Policies:

 

Data policies will help to set a limit on the connectors to protect the data within the organisation.
I hope this helps.
Malla Reddy(@UK365GUY)
Share this:

{How to} use Configuration Page in Power Platform and Dynamics 365

Hi Everyone,

Today i am going to show how to use configuration page in Power Platform and Dynamics 365 Solutions.
What is Configuration Page: Configuration Page is used to track the solution deployed from dev to uat or production, what are the changes in the deployed solution and its easy to track the changes in future.
Lets gets started.
Now we need to create a Configuration Page, go to the Power Platform or Dynamics 365 Solutions area.
In this blog post i will show from Power Platform maker portal.

 

Click on the solutions and list of solution already deployed will be shown, in our case click on “New Solution” and then fill up the solution name and publisher, here the configuration page is “NONE”, then create the solution.
Open the newly created solution and create webresource from it.
save and publish webresource.
So the webresource is part of the solution.

 

Go back to the solutions area and select the new solution created and click on “…” then click on settings as you can see from the above image.
Select the newly created webresource in the configuration page and update the solution.

 

Head over to the Classic view to see how the confirguration page looks like on the Dynamics 365 Model Driven App.

 

As you can see from the above image the configuration page note information related to the solution.
So it will help to track the changes deployed to other environments.
I hope this helps.
Malla Reddy(@UK365GUY)
Share this:

{How to} Create a Custom Security role in Dynamics 365 Sales Model Driven App

Hello Everyone,

Today i am going share a new feature which has been introduced recently about the custom security role in Dynamics 365 Customer Engagements, Model Driven Apps.
Previoulsy if we need to create a custom security role, we use to copy similar or minimal previleges role and create a custom security role.
So Microsoft now have introduced new Custom Security role where we can use it and recreate custom security role.
How ?
Lets gets started:
Login into Dynamics 365 and head our to Settings in Classic View or through Power Platform Admin Centre(PPAC).
Open the environment of your choice of Model Driven App

 

Click on Settings and security roles, select the App Opener security and click on the “…” you will see copy, edit, delete.
Click on Copy and new pop up will come and name the new security role again click on Copy.

 

A new security role will be created.
    Then select the New “App Opener Manager” role and click elipses “…”
you will see three options
 1. Copy
 2.  Edit
 3. Delete
Select the 2 option : Edit
New window will open with all the previleges and give appropriate previleges and save and close the security role.
Now we may need to add this new security role to the Model Driven App:

 

1. Select the App we need to share with the new security role: App Opener Manager
2. Then click on the …  and then on the “SHARE” button.
3. New Window will come on the right hand side
4. Select the App and assign the New Security Role: App Opener Manager.
5. Finally click on the Share Button.
Now we have created a new custom security role successfully.
I hope this helps.
Malla Reddy(@UK365GUY)
Share this:

{How to} resolve A record with these value already exists, a duplicate record cannot be created, select one or more unique values and try again.

Hi Everyone,

Today i am going to show to resolve error message while importing the data into Dynamics 365 Sales.
Sceanrio: whenver you import data into Dynamics 365 Sales you may face this issue:
” A record with these value already exists, a duplicate record cannot be created, select one or more unique values and try again “,
How to resolve this?

 

Lets gets started.
When we import the data into Dynamics 365 Sales the error message itself says this record already exists.
Duplicate records can not be created.
So if you still want to create record already exists then you may need to revisit the record you are trying to import and make changes required and import again with modified values which will not be same as record that already exists.
I hope this helps.
Malla Reddy(@UK365GUY)
Share this: