Complete our Nintex Community Survey
Access resources, discussions, and troubleshooting tips to build custom applications and streamline workflows with Skuid NLX, SFX, & EXP.
Recently active
Most Devs I know appreciate any shortcuts that allow them to keep hands on the keyboard. Its so much faster than jumping back and forth to the mouse. In Skuid a task that is often pretty repetitive and slow is building models. Scrolling up and down the field list can be a royal pain…Skuid to the rescue with a cool affordance!!! 1. Whenever the field list is exposed the cursor is focused on the search box. Start typing directly. 2. Search executes dynamically as you type. Type NAM and the field list will narrow to the Account Name field.3. Tab key will move your cursor focus down through the available fields. Shift-Tab will move focus back up. (Searching for ID results in lots of fields)4. Space bar will select the focused entry and move focus automatically back to the search box. Rinse and repeat. AND NEVER TOUCH THE MOUSE!!!
Did you know that you can format your section title templates with HTML? for example, if you do Open Tasks It’ll look like this, which is rather more pleasant than plain text: One day we hope to have the Skuid CSS better documented so its easier to know how to do stuff like this. For now, though, you can always use your browser’s Inspect Element feature to dive into different page elements’ styles.
Sometimes to help us debug your Skuid pages, we’ll need you to post the XML to the community. There are two ways to do this. 1. The first way is to wrap your XML in the following HTML tags <pre><code> </code></pre> Here is an example of me using the first method <skuidpage showsidebar="false" showheader="true" tabtooverride="Skuid Central"> <models> <model id="Events" limit="100" query="false" createrowifnonefound="false" orderby="LastModifiedDate DESC" sobject="Event"> <fields> <field id="StartDateTime"/> <field id="EndDateTime"/> <field id="Subject"/> <field id="WhoId"/> <field id="Who.Name"/> <field id="Type"/> </fields> <conditions/> </model> <model id="Contacts" limit="100" query="true" createrowifnonefound="false" orderby="LastModifiedDate DESC" sobject="Contact"> <fields> <field id="Name"/> </fields> <conditions> <condition type="fieldvalue" va
Add “Role” as a Page Assignment option (in addition to Profile and Org Default). The difficult thing here is: which takes precedence, Role or Profile? The standard “assignment” hierarchy goes like this — think Hierarchy Custom Settings): Org Default Profile User (not currently supported in Page Assignments, but Since Users have both a Profile and a Role, we would either have to do one of the following: Arbitrarily place Role either above or below Profile in this hierarchy (unless someone can give an argument as to whether above or below is NOT arbitrary) Add Role as another dimension to the Page Assignment processing. This would: Not require making an arbitrary prioritization of Role vs Profile. Would massively increase Page Assignment flexibility - but also introduce complexity - which we could eventually remedy with a more easy-to-use Page Assignment “matrix” editor or improved UI. With this in place, though, we could actually differentiate by Profile and Role - e.g. there would
Just checking . thanks.
Hi everyone,I need help with integrating the Click-To-Dial functionality from a managed package (CTI360) with a Skuid button. Has anyone successfully achieved this? Any guidance or examples would be greatly appreciated.Thank you in advance for your help.Best regards,Prashant
I am using NLX on version Edinburgh Update 6 (16.7.1.0) connected to a Microsoft SQL database. The field I am having issues with is built as a DATE (not datetime) field in the database and the schema in Skuid reflects that. When I create a record and set the date (using a TODAY function) it looks correct in the console where it is just todays date only (6/26/24). It also is correct in the DB when just doing a SQL query. The problem arises when I load that record back into NLX it displays in the console as 2024-06-26T00:00:00.000Z and then displays the date on the table as the day prior (6/25/24). This is affecting some logic as well as its just not the correct display. I have attached screenshots as well. Any help would be great, I don’t know why its loading it as a datetime when its Date only in both DB and Schema and I also don’t know why that’s getting displayed as the day before. (Screenshot Reference – 1)Form – original record creation 2) screenshot from db sql query showing raw d
I am trying to auto populate a date field with the value same date but 1 year from now. ‘Single Specified Value’ doesn’t have the option > n days from today or weeks or yearsSo opted for ‘Result of a Formula’ but can’t seem to find the proper formula format to do “Today() + 365 days” . Could someone please advise?Did try playing with this > DATE_ADD(today(), 52, week) but it’s not workingthank you
Welcome Skuid Community! The Community is here for you to discuss, collaborate, ask questions, and stay updated with everything Nintex! We have compiled links to all your Skuid resources in an informative one-pager. You can find it here.To find the location of your content once it is fully migrated, please refer to the table below. Skuid Community Nintex Community Questions Skuid Forums Discussions Skuid Forums Announcements What’s New? Skuid User Groups Group Overview Page Please rejoin any Groups you were previously a member of. Contact admin if you need assistance. Site Feedback For any site feedback, please contact your Community admin. Report a Defect Skuid Forums Ideas All historical ideas have been migrated into Skuid Forums. Going forward, you will add new ideas to Nintex Ideas. Skuid Skool remains available here. Familiarize yourself with
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.