Challenges with Installing/Upgrading Skuid on Salesforce Spring 17 Orgs

  • 2
  • Announcement
  • Updated 2 years ago
  • (Edited)
Please be advised of an issue regarding challenges with installing or upgrading any version of Skuid running on top of the Salesforce Spring 17 release. At this point, only Sandboxes and Preview Orgs are running Spring 17.

What does this mean for my organization?
  • If your org is NOT on Spring 17, you are not affected and can install or upgrade your Skuid version without any problems. 
  • If your org IS on Spring 17: 
  1. Already have Skuid installed? You are good to go and can keep working with your Skuid pages without issue. You will receive an error message only if you try to upgrade your Skuid version. 
  2. Do not have Skuid installed? Unfortunately, you will receive an error message and you will not be able to install Skuid for the time being. 
A critical case has been opened with Salesforce regarding this issue and they expect to have it resolved soon. We will update the community once the root cause is identified and fixed and when Skuid can be installed or upgraded in Spring 17 orgs. 

Where do I find what version I am running? 
  1. Check https://status.salesforce.com/status and click on your instance to see which version of Salesforce your instance is running.
  2. Log in to your org and look at the logo in the upper left hand corner.
  • If you see a  snowman, you are still on Winter 17. 
  • If you see a  rainbow, you are on Spring 17. 
Photo of Karen Waldschmitt

Karen Waldschmitt, Official Rep

  • 8,220 Points 5k badge 2x thumb

Posted 2 years ago

  • 2
Photo of Karen Waldschmitt

Karen Waldschmitt, Official Rep

  • 8,220 Points 5k badge 2x thumb
Official Response
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
(Edited)