Hi Peter -
Here is some helpful insight (paraphrased) I received yesterday from Karen @skuid:
Regarding rollback:
The issue with Salesforce’s Spring '17 release created problems in installing any version of Skuid. They provided a workaround which has been implemented in Brooklyn Iteration 3 (9.3.3) so currently, customers are only able to install 9.3.3. Even if we could help them uninstall and reinstall (not recommended), we wouldn’t be able to get them back on 8.15.8. (from a package install)
Options:
1. They can create a new sandbox off their production org and it should automatically bring the production version of Skuid (Rockaway 10) down with it. They would be able to package up their Skuid pages in the sandbox they’ve been working in so they don’t lose their development there. They’d be able to unpack those pages in the desired sandbox. Here is a tutorial on how that can be done.
*note: If you have not yet installed skuid on production, you can still do so as long as your production instance is still on Winter '17 and has not been updated to Spring '17
2. A number of bugs from 9.3 have been resolved in 9.3.3 and more will be addressed in Iteration 4 (released 1/26/17, currently available on skuid.com/release website). (you may need to install 9.3.3 into an org before updating to 9.3.4 because of the Spring 17 issue, not positive on this one)
Also, Skuid has an auto-update opt-out list that you may want to put yourself on. Just send the request to their support email and provide the org ids for the environments you don’t want to auto-update.
Hope this helps!
