What’s New in Skuid?

Brooklyn Q2 Point Release

At Skuid, we’re always looking for better ways to help our customers create exceptional user experiences, efficiently and elegantly. This drives our product roadmap, and informs our desire to constantly update and iterate. Here’s what we’ve been up to lately.

More features! More capabilities! More exceptional user experiences!

Updates as of 10.0.17

As of Millau 11.1.3 and Brooklyn 10.0.17, we now report inaccessible fields as Page Problems to aid Page Builders in resolving inconsistencies between the App Composer and the runtime. Users with Skuid Admin or Skuid Page Builder permissions may now see page problems. This does not represent any change in behavior for standard Skuid users.

The second change relates to field level permissions. Skuid’s handling of relationship fields is now consistent with Salesforce standard layouts. If you experience field level behavior changes in Skuid after upgrading, please review your Object and Field level permission settings.

If you have further questions, please contact support@skuid.com.

Updates as of v10.0.16

LockerService: Skuid is Ready

As of the Salesforce Summer 2017 release, LockerService enforcement is based on API version—specifically version 40. This means that LockerService is not yet enforced in all orgs. Even so, Skuid is ready!


While Skuid’s Brooklyn Q2 Point Release is on API version 39, it is LockerService compliant.

Even if LockerService is not yet activated in all orgs, users are encouraged to take all steps necessary to prepare. See Salesforce LockerService developer documentation for more information.

New product features—in Skuid

  • You asked for it—and we heard you. Skuid Table components can be made responsive, shifting how they display data for maximum usability on desktop, tablet, or mobile phone.

  • More data, your way:

    • We’ve added the Box pre-configured data source type for Skuid Platform and Skuid on Salesforce.
    • Data source features: more fields and improved file uploads in Microsoft OneDrive, new entities and capabilities in Slack, and the ability to download files using your SharePoint data source.
    • Salesforce invocable actions are now available as Salesforce data source actions. Post to Chatter, send emails, activate flows, run quick actions, and more!
    • This just in: use related fields with the OData data source type to add details to reference fields.
    • Reference fields in OData and Microsoft Dynamics data sources can now be rendered as links to their appropriate record detail pages.
  • New multicurrency chart settings: Does your enterprise have users across the globe? Ensure that users see chart details in the appropriate currency.

  • The Numeric Range filter option lets you set number ranges in the same way you set date ranges. Use it to show all records between Amount A and Amount B (for example, “all opportunities between $1000 and $5000”).

  • The Toggle Component action type: Conditionally render components without the complexity! Use to show or hide designated components.

  • Want more diversity in your table icons? Skuid now supports 7 icon sets.

  • Models with long load times holding back your pages?: Enable the Allow Page Render Before Query Completes model property so your Skuid pages render even if the model is still being queried. If one of your data sources is slower than the others, then your users won’t be concerned that their pages are broken.


    Prior to Skuid v10.0.3, this property was labeled Load Model After Page.

Minor updates

  • Character counter field property: Tell users how much text they can enter using the for string and text area fields.

  • The UI-only formula function COMBINE_STRINGS is now deprecated in favor of the more flexible JOIN_TEXT.


    Pages currently using COMBINE_STRINGS will continue to function.

New product features—in Skuid Platform

  • Use the new AWS Polly pre-configured data source type.
  • Need to manage your subscriptions? It’s easy to do, right from Skuid’s configure tab.
    • Also new in the configure tab: set the default Skuid app for individual profiles.
  • Use Login History to monitor your Skuid site’s use—or debug SAML configurations.
  • The Go to Skuid Page action type reduces load times and makes app navigation easier than before. No more URL trickery!

Want more technical details about this release and other updates? See the Skuid Releases page.

Heads up!

Here are some changes that could affect the way your pages work when you update. Make sure your upgrade experience is smooth sailing.

Update Themes

We recommend all users update their themes after installing this update:

  1. Navigate to Configure > Themes.
  2. Click fa-refresh Update out of Date Themes.

UI-only Fields and Formulas

There have been two important changes to UI-only fields and their formulas:


These changes could cause issues within your Skuid pages. Heads up!

  • Equality operators are now always treated as strict—meaning they will always compare type and value. For more information, see the operators section.
  • In previous Skuid releases, UI-only formulas could technically parse and evaluate JavaScript. This behavior was never supported and has been officially disabled as of the Brooklyn Q2 Point Release.

Microsoft Dynamics and Metadata Caching

Using the Skuid pre-configured Microsoft Dynamics data source type? Once you install the Q2 Point Release, your existing Dynamics pages will not work until you do a metadata refresh for the Dynamics data source.

The length Merge Variable

The length merge variable is now a number value and not a string. Double check your merge syntax!


This may impact your Skuid pages if you have used this merge variable in UI-only field formulas.

undefined vs null


An internal JavaScript API leveraged by multiple Skuid JavaScript APIs (most notably skuid.model.Model.getFieldValue()) will now return undefined for appropriate properties instead of always returning null.

Previously, null was returned more liberally for several APIs—even being returned for properties that were not set. By standard conventions, undefined should have been returned for these unset properties. This behavior has been corrected.

If your code explicitly checks for the null value on undefined properties, you’ll need to update it accordingly. Two options to do so include:

  • A “Falsy” Check

    Both null and undefined are considered falsy values:

    myField = myModel.getFieldValue(row, 'FieldId', true);
    if (!myField) console.log('Field has no value');

    By updating your code to use the ! (not) operator, you’ll be checking for either null or undefined.

  • Explicit Check for “null” or “undefined​”

    You may also add an explicit check for undefined values alongside your check for null values.

    myField = myModel.getFieldValue(row, 'FieldId', true);
    if (myField === null || myField === undefined) console.log('Field has no value');

jQuery 3

Skuid has upgraded to jQuery 3. If you’ve written code that references jQuery, be sure to read the jQuery Upgrade Guide to verify your code will not break.

Of note: .context and .selector have been removed from jQuery 3.0. (Both properties have been deprecated since version 1.9.)


What does this mean to Skuid users? If, in the past, you wrote code that uses the removed jQuery APIs, that code may break, potentially impacting associated Skuid pages.

If previously functioning pages are suddenly not working—or working incorrectly—check any custom code, snippets, or components for evidence of .context, .selector—or other removed properties—and rewrite the code.