Skuid NLX, SFX, & EXP

It would be great if we could create hierarchy between filters. For example, I have a table called impact area, which is joined via lookup to a much larger table called impact topic. I would like to create both table filters, but associate them in such a way that if I select a value within impact area (say, Governance) the Impact Topic filter would only display to the user the values that look up to that Impact Area value (The Impact Topics under the Governance Impact Area). This would essentially make the values in a filter contingent on the selection from another filter, in cases where there is a logical hierarchy between them in the database

Often have a need to go to the associated model for the component I’m working. This can be a bit of a pain when there are dozens of models.

It would be great to see an ‘agenda’ view on the calendar, which shows events in order. It really wouldn’t be much different than a nicely formatted table, but it would be nice to easily switch between current calendar views and the agenda.

I know this is really simple CSS, but I just realized it for the first time, and wanted to share my joy. 🙂If you leave the panel width blank for a custom panel set, the panels will size themselves to their contents and display as inline-block.

I noticed there wasn’t a complete script available in the forums that allowed for this, so I wrote one. This can also be used to copy selected rows in any models table to another model. The source model in this example is LineItemsBundle, which is conditioned and queried using action items. (Activate Condition & Set Value, Query Model, Open Drawer). It didn’t work particularly well using Before Load actions, so manual actions were used instead. The destination model is QuoteLineList. Selected rows from within the draw will be added to the QuoteLineList model with variables set in the script and then saved. Hope this helps! var params = arguments[0],<br /> $ = skuid.$, models = skuid.model.map(); // grab ids of all selected rows var Ids = skuid.$.map(arguments[0].list.getSelectedItems(), function(item){ return item.row.Id; }); // model to add seleted rows from var bundleline

The idea is rather simple but very useful. Consider the detail page for any record. Often when creating a page for new records, a separate page is built even though all the same fields are desired in the page.It would be great if the mode could be conditionally set. Such as having a Field Editor be in edit mode if row is a new record and Read w/ inline-edit for existing record.

Can’t wait to see it!

Our users would like to upload images directly from the rich text editor instead of uploading them and then adding the URL. The non-skuid rich text editor enables this, but for some reason, it doesnt carry over into skuidified pages. Is there a workaround? Skuid editor Out of the box SFDC editor

I often see pages that have multiple models for the same object. It would be great for page load time to be able to have a condition on the component itself in order to make use of just one model.

We’re starting to work collaboratively on different Skuid pages, and it would be nice if we could have a chatter feed within the page builder, so we could discuss edits. Seems like it wouldn’t be too hard, considering that Skuid seems to be built with Skuid…

When you navigate to a date field in Salesforce 1 on a Skuid mobile page, this happens. You have to click Done to hide the keyboard to see the whole calendar. It should either a) auto hide the keyboard, or b) use the iOS date picker instead of the pop-up calendar. Any way to javascript a temporary solution here? You could also maybe use the same thing that Salesforce 1 uses, hide the entire screen to show a calendar, but it’s not ideal because it doesn’t tell which date field you chose, and you have to choose a date to get out of it.

Anyone interested in writing a Skuid review on G2 Crowd gets a $5 Amazon gift card.  We are new to G2 Crowd and have 0 reviews at the moment.  Disclaimer is you only get the gift card if it is your first written review for G2 Crowd.  Thanks!https://www.g2crowd.com/products/skuid/reviews

Short of having this come out as a feature, feel free to use this utility. Lemeno if you’re able to improve upon this.https://drive.google.com/file/d/0B6URHpTQ0n-kWVNiY21VanJ3NnM/view?usp=sharing

Since url parameter conditions have a ‘no value’ behavior, it would be handy to be able to launch a page with the builder’s preview button (or the preview row action on the Pages page) and not provide a parameter.

These are in the community already but thought that new users should have it easily searchable by title. // this is the code that makes a non-reference field not link skuid.snippet.registerSnippet('DontLink',function(args) {var field = arguments[0], value = skuid.utils.decodeHTML(arguments[1]); if (field.mode !== 'edit') { field.element.append(skuid.$('<div>').addClass('nx-fieldtext').text(value)); // this code can be modified to meet the needs of the other modes } else { skuid.ui.fieldRenderers[field.metadata.displaytype][field.mode](field,value); } }); // this is the code that makes a reference field not link skuid.snippet.registerSnippet('refDontLink',function(args) {var field = arguments[0], value = skuid.utils.decodeHTML(arguments[1]); if (field.mode !== 'edit') { field.element.append(skuid.$('<div>').addClass('nx-fieldtext').text(field.model.getFieldValue(field.row,skuid.utils.getFieldReference(field.id,field.metadata)))); // this code can be modified to meet the need

In a sharing mood today. 😃Similar to this blog but slightly updated code.http://www.mblazonry.com/creating-a-new-opportunity-in-salesforce-using-only-one-model-2/ // Listen for popup close of new record using just one model. // Snippet to be called after creating new row AND displaying popup // Only downside to this is that saving the model in the popup also saves any // other edits in the model. skuid.snippet.registerSnippet('listenForPopupClose',function(args) { var params = arguments[0], $ = skuid.$, row = params.context.row, model = params.context.model; skuid.$(".ui-dialog-content").dialog({ "beforeClose" : function() { var numOfChanges = Object.keys(model.changes).length; // if there is more than row that is currently changed (new, marked for deletion, edited) then this new row will be abandoned. if (numOfChanges > 1){ model.abandonRow(row); // otherwise just mark if for deletion and save } else if (numOfChanges == 1) { model.deleteRow(row); model.save(); } } }); });<

// used to be to refresh model from page that called a page include // before page include action skuid.snippet.registerSnippet('setSourceModelName',function(args) { var params = arguments[0], $ = skuid.$; sourceModelName = params.model.id; }); // used in conjunction with snippet 'setSourceModelName' skuid.snippet.registerSnippet('querySourceModel',function(args) { var params = arguments[0], $ = skuid.$; skuid.$M(window.sourceModelName).updateData(); });<br>

When using table filters with the toggle option, it would be helpful if there was an option for two field labels i.e. a label for when the toggle is on and another for when it is off. The Show All button is a toggle filter. Right now, it is Showing All, and I would prefer to set the label to be Hide All (or something like that) and have the button still look active.

Currently arguments[0].button is the jQuery wrapped DOM element for the button that initiated javascript through “Run a Skuid javascript snippet.”It would be great if .button was also included in the arguments any snippets run from the action framework for buttons that “Run multiple actions.”

I often find myself using a panel set and two field editors one the same model because I want a different layouts for different columns or sections of a field editor. For example, label beside field on the left column, label above field on the right column.I could accomplish this with a single field editor component if the layout property was moved down to the section level.

We often have a use case where we’d like to be able to use a wizard, except that users occasionally need to jump around between screens. So we use tabsets, and add a Pagetitle component at the top of each tab, with Next Tab and Previous Tab buttons that run a snippet called ‘nextTab’ and ‘previousTab’, respectively.Here’s the generic inline javascript to make it work: <br>// Tabs<br>(function (skuid){<br>//Shortcuts<br>var $ = skuid.$;<br>//Helper Functions<br>// Given the button that was clicked, find the parent tabset.<br>var getTabset = function (button) {<br>return $(button).closest('.ui-tabs-panel').parent();<br>}<br>// Given the active tabset, find the active tab.<br>var getCurrentTab = function (tabset) {<br>return $(tabset).tabs("option", "active");<br>}<br>//Build Snippets<br>var snippets = {<br>'nextTab': function () {<br>var clickedButton = arguments[0].button;<br>var