Skuid NLX, SFX, & EXP

Along with the new Spark release, we are proud to acknowledge our latest community champion:Mike Dwyer Mike has been exceptional in his willingness to assist our members overcome problems via the community. Skuid would like to thank you for helping to break down obstacles so others can see  the amazing things you can build with Skuid. By bringing known issues to our attention and sharing workarounds with other members, you have helped the Skuid community to grow as a valuable source for solutions.We can’t thank you enough, Mike!!!

It would be great if actions could be deactivated and grayed out for testing purposes.

Hey! It’d be great if merged counters in tabs would update on model save/query. I know this is a long-standing issue but I think it’d be sooooooo cooooool to get this sorted. I know we can do this by re-rendering the component with a javascript snippet but this often causes issues particularly when tab components are nested, etc. I’m guessing that if we were able to assign tabs to a particular model then this problem would be fixed? I know it’s easier said than done but could there be other benefits to assigning a particular tab to a model? Or multiple models? I’m not sure the best approach but this would be such an ace feature. Cheers! Louis

This one would likely take a lot of overhaul the page composer…but I think it could be very helpful in accelerating the learning curve for new admins/builders. In my experience Skuid admins tend to struggle the most with the concept of a model when they first start learning to build with Skuid. On the other hand, the concept of the Component is very intuitive. So re-designing the page composer to be oriented around the Component would be valuable for new admins/builders.For example…When a user places a Component on a page, the first tab within the Component’s properties section could be named “Data” and it would allow the user to setup the Model properties (naming it “Data” to fully abstract away the concept of Models).If Skuid auto-named each model as Pat suggested here, that Model’s data could still be referenced in other actions, conditions, etc. but it would be named something like “Field from another Component’s Data”…instead of “Field from another model”.Regarding Model Fields, I

This is probably a pretty “far left-field” request…so I get that it’s nothing that would be implemented quickly…but I’ll still throw it out there. I’m building longer and longer action sequences these days, often times executed on a button within a drawer or popup…and my screen gets very cluttered with the popup/drawer window, then having to expand the action sequence builder/editor…see attached image as an example. It would be nice to have that action sequence builder/editor reveal from a sliding panel on the left or right side of the screen…so I could endlessly scroll through my action sequence while still keeping the rest of the composer nicely in view.

As per subject. This would be especially useful the picklist has many many options.

We have a page that uses a table control. The table has six columns. The columns can be logically organized into two groups of three. We would like to display a second-level header above the normal column headers that spans the three columns that make up each group. Can this be done within the table control? If not, is there a good way to fake it?

This one’s troubled me for years! When you set a default date (e.g. on new row action) you can’t just enter some merge text to reference a date from another model - you can only select a specific date or a relative date. It’d be so lovely if I could just write ‘{{$Model.MODELNAME.data.0.SOMEDATEFIELD}}’ whereas instead I have to overwrite it in the XML. Cheers! Louis

What I’d like is an easier way to create child record defaults (more complicated ones, requiring a formula) when creating that record from a parent - which is a frequent process. When creating a quick-action in Salesforce to create a new record from a parent you can set predefined field values via a formula. It’d be really swell if you could do the same in Skuid as the way I’m currently doing this in Skuid is to create some ui-only formula fields on the parent model and to then reference these via ‘{{$Model.MODELNAME.data.0.FIELDNAME}}’ in the new row action. This is a lot more work/overhead than the Salesforce quick action process. Screenshot sums it up best! Let me know if I’m missing something! Cheers! Louis(p.s. some validation in the formula editor would also be SWEET - including making sure referenced fields are in the models)

Finally got a chance to finish watching the sneak peak to the Skuid Spark release. Mind blown!!! Well done Skuid Product Team! Super excited to dive in!

I’d try to explain my use case but honestly it’s nutso. Suffice to say that I have a dashboard page that has hundred’s of charts and tables using one 1 aggregate model. The charts and tables make use of XML based conditions and javascript to customize each. Basically I group by everything possible and use conditions in the charts to further filter and aggregate to the desired data set.

Hello,I’ve got a wizard in which the navigation button calls a couple action sequences back to back.However, I’ve discovered that if I have a validation rule fire or a required field throw an error on the save that is in the first action sequence, the second action sequence is still invoked - and even the navigation at the end of the flow.  So the error flashes, but it bypasses the save, and proceeds with now incorrect data.Any idea how to get around this?  I’ve played with different approaches but they all move forward in the flow.  Btw, I’ve seen posts on this regarding js, but this is pure skuid wizard/action sequence config.Any thoughts?Thanks,Paul

