Page include not working with Brooklyn upgrade

The page doesn’t load since updating when using id={{$}} as a query string.

Any ideas of how to correct this?

Looks like a bug, but try using triple brackets: {{{$}}}

No, that doesn’t work.  Do you know if there will be a fix for this shortly?

Hi Team,

I am facing this issue after upgrading my skuid package to Iteration 3.


I am facing the same issue even using 9.3.3

Our sandboxes were upgraded this morning without us doing anything and we are now experiencing the same issue on 9.3.3

I am having this problem as well. I did not update to 9.3 but somehow last night all of my sandbox environments automatically updated from 8.15.8 to 9.3 and now all my page includes are broken.  I tried to revert back to 8.15.8 but was getting the failed install message as my sandboxes are already updated to Spring '17.


Is there any update on when can this be fixed please?

Hi Skuid Community~

This may have been fixed in Brooklyn Iteration 4 by [SKUID-2866] which is now available from the Skuid Releases page. Can you try upgrading and see if it fixes the issue or not? As a reminder, Salesforce does NOT allow reverting back to prior versions of managed packages. Skuid always recommends installing new versions in a non-business critical sandbox environment to test all mission critical functionality before installing into a production environment. We also recommend that you update out of date themes when you upgrade.

Please let us know if upgrading does not fix the problem and we will investigate further … 


Hi Karen,
I don’t think the issue is still addressed. I have upgraded to 9.3.4 and the issue still exists for me.  Need quick resolution to this.

Best Regards,
Amit !

Can you give a method for us to be able to recreate the problem?

Hey Stephen, sorry the formatting is going to be destroyed but I have pasted the snippet below. This runs without issue after the page has loaded.

var $ = skuid.$;
$(function() {
var opportunity = skuid.model.getModel(‘Opportunity’).getFirstRow(),
isClosed = opportunity.IsClosed;

var renderFieldEditor = function() {
var pageTitle = $('#pageTitle');
    var editor ='object').editor;

var fieldEditor = $('.nx-basicfieldeditor').data('object');
if(isClosed === true) {
        displayMessage(editor, 'This opportunity has been closed', '');

var renderAsReadOnly = function(fieldEditor) {
    fieldEditor.mode = 'readonly'; 

var displayMessage = function(editor, message, severity) {
              message: message
              ,severity: severity.toUpperCase()
    $(".nx-messages *").off("click");
    $(".nx-messages *").css("cursor", "default");



Replace this line:

$(function() {

with this:

$(".nx-page").one(“pageload”, function() {

Hey Zach, that worked for the above example.  One other snippet we use in many places which also breaks on quite a few pages - : 

skuid.snippet.registerSnippet(‘showVIPAlerts’,function(field,value) {  var $ = skuid.$;

  var noteModel = skuid.model.getModel(‘Notes’);

  var renderFieldEditor = function() {
    var pageTitle = $(’#notesTitle’);
    var editor =‘object’).editor;

    if( > 0) {
      for(var i = 0; i <; i++) {
        var row =[i],
        parentType = ‘’,
        createdDateFormatted = skuid.time.makeFormattedDate(row.CreatedDate);
        switch(row.Parent.Type) {
          case ‘CustomObject__c’:
          parentType = ‘Custom Object’;
          case ‘OtherCustomObject__c’:
          parentType = ‘Other Custom Object’;
          parentType = row.Parent.Type;
        parentTypeInfo = ’ (’ + parentType + ': ’ + row.Parent.Name + ‘)’;
        displayMessage(editor, createdDateFormatted + ’ ’ + row.Body + parentTypeInfo + ’ - ’ + row.CreatedBy.Name, ‘warning’);

  function displayMessage(editor, message, severity) {
      message: message,
      severity: severity.toUpperCase()

    $(".nx-warning").css(“cursor”, “default”);


Any further update on this?


Are you still on 9.3.3? Have you tried updating to 9.3.4? 

Sorry this is still an issue for you!

Hi Amy,

Yes, we have updated two of our sandboxes to 9.3.4 and are still having this issue.  I will continue to look at options on our end since we cannot upgrade our production instance until we have a workaround.