Skuid NLX, SFX, & EXP

Thought this solution might be helpful for folks. It builds on a few previous posts and I’ll cross-link when I track them down again. One my rules of thumb with scripting is to use parameters rather than embedding specific rules or references in code. This example connects the Unique Id of the Field Editor and a CSS class of a button to link the two together (field editors don’t have additional button options declaratively). Mechanically, the button click passes the button component into the snippet as a parameter, the first class is extracted and then the skuid.component.getById() is used to grab the field editor based on that class on the button. The button will toggle the Field Editor mode between edit and read. If you combine this with some logic on save and cancel buttons in the button set, you get to a pretty nice sequence of button behaviors. The way to set this up is to add a Field Editor component and a Button Set to the page. Add the unique ID from the field editor (f

It’d be neat if there was a rendering option on components which was simply “Do not render”. This would predominantly be for testing or if you wanted to hide a component temporarily but not throw away all of your good work.I currently just add a rendering option of Page/URL Parameter asdfasdfg = fashjdgfkjahg to hide the component, which isn’t terribly elegant…Anyway, if I’m missing a simpler way of doing this please let me know.Cheers!Louis

Current set of options. Should include

Trello anyone?

I would like to do one of those cool switches for a Booleen field instead of a check box. On would be true and off would be false (Obviously). Thanks for all the hard work Skuids!

We are excited to announce that the Millau release (pronounced ME-yew, after the cable stayed bridge over the River Tan in Southern France) and the release notes are now available!!! We are also proud to acknowledge our latest community champion:John DahlbergJohn not only asks great questions that others will also benefit greatly from having answers to, but also follows up regularly on posts he is chiming in on. John generously shares his insights and knowledge with the community in order to help others resolve the issues they are facing. We are blessed to have you as an active part of our Skuid community. 

I would be sweet to have the option when we get this error… …to just click a “Remove” button and have skuid automatically remove those fields from the model. Instead of finding the model and scrolling through the fields to manually remove them.

So this one is just for fun.

The Millau release and its associated release notes, originally scheduled to be released today, will be available on Thursday, November 2nd. 

I am pulling in data from a Dynamo DB database and just noticed the when setting a condition on a field that is a string I only have an option to select "Single value’ equals … something.Is there any way to set a condition that “contains” a certain string as we can on skuid for sf?

As found at bottom of this page

As the user progresses through the wizard, it would be nice to conditionally display a completion icon for each tab. The progress component bar is nice, but if the users want to hop around or close out and come back later (they do), there is currently no way to indicate how much they have already completed. I’ve already built checkbox fields, which are updated as the user completes the info on each tab. Now I just need some nice way to display the status of those checkbox fields. Something like this…except icons would be rendered dynamically instead of statically

Is there a way that I can have a custom component that would add a model to the page’s definition on the builder side?

It would be sweet if we had the option to make an aggregate ui-only model, which would just summarize the data in another model on the page. Instead of querying a data source, the data source would just be the contents of a model on the page and all the ‘counting’ would be done client-side.

Just like this board.

Really neat new drag and drop JS library. I’m not an ace developer, but if I figure out how to integrate this with skuid I’ll post it here. Hopefully if someone else beats me to it they’ll do the same.https://shopify.github.io/draggable/

Love Skuid and want to make it your full time job?Rosetree Solutions is hiring a full time consultant/developer position. We’re Skuid Alliance Certified consulting and developer partners and have worked with Skuid since 2014. We help new and existing Salesforce and Skuid customers get the most value out of the platform. We’re based out of Dallas, TX but are open to hiring from anywhere.Since Skuid is such an integral part of our company and direction, good working knowledge of Skuid is required for this position. This position involves communicating directly with customers to work through their process and determine the best way to solve those issues combining Skuid and Salesforce tools. Our work involves anything from standard components to custom javascript snippets, components, and beyond. If you’re interested, check out the job posting on Indeed. We’re currently holding interviews and Skuid experience is the number one quality that will put a candidate to the top of the list. Feel

Skuid, please implement this as declarative. (function(skuid){ var $ = skuid.$; $(document.body).one('pageload',function(){ var ADashUIOnly = skuid.$M('ADashUIOnly'), row = ADashUIOnly.getFirstRow(); window.addEventListener("resize", setWidth); function setWidth(){ ADashUIOnly.updateRow(row,'minWidth',$(window).width()); } }); })(skuid); See: “YouTube”

Thought this solution would help folks out regarding replacing the Row Action visual component. Row Actions are great for working with table data, but the row of Icons is one of the least favorite visual design elements in the framework. Also, I haven’t seen anything in the API documentation regarding row actions but here’s a solution we came up with that dynamically builds a drop-down picklist of the active options and then executed the declarative actions when the option is selected. The way this works is the snippet will traverse the DOM, grab the elements from the list of row actions, and build the picklist. This happens on hover and rebuilds each time the hover event occurs, so if there is rendering logic on the rowAction, it will update the picklist real-time. This approach also helps with problems of the field re-rendering with a mode change. When a picklist option is selected it will then parent up to the table row and perform a click on the correlated row-actions. Note t

As per my other master component settings post last week, I’d like to have the ability to maintain certain model options in a master model.Think about the times you’ve had to create multiple models for the same object over and over on one or more pages. Then a change on the object that needs to be updated across all pages would then need to be updated in each of the models.This happens to me all the time and it’s a real pain!Combine this with my master component settings post and you can create fully fleshed out popups for New Tasks, Events, Contacts, Custom Objects, etc.

I know how to do this via XML, but with Skuid being a declarative UX platform this really really should be provided by Buttons to a Wizard.As per the following posts:Navigation Master Page - Trying to convert a prior page into a child pageChanging the Master Page on a Skuid pageMake Child Page Regular Page

Similarly to Master pages, it would be great if I could control component settings on a master “Control” component. Every company/Salesforce org typically sticks to one look and feel in how they use Skuid. It’s very difficult to make a change to the standard UX choices made across all pages. Using a master “Control” component could be used to update all components associated to it.Awesome!Additionally, it would be great if there was an option to use a master for default settings as well.Awesome!

I’d like to be able to initiate an on-click, press or swipe action on a wrapper. Used to be able to do that in the mobile builder, but that feature didn’t make it into the wrapper on the integrated builder?

Salesforce now supports using browser based spell check on Rich Text fields, but it seems that the Skuid UI does not support this functionality for Rich Text fields. Is this a setting that can be changed? Our users are asking for the suggested spelling options that the browser spell checker offers for Salesforce Rich Text fields within the Skuid UI, but I can’t seem to find spell check as an option.