No parameters are passed to a snippet used for conditional rendering a field. er … uh …

We are implementing salesforce matching rules and duplicate rules. We found skuid is not handling alert properly. comparing with salesforce native ui, there is list if matched duplicated records and option to ignore (as matching rule config). But in skuid error message doesn’t handle ignore and save, and there is no indication of matched records. Screenshots attached

It would be convenient for our users if there was a ‘today’ button or link in the navigation section of the calendar component (in all three views) when the current date was not visible.

As per subject! Anywhere a user can call a snippet action there should be parameters available.

Enjoy!(function(skuid) { /* ========== Custom field type-specific renderers here ========== / var $ = skuid.$; function defaults(field){ $(field.element).dblclick(function(e) { e.stopImmediatePropagation(); return false; }); $(‘a’,field.element).attr(“target”, “_blank”); } function customBoolRenderer(ogRenderer, mode, field, value) { // To call original renderer ogRenderer.apply(this, Array.prototype.slice.call(arguments, 2)); defaults(field); } function customComboRenderer(ogRenderer, mode, field, value) { // To call original renderer ogRenderer.apply(this, Array.prototype.slice.call(arguments, 2)); defaults(field); } function customCurRenderer(ogRenderer, mode, field, value) { // To call original renderer ogRenderer.apply(this, Array.prototype.slice.call(arguments, 2)); defaults(field); } function customDateRenderer(ogRenderer, mode, field, value) { // To call original renderer ogRenderer.apply(this, Array.prototype.slice.call(arguments, 2)); defaults(field); } function customDTimeRe

Because of this: https://community.skuid.com/t/model-condition-rich-text-field-null-not-working Skuid should not allow us to select textarea fields for conditions on salesforce data sources.

Building on this idea - where you have two buttons, and each one stores a specific table layout and lets users switch back and forth: https://community.skuid.com/t/snippet-to-show-hide-set-of-column-in-tableLet users arrange a table however they want (reorder and show/hide columns), then save that layout, give it a name, and be able to call it up later. Should also include whatever filters (conditions) were present at the time and any values there. Ideally also check if any Sorting was applied and save that. Our use case is users have a list of patients, the table has a possible 50 columns with all kinds of data. Users sometimes want to see just two columns, other times a different set of 5 columns, sometimes they’ve applied a filter as well. And with 100 different users, there isn’t necessarily enough overlap to say, build a tab with a dedicated table for a particular use case. We’re looking at utilizing a custom object (maybe Saved View) to store personalization settings, then let us

I have made few fields required on skuid page and when User fill the form and left any of the field blank. e.g First Name, Last Name, State, Address Mobile Number etc. An error message will be shown on top of the field like This field is required. In addition to this, an another message like Required fields has no value will also be shown at the bottom. I just want to hide this error message at bottom. Please suggest.?

Not sure if this can be done and i don’t know it but i would like to allow users to hide or show fields in a field editor like we do columns of a table.  Is this possible or on the list of things to do?

It would be very helpful if when you create a filter with Pick Options and Condition(s) created automatically, that there was the ability to add ‘Blank’ to the auto created filter options.One example of a use case would be if an opportunity is in the ‘Finals’ stage, show all opportunities where ‘Date sent’ is blank. This would also be helpful to see all opps where multiple specified fields are blank.There is no good work around for this. (Unless someone can suggest one I haven’t though of!) They all have restrictive limitations. If your picklists have a large number of values then manually creating conditions for each filter becomes time restrictive. Creating toggle buttons based on an ‘is blank’ condition will get cluttered when used in addition to the normal filters, not to mention the normal filters and the toggle condition buttons can contradict each other. Sorting on a column header does not re-query a model so if there are too many records to display on page load then the result

I have a use case that needs this functionality.Is there a way to disable this via js?

Thought this might be helpful for folks. This is a snippet that you can use on tables to limit the values of a picklist field to the permitted ones for a selected Record type. Skuid tables don’t have record context, so the default behavior is to display all picklist values for a field in the filter. For more involved objects, this gets unwieldy. The code here is an extension of this article: https://docs.skuid.com/latest/en/skuid/filters/snippet-as-item-source.html and the setup of the page (and the logic) is pretty similar to how it’s described in the article. A model condition driving the table needs to work off the RecordTypeId and only works with a condition where the operator is “=” (No multiple values allowed in the condition). We use “Field from another model” for the condition and that one looks up the RecordType object which is either accepting a parameter fed into it or setting the DeveloperName to pull the recordType as well as an SObject condition. If the filter is