SPJeff

Learn how to safely share one SharePoint site across the PowerPlatform lifecycle for ALM. By tagging SharePoint items and files with Environment GUID we can clearly identify the source Environment which created this item. MS Flow triggers with condition logic can “compare” the source SP data Environment GUID to the local current Environment GUID. If matched, proceed with action steps. If not matched, then cancel.

Allows us to streamline overall design, reduce components, while keeping safe isolated lifecycle for PowerPlatform Solutions, Canvas App, PowerAutomate MS Flow, and more.

• Central SharePoint site
• One URL only
• Share safely across PowerPlatform Lifecycle for ALM
• Multiple lifecycle (DEV \ TEST \ PROD)
• Tag SharePoint items with Environment GUID
• MS Flow cancels itself, if current Env not matching SPListItem Env

VIDEO

CODE – MS CANVAS APP ONSTART

// Auto detect current PowerPlatform Environment GUID
Set(varPPEnvironment, PPEnvironment.Run().ppenvironment);

CODE – MS FLOW

workflow().tags.environmentName

SCREENSHOTS

REFERENCES

• https://rajeevpentyala.com/2023/07/12/canvas-app-get-environment-id-without-the-need-of-cloud-flow/
• https://imperiumdynamics.com/blog/Environment-Variables-in-Canvas-Apps.html
• https://learn.microsoft.com/en-us/power-platform/alm/