Share
ReportHi All,
While I was updating plugin assemblies in our develop sandbox environment, I mistakenly unregistered a long existing plugin assembly. I new registering it again would cause the GUIDs to change, so I decided to restore the environment to an earlier backup just before the mistake. Unfortunately, the tenant is at capacity, so I couldn't restore the environment. I could request an extension from Microsoft, but we've been over capacity for a while now, and have requested multiple extensions in the past, so that would likely not happen. Anyway, this was yesterday and new development has already been done, so a restore is pretty much out of the question now.
We import managed solutions to our UAT and Production environments, so I can't export the assembly from there, but I did have an older sandbox environment I could export the assembly from, but unfortunately, two new plugins have been added since then, so I'd still have to register two new steps, which takes me back to the GUID issue.
Is there any way to avoid having duplicate plugin steps when I import the patch solution to our higher environments? Can I somehow manually set the GUIDs of the new plugin steps to match the old ones? I know I can unregister the old steps, but there will be a short window of time during the import where I'll have duplicate steps on a very business system, which could lead to issues.
I have the same question (0)
All responses (
Answers (
141
