Skuid NLX, SFX, & EXP

Anyone else find themselves using Search Properties way more than Filter & Search Behavior?Can we take a vote to switch the order so Search Properties is first (and shows by default)?

Following is made possible with the following: Styler Chrome Extension .SchemaBuilderUi .bPageTitle, .SchemaBuilderUi #schemaBuilderToolbar { display: none; } URL parameter: ?isdtp=nv WEEEE!!! I refer to myself and others when I’m having fun.

Would like to see the ability to select the fields to “exclude” when subscribing to model field events.  I have a scenario where when one field is updated, I don’t want to run a certain set of actions.  To support this, I need to “check” all the fields except the one I don’t want (or write javascript).  The challenge here is that each time a new field is added to the model, you have to remember to go check that field in order to gain the AF actions.  By offering a “All fields except those checked”, it minimizes the risk of unintended behavior and reduces code/config maintenance.I could see this working by having a toggle that indicates the checked fields are to be “included” or “excluded”.Thanks!

Currently, when using the action framework “Update a field on row(s)”, the value for date and datetime fields are restricted to built-in functions.Would like to see the ability to be able to specify merge syntax so that values from other models/rows can be used to update the field in the target model.  Merge syntax is supported with other data types (e.g. text) but not date and datetime.

When creating a UI-Only field of Display Type Date or DateTime, would be very useful to have stock support for functions like Today, Yesterday, Tomorrow, etc.Also, if you input an invalid value in the “Default Value”, instead of encountering an error/exception/warning, the page functions without issue and the field itself is not added to the model.  For example, if you input a Default Vaule of “Today”, a new row will not have a value for the field.  However, if you in put “1/1/1900” it will.  If an invalid value is input, likely worth at least outputting a warning to the console.

If the model needs to load more records, we’d like to be able to hide the “Last” link in the lower right page selection menu, since we find it misleading for our users. It’s just not intuitive to call the last loaded records the last records when they’re just the last LOADED records. Or otherwise have control over it to rename it.

Love the new header but one issue is that I quickly lose track of which environment I am in. Would be nice if the environment name would show up somewhere in the header bar. I had to disable it for now to make sure I am in the right environment when making edits. 

I might be thinking about this all backwards, but I just assumed I could make this work pretty easily. We have a multi-select picklist for “Skills.” We want to use this field to filter our Contacts that have a set of “Skills.” For example, we want to find a Contact with CSS, HTML, and MongoDB skills. If I select all of those in a multi-select table filter, it will show me devs that have ANY of those skills, but not all 3 combined. Am I missing something simple? 

It’s be pretty cool for objects to have this feature.Not having to update all associated models on screen to have them reflect the change on the great great grand child object!How many times do you have to review/trace where the change happens and update 1+ models because of this.

This is a very straighforward feature I just discovered. Someone suggested it to me a couple days ago and thought it might difficult to implement. Looked as though it would be based on this post.https://community.skuid.com/t/request-meeting I didn’t have to add the static resource to the page to make this work. Simply created a popup with a template with the following iframe. Works with contacts, leads, and person accounts (if enabled). <iframe src="/scheduling/createMeeting.apexp?id={{{Id}}}"; width="100%" height="750px"frameborder="0"/>

We now have a gem of an article on Component Properties authored by one Andrew Duensing.

Yeah, I am old and cranky. But I would love to be able to “expand” the action properties list instead of having to scroll. Currently, I have to go into the XML when I want to see the full list. Maybe provide a button to show a dialog ala drawer. Or provide an expandable property editor. See screenshots. Thanks!

It would be nice if an event could cover multiples of the “group by” field (or at least transcend the grouping entirely). For instance, this event could cover both columns:I think you could accomplish this by letting any event that doesn’t have a value in the grouping field cover all groups?

Any thoughts on providing client side validation rules via the Page Composer experience?  e.g. Start Date cannot be in the past, Irvin’s Salary cannot be less than 1Gillion, etc.

Say, for instance, I always want my week view to look like this:

It’s a real pain sometimes hunting for a model for those larger skuid pages with many many models to look for the model(s) desired in action framework. Most of the time it’s the model in which the action framework is associated w/ or the model(s) in context. Also in conditional rendering. Probable more places, but this would be a great start.

Expand to a ridiculous set of possibilities. Option to choose which corner to place the mini icon.

Would like to see the following enhancements to conditional rendering:1) Ability to write a conditional rendering rule based on the “mode” of the component (e.g. edit, read, readonly)2) Ability to write a conditional rendering rule based on the “editability” of the field (e.g. field.editable)This would go a long way towards being able to make components that support view/edit/new simultaneously.In the past, there was discussion of adding a “call snippet” feature to conditional rendering.  This would allow a conditional rendering rule to be written in anyway that one could imagine.  The snippet would return true/false and could even not allow promises (to avoid long waiting async calls).  Having this added would be my personal nirvana 🙂Thanks!

It would be great to add Child Records more than once to a model, so that you could have different Conditions on each instance. Similar to adding aggregations more than once, instead of checking a box, you click on the child record type and it adds it once to the model…

Please, please … please.Skuid Superbank and Banzai are certainly blazing a path.But, in doing so, it has felt as though documentation and samples come as an afterthought.It’s true that most of the new features are self explanatory, but I’d to be able to go to a new feature and click the “Help Button” to get to the related page in help.skuidify.com. It would be great to find documentation, sample code and a youtube video. Best yet, links to the related API calls used for this feature.Icing on the cake would be a new Skuid CRM package with samples to every feature possible! Everything possible!It just feels like the path could be so well lit to get new people to skuid directly to their solution so much faster.The one saving grace to this realm of thought is this Community. It’s the fastest moving community I’ve ever been part of.

So. Seems simple but I was surprised to not see Standard buttons on Action Framework. Why not? Especially if that button has a VF page override.It would simplify having to update any places that do reference a skuid page and/or vf page to create a new record.Otherwise left with managing non dynamic links to create new records via skuid “New Record” pages… Unless I’m missing something. Quite possible as I was up very late last night. :S

We have some fields that have been renamed in a managed package and will display as an error in skuid pages. It would be great if there was a way to pull up all pages that have an error.

Ok, this one is a little “out there” but I’ve encountered several situations where it would be very helpful so I thought I would cast the line and see what happens…I’ve had situations were I need to run a specific set of “Action Framework actions” that aren’t triggered by a UI event.  For example, on page load, I want to automatically open a popup in certain situations.  I can do this today with Javascript but it would be slick if I could put a component at the top of my page where I could define a set of actions to occur.  I could then conditionally render the component to only get displayed in the situations I need it to. When displayed, it just runs its action sequence. Enter the “Action Runner Component”…From the toolbox, you would drag the runner to a page.  In the component properties you could define actions just like you normally would.  When the component renders, it would just run the actions.