[SOLVED] Issue with moving Actions between environments using Solutions

By | April 7, 2017

Issue:

Recently, while moving an Action from Dev environment to the Production environment through solutions, we faced an issue of “Resource not found”.

Though the action seems to be imported successfully, it didn’t appear to work and was showing the mentioned error.

Cause:

Further investigating the issue, we came to know the reason behind it.

We had created the Action named “ApproveAgreement” in the solution whose Publisher was IKL with prefix “ikl” as shown below:

Siddhesh Blog 1

In that solution, we added the action as shown in the screenshot below;

Siddhesh Blog 2

Now we had to move this action to the UAT environment. So, we created a new solution “MoveSolution” whose Publisher was the “Default Publisher” with the Prefix as “new.”

Siddhesh Blog 3

When we imported the solution into the UAT Environment, the action was imported successfully. However, the unique name changed from “ikl_ApproveAgreement” to “new_ApproveAgreement” as shown in the screenshot below;

Siddhesh Blog 4

And this was the reason our working had stopped, and we were receiving “Resource not found” error.

Fix:

Make sure that the Publisher while exporting the solution has the same prefix as that was used at the time of creating and publishing the action.

QUICKLY DOWNLOAD OUR PRODUCTIVITY SOLUTIONS FROM MICROSOFT APPSOURCE IN A SINGLE CLICK

2 thoughts on “[SOLVED] Issue with moving Actions between environments using Solutions

  1. Anish Maurya

    The Publisher changes Automatically for Actions in new environment. How do you fix that?

    Reply
    1. Inogic Post author

      If your exported solution’s publisher and action’s publisher is different, then the publisher of Action changes while moving action from one environment to another. So, we always ensure while exporting action from a solution to keep the solution’s publisher same as Action publisher.

      Hope this helps.

      Thanks!

      Reply

Leave a Reply

Your email address will not be published. Required fields are marked *