{"id":1969,"date":"2022-01-10T08:40:08","date_gmt":"2022-01-10T08:40:08","guid":{"rendered":"https:\/\/365stack.in\/?p=1969"},"modified":"2022-01-10T09:01:38","modified_gmt":"2022-01-10T09:01:38","slug":"how-to-do-deployment-via-solutions-in-power-platform","status":"publish","type":"post","link":"https:\/\/365stack.in\/index.php\/2022\/01\/10\/how-to-do-deployment-via-solutions-in-power-platform\/","title":{"rendered":"How to do deployment via Solutions in Power Platform"},"content":{"rendered":"\n

Deploying artifacts from one environment to another is an integral part of application life cycle management. Solutions are the Microsoft recommended way to do the development for easing out the deployment part. The problems which we faced in the Export and Import Flows<\/a> and App<\/a> are addressed here and no need to modify the JSON before deployment, everything is configurable in solutions.<\/p>\n\n\n\n

Kindly check our previous post on how to work in a solution<\/a> before proceeding further because we will be referring to some examples from that post.<\/p>\n\n\n\n

Once all the development activities are completed a solution check has to be run to see what are issues in the components. No need to wait till the development completion, periodically it should be run and there should be no issues.<\/p>\n\n\n\n

In this case, 7 issues were found, all the issues should be fixed before exporting.<\/p>\n\n\n\n