SharePoint Server Subscription Edition Installation with minimize expenses

 

I created my farm using the guide found on this page: SharePoint Server 2016 dev/test environment in Azure - SharePoint Server | Microsoft Docs

 

However, I did a bit of adjustment of the VM creation scripts to accommodate the following:

1. Using new versions of Windows Server, SQL Server and SharePoint Server which are aligned with new system requirements for SharePoint Server Subscription Edition
1. Windows Server 2022
2. SQL Server 2019
3. SharePoint Server Subscription Edition
2. Adjusting VM size based on my other test farm (SP2016+19) to minimize expenses

 

I also configured auto-power-off for all VMs so that they will be shut down automatically at 7PM if they are on (that is done in the Azure portal).

 

All of the four changed PowerShell segments are attached in the compressed zip file. The rest of the process stays the same like described in the document above.

Download Scripts: Scripts

Issue with exporting PowerApps solution In default environment

 

Issue:

We are facing issue while exporting a power apps solution from default environment "ABC". Error attached below.

Solution "ABC" failed to export: Principal with id e96d176f-3487-eb11-a812-000d3ab52d2a does not have ReadAccess right(s) for record with id 21b01452-9f7d-ec11-8d21-000d3a66509a of entity workflow. Details: {"CallerPrincipal":{"PrincipalId":"e96d-a812-000d3ab52d2a","Type":8,"IsUserPrincipal":true},"OwnerPrincipal":{"PrincipalId":"3ee8fac0-3687-eb11-a812-0d2a","Type":8,"IsUserPrincipal":true},"ObjectId":"21b01452-9f7d-ec11-8d21-000d3a66509a","ObjectTypeCode":4703,"EntityName":"workflow","ObjectBusinessUnitId":"7581668f-6f11-e911-a99d-000d3ab78b73","RightsToCheck":"ReadAccess","RoleAccessRights":"None","PoaAccessRights":"None","HsmAccessRights":"None","GrantedAccessRights":"None","Messages":["PrincipalHasOwnerPrincipalWithAtLeastBasicPrivilegeDepth = False","EntityUserGroupRights = None","MinimumPrivilegeDepthRequired = Local","SecLib::AccessCheckEx2 failed. Owner Data: User principal 3ee8fac0-3687-eb11-a812-000d3ab52d2a is not loaded in UserDataCache yet; Principal Data: roleCount=6, privilegeCount=1538, accessMode=0"],"EntityOwnershipTypeMask":1,"CallerInfo":{"IsSystemUser":false,"IsSupportUser":false,"IsAdministrator":false,"IsCustomizer

Resolution:

Based on the below error ,  it seems that the solution contains a flow not owned by user https://ABC.crm4.dynamics.com/api/data/v9.1/systemusers(e961-a812-000d3ab52d2a).

 

So based on information provided here: Security roles and privileges - Power Platform | Microsoft Docs, Local would be the minimum security role access level required for allowing to successfully export the solution

To resolve this issue, please take the following steps:

An environment admin should browse to the Power Platform Admin center https://admin.powerplatform.microsoft.com 

1.       Select the environment(s) with this issue

2.       Click Security Roles > See all

 

 

Select environment maker role and select Edit

Click the Customization tab

 

 

 

In the grid of circles, enable Read permission on the Process row to Business unit level of permission .

SPFx Form Customizer Extension To Customize SharePoint New/Edit/Display Form Of List/Libraries

Microsoft has recently released SPFx 1.15.1 Preview version adding a few new features and updates for building SPFx-based solutions. We can find full release notes at the link. With this release we can customize complete SharePoint list form using. SPFx full blog with example.

https://www.c-sharpcorner.com/article/spfx-form-customizer-extension-to-customize-sharepoint-neweditdisplay-form-of/

Change the owner of cloud flow

https://docs.microsoft.com/en-us/power-automate/change-cloud-flow-owner

https://powerautomate.microsoft.com/sv-se/blog/team-flows/

ALM Accelerator for Power Platform - Pros & Cons

 Microsoft released another innovate tool to Manage Power Platform (Canvas & Model driven) Applications using Application Life cycle Management(ALM)

Ste by step guide : https://powerapps.microsoft.com/en-us/blog/introducing-the-alm-accelerator-for-power-platform/ 

My first Impression with ALM

ALM Accelerator is tightly coupled with Azure DevOps & git, but there no link between recent relese features like CO- Authoring features, So by end citizen developers should maintain 2 git repos for store same solution.

Setup & maintenance complexity is same like earlier version. this tool is good fit for small originations not for Enterprises.

Co-Authoring in Power Apps - Limitations

Microsoft released many new features in Power Platform in 2021, there are 2 main features are very useful for developers. 

Co-Authoring as an experimental feature to Power Apps.

Co-Authoring as an experimental feature to Co-Authoring in Microsoft Teams. 

Co-Authoring in teams lets you edit a document while another person is editing the same document.

With Power apps it is just the same. You can edit one app with multiple people at the same time.

Be aware though that enabling Co-authoring is more than just enabling a feature. When multiple people edit the same app, it is very important that you use the same standards and that you are aware of which parts each person is working on. like Standard development / release Life-cycle using Version controls (Gits or Devops)

Saving your work on a regular basis, and collecting other people’s changes regularly might be a good idea.

Based on documentation, I tested in both Azure DevOps & git repos. found few bugs in additions limitations. 

https://docs.microsoft.com/en-us/powerapps/maker/canvas-apps/git-version-control.

Steps Followed:

1. Created Github Repository
2. Generated a personal access token for my ID in github
3. Created a canvas app and connected it to Github repository
4. Provided github repo and canvas app access to another user
5. User needs to generate a personal access token for himself
6. Edit the app and other user must provide his github credentials

Now both users can edit and work on the app simultaneously

Known limitations

1. This feature isn't compatible with code components. Don't use this feature with apps that make of use of code components.
2. This feature doesn't work with public Git repository. Use a private repo instead.
3. This feature doesn't work with on-premises Git repositories. The Git repo must be hosted on the web and accessible with username and personal access token.
4. Edits to the same property on the same control aren't merged. The last edit made will win.

Additional findings :

Co-authoring feature is not working for Dataverse & SQl  tables, but SharePoint works fine without any issue.