Power Platform Community Forum Thread Details

Nicely format Flows (JSON) when using solutionpackager.exe /action:extract

When "exploding" a solution that contains flows/PowerAutomates the JSON is held on a single line and is hard to diff.

i.e. when a solution contains flows (or SLAs) and the solution is expanded

SolutionPackager.exe /action:extract /zipfile:CustomSLA_1_0_0_1.zip

The exported flows are not nicely formatted and are very difficult to compare over different revisions of the SLA logic. One of the key benefits of using the solution packager is change tracing, which is being made much more difficult since the extract flow JSON is in one long line as demonstrated below.

{"properties":{"connectionReferences":{"shared_commondataserviceforapps":{"runtimeSource":"embedded","connection":{},"api":{"name":"shared_commondataserviceforapps"}}},"definition":{"$schema":"https://schema.management.azure.com/providers/Microsoft.Logic/schemas/2016-06-01/workflowdefinition.json#","contentVersion":"1.0.0.0","parameters":{"$connections":{"defaultValue":{},"type":"Object"},"$authentication":{"defaultValue":{},"type":"SecureObject"}},"triggers":{"[Do not delete or update] Invoked Through Execution Workflow Call":{"type":"OpenApiConnectionWebhook","inputs":{"host":{"connectionName":"shared_commondataserviceforapps","operationId":"SubscribeWebhookTrigger","apiId":"/providers/Microsoft.PowerApps/apis/shared_commondataserviceforapps"},"parameters":{"subscriptionRequest/message":3,"subscriptionRequest/entityname":"slakpiinstance","subscriptionRequest/scope":4,"subscriptionRequest/filteringattributes":"versionnumber,createdon"},"authentication":"@parameters('$authentication')"}}},"actions":{"[Do not delete or update] Switch":{"runAfter":{},"cases":{"[Do not delete] Is Near Non Compliance.":{"case":2,"actions":{"Update_a_record":{"runAfter":{},"type":"OpenApiConnection","inputs":{"host":{"connectionName":"shared_commondataserviceforapps","operationId":"UpdateRecord","apiId":"/providers/Microsoft.PowerApps/apis/shared_commondataserviceforapps"},"parameters":{"entityName":"incidents","recordId":"@triggerOutputs()?['body/regardingentityid']","item/pgc_ragfirstresponse":289920001},"authentication":"@parameters('$authentication')"}}}},"[Do not delete] Is Succeeded.":{"case":4,"actions":{}},"[Do not delete]Is Non-compliant.":{"case":1,"actions":{}}},"default":{"actions":{}},"expression":"@triggerOutputs()?['body/status']","type":"Switch"}},"outputs":{}}},"schemaVersion":"1.0.0.0"}

Can the solution packager output formatted JSON that is friendly to read, and more suitable for standard comparison tools (e.g, diff, WinMerge, etc)? e.g.

{
 "properties": {
 "connectionReferences": {
 "shared_commondataserviceforapps": {
 "runtimeSource": "embedded",
 "connection": {},
 "api": {
 "name": "shared_commondataserviceforapps"
 }
 }
 },
 "definition": {
 "$schema": "https://schema.management.azure.com/providers/Microsoft.Logic/schemas/2016-06-01/workflowdefinition.json#",
 "contentVersion": "1.0.0.0",

Categories:

Application Lifecycle Management (ALM)

Quick Links

Leaderboard > Power Apps - Power Apps Pro Dev & ISV