Best Of

Please don't use JS. You need to put the full function and field name in the model sort property, instead of the alias.

So if you are aggregating the SUM of Annual Revenue - your sort order statement on the model would be : "SUM(AnnualRevenue) Desc Nulls Last"

If you are grouping by Created Date (Calendar Year) - your sort order statement would be: "CALENDAR_YEAR(CreatedDate) DESC"

If you are grouping by a field - with no function - just use the salesforce field API name (rather than the aggregation alias).

Skuid does have actions that do client side sorting. You can set those up to run on page load or on requery - but ideally you can get the sorting you need server side.

Bill,

In the DSS, go to Components > Form > Label > Required. There you will find all the properties to style your required text... even creating a "badge" by giving it a little padding, a background color, and a rounded border radius.

That is bizarre. Here are a few workaround ideas.

1. Put the first 2 into {{{triple braces}}} - which will just merge the data and won't run the renderer code. (You might need to change to {{Tenant.Name}} but whatever.
2. Move your combining to a formula field in a model - using a "Combine Text" function - and then just merge that formula field.

Reminder for posterity.

When you upgrade Skuid - its best practice to go to your Design Systems page and see if there is an. "Update All" action available next to the create button. That means that the new version of Skuid has some changes to Design System structure that need to be applied to your custom design systems.

We are working to make this an automatic post install process - but that is taking longer than we'd like.

I've run into this problem intermittently in Lightning implementations. I'm not exactly sure what is happening, but it seems to be tied to IndexedDB entries that salesforce is populating. If you open the developer tools in Chrome and look in the "Application" tab, and expand the "IndexedDB" node - you will probably find lots and lots of entries. I'm not sure why the are proliferating, but Skuid is not creating these. The org I was working in had several hundred replicated entries.

(the "skuid-demo..." in that picure is just the URL of the org I'm testing in. )

You can clear the IndexedDB entries by clicking on "Clear Storage" and making sure IndexedDb is selected. That should get your Skuid page to run again.

Please let us know if this continues to happen.

Thank you for your patience! Skuid has addressed the indexedDB issue as of versions 12.4.14 and above. Install links for the latest versions of Skuid are available on the Skuid Releases page.

Best practices for upgrading can be found in Upgrading Skuid on Salesforce.  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 after you upgrade. Please let us know if you continue to encounter any problems with this issue after upgrading.

Thanks again for bringing this issue to our attention.

Hi Eva,

To be clear, required fields will only be evaluated upon saving the model. If you have a step that does not have an action to save the specific model, the required field will not be evaluated. It is strange the validation works upon save in the first step, but not the subsequent ones.

Have you checked for any unintended model actions or other rogue actions that might be applying/updating a value on this field?

Are you by chance saving the model as soon as the page loads? This is a rare use case but if so, the save may be taking place before the component is loaded, which triggers the validation. Skuid will only evaluate fields that have unsaved changes so if you are saving the model on page load (before the component loads), you can try adding an action to update the field to blank right after saving. This would cause the field to be in an "unsaved" state and would trigger the validation.

If you have a simple page showing this problem, you might share the XML here to get extra eyes on it.

Arne-Per,

Just checking, have you tried all of the obvious things mentioned in the error message (making sure the static resource name only has letters and numbers, begins with a letter, and that you don't have any other page packs under the same name)? If you want to verify that the name you're trying to use if unique, you can open the Salesforce Developer Console, go to Query Editor, and run the following query:

SELECT Name FROM StaticResource WHERE Name = 'PagePackName'

where "PagePackName" is the name of the page page that you are trying to specify. If you don't get any results in the query, then your page pack name is unique.

Also, it sounds like you're trying to create a new page pack, not package into an existing page pack?

Thanks!

Emily

V2 Page Includes are more completely isolated from their parents. So the action you trigger in the page include is not going to affect the modal spawned by the parent page. The tool we use to get around that is events. Events can be set to be global - published and listened from all the skuid pages that are currently active in the browser window.

• Your action in the page include should be to publish an event. Just call it "CloseModal"
• Then in your parent page create an action sequence that is triggered by the "CloseModal" event that actually does the modal closing..

Its a bit of a complication, but there are plenty of benefits of the more complete isolation we have introduced for V2. We feel the tradeoff was fair.