Skuid NLX

The ability to conditionally rendering a component or component element would be so much cooler if there effects available when rendering such components. As an example you could use jquery slideToggle() to have a large wrapper with multiple components slide/push elements down the page from within a tab.

I envision a component you can drag in that has settings allowing you to choose fields upon which you can identify duplicate records. The user would see a blank form with these fields. They would enter data I any/all of the fields and click “find duplicates”. The result would bring up a table displaying a predefined set of fields showing potential duplicates. The user could then just check the boxes next to the records they want to merge and choose one as the master record for overwriting situations. It would then automatically update every field in the records across the entire object(s) involved without having to choose which records to bring into the model. It would have to extend to migrating all child and related records too. This is, I suppose, something that could be built from scratch each time, but if there are a lot of relationships and or a lot of fields, it could be extremely time consuming. Seems like the Skuid-zards (Skuid Wizards) could cook something up to make this pro

Hi friends! If you haven’t heard, Carl and I are picking up the Nautilus Notes again. We’ll meet tomorrow - Tuesday, April 14th - at 2:03 EST to talk about Spark Update 3 and much more. Here’s a quick preview: New Skuid admin app experienceNew page composer features, like undo/redo buttons and an index of elements in your pageImprovements to the Design System StudioNew V2 component enhancements, like setting fixed columns on tables, accordion section states, and label-left for forms Already-released-but-maybe-you-didn’t-know features, like adding HTML to a page using the Text Component and keyboard navigation in table cellsNew Early Access program for Skuid’s update and major releasesWe’ll also talk to one of our customer users, Erik Wahlberg, about the new release and some ways his team is dealing with this new normal of working remote (and other challenges). You can register here: https://go.skuid.com/nautilus-notes-april-2020Hope to see you there! 

Common use case is within a deck to set card styling.

We like to use guage charts in some of the other parts of our organization to display current values of a metric. Skuid/Highcharts doesn’t have a specific guage chart (as far as I’m aware), but I just discovered that we can turn a donut chart into a guage by setting the start and end angles of the chart! 🙂A before render snippet like this does the trick:var args = arguments[0];$.extend(args.plotOptions.pie,{startAngle:-90, endAngle:90});

It would be nifty if there was a function to test Skuid page’s ability by systematically loading the page in groups of models set to query on page load.My use case is often single-page apps that have many models that need to be on the page. Other models/components are put to page includes whenever possible.So the test would first gather up all the models that are enabled on page load. Then it would systematically test the page to isolate the model that is the culprit. The page could actually have more then one model that is causing the issue, but running the test would discover this.

I was struggling to find a way to conditionally render a button on a table row to take an action with context based on the field value of that specific table row or child object from a table row, and pass that context to the action taken. It would appear that SKUID allows you (in the Editor UI) to have conditional rendering on elements in table rows based on “Row Property” but not row field value which is an unfortunate limitation. Additionally, if dealing with child objects for that row item, it looks like there’s not much directly in the UI to do if you want to have a conditional button that passes context on those. I found a solution and wanted to share it here in case anyone is having this trouble as well. To make this work I used a template field and inside the template field draw from a formula on the row (or child object) to conditionally render an edit button using an HTML link invoking inline javascript like this: {{ConditionallyRenderMe__c}} (edit){{/ConditionallyRenderMe__c}

A fair number of posts here refer to Sample Pages that we posted in Github or Bitbucket.  We have moved these to a new repo.  So if you get 404 errors on the links in an old community post.  Most likely you will find that page here: https://github.com/skuid/SamplePagesSearch for the page name in that repo and most likely it will still be there.  Some of the more code-heavy pages are being moved to Skuid Labs - our repo of interesting experiments and extensions.   Check that out at  https://github.com/skuid/skuid-labsAlso you should check out the examples of fully built Skuid applications that are found at our Design System site:  https://portal.skuidsite.com/designsystem 

As per subject. The use case I currently have is that I have a deck component with a button set component next to it. I would like to be able to toggle a condition using just these icon only buttons. I could make use of UI only model and field, but would prefer the option to render based on a model conditions state.

Simply to deactive if active or activate if inactive a condition. I could use this in a button.

Hello Skuid Community!Please be sure to review this important information about Salesforce’s Spring '20 release, which contains updates that will affect your Skuid experience.

Happy New Year Skuid Community,We want to alert you to two changes with your Salesforce environment that affect your Skuid experience and provide recommendations we have to address these impacts.Change #1: Lightning Component ChangeSalesforce has made a change to the way Lightning Components are validated as explained in this knowledge article. This change prevents a successful upgrade of Skuid when trying to upgrade from older versions of Skuid for Salesforce (older than 11.1) to the current supported versions (Millau 11.2.X and Spark 12.2.X) as noted in this community post. When is this change happening? Salesforce is requiring compliance with these changes in Salesforce’s Spring ‘20 release which hits sandboxes the weekend of January 3, 2020. (allow time for proper testing) What do I need to do? If your company’s production instance is running an older, unsupported version of Skuid for Salesforce (older than 11.1), you need to take action by upgrading your Skuid version to the curre

Same as “Show Message and Block UI” but this would the user to continue with page elements that are not blocked.

I ran into an issue where I was running through heavy javascript processing (big for loops) and the browser tab was freezing while it was iterating over the loops. In order to fix this I utilized some code that ran the loops in asynchronous chunks broken up by a maximum time per chunk, allowing the page to have intermittent updates while the loop was running. I wanted to share this template code here so anyone that is having this issue can benefit from it. Keep in mind this code is ran asynchronously, so you’ll need to rely on the “endFn” function variable to execute code after the loop completes. //Iterate Array Asynchronously //If iterating over Model Rows, first get the rows into an array using model.getRows(), use that as the array variable //fn = the function to call while iterating over the array (for loop function call) //chunkEndFn (optional, use undefined if not using) = the function to call when the chunk ends, used to update a loading message //endFn (optional, use undefined

Nautilus Notes December starts at 2:03pm today! Here’s a brief preview of what we’ll be talking about: Skuid actions: event publishing, inputs, and toast messages Einstein analytics data & REST models Skuid and LWC Carl’s ridiculous tacky sweater Looking forward to seeing you there (registration link: https://go.skuid.com/nautilus-notes-webinar-december). Come prepared with your best Christmas Carol puns. Cheers! Matt

Hi all, You may have already seen this, but in case you didn’t - no Nautilus Notes today, as we are going to do a Dreamforce “cooldown run” Nautilus Notes on Friday, November 22. Register here: https://go.skuid.com/nautilus-notes-webinar-novemberHope you can join us!Thanks,Matt

Would be nice. 🙂

Can you block the page while saving the page? It’s annoying having to scroll up to the top when saving page to know for sure it’s saved or in the process of saving after using Ctrl+S hotkey.

This is Scotty’s idea.

For those of you looking for a solution for box.com’s Salesforce integration, I used this post as a template to create the following code. Replace “Contact” with the name of your object. Add a template component to your Skuid page and paste the code in. Worked like a charm. https://community.skuid.com/t/how-to-view-a-visualforce-page-on-a-skuid-detail-page

It would be awesome if the picklist options for a field could be displayed in this big plank space (when you click on the field in the model), just to make it easier to reference: This is especially handy when setting render conditions based on a value in a picklist. (Interaction_Purpose__c = ‘Initial Pregnancy Appointment’, for instance). I often find myself returning to the object in SFDC to figure out exactly how a picklist option is spelled. And if I could see that info in Skuid, it would speed up page development. It would be even awesomer if the list of picklist options came with checkboxes, so we could select the values that we want included in the picklists (default to all selected).

Skuid has a great selection of icons for row actions, but if I could display row actions as text, then I could make a page even clearer to the user. This would be especially useful in communities, where often the user does not receive any kind of formal training for using the pages and processes. 

I would be great if there was some kind of option to choose ‘standard’ or ‘merge syntax’ for various fields where merge syntax can be used in the page editor. In my case, tab labels. I find it hard (and ugly) to deal with long strings of merge syntax in a small text field.It would be great to be able to change a setting to show the tab label field as a larger text box with more room to edit. Perhaps the merge syntax could be collapsed as well so that we wouldn’t end up with tabsets looking like this in the editor:

Below is the webinar that we conducted yesterday introducing the high level features of the Superbank release.  We will be scheduling further deep dives to provide deeper details about specific features. Enjoy!