Challenges with Installing/Upgrading Skuid on Salesforce Spring 17 Orgs

Discussion General
9

Hi Community~

There were changes in the back end architecture of the Salesforce Spring '17 release that prohibited installing certain versions of Skuid. Unfortunately​,​ the patch that Salesforce released to address the root cause of this issue ​did not successful​ly address the issue​.
 
What does that mean for installing Skuid since all orgs are now on Spring ‘17? 
The workaround that Salesforce provided can only be applied to one Skuid version at a time​ and it cannot be applied to all released versions of Skuid​. To minimize confusion, all versions and their accompanying release notes will be viewable from the Skuid releases page, but only versions to which the workaround has been applied will have install links.

  • Running Rockaway? We know that many of you are still using Rockaway so we have applied the workaround to the latest version of Rockaway: Rockaway ​Iteration 14. 
  • Running Brooklyn? You can upgrade to ​any version of ​Brooklyn ​beginning with Iteration 3. 
​Need to update a sandbox? Sandbox refreshes do not appear to be affected by the issue. Sandboxes created/refreshed will inherit the version of Skuid installed in your Production org. ​​Use​ the instructions in​ this tutorial ​​to ​migrate your Skuid pages from your development sandbox into ​any new​ly created/refreshed​ sandbox.  We will keep you informed of any other changes or additions to this topic.

Finally, as always, Skuid recommends installing new versions in a non-business critical sandbox environment to test all mission critical functionality before installing into a production environment.

Thank you for your understanding and patience!
Karen