Inputs and Forms

Editable cells are the inputs to your NExS app. This guide covers how to configure inputs, add validation, and build interactive forms.

Defining Editable Cells

Use the editable (or input/inputs) keyword in your view configuration:

This allows users to edit cells B3 through B8 and cell C12.

Single vs. Multiple Inputs

You can list inputs on one line or split them for clarity:

Or split them into logical groups:

Both input and inputs work the same as editable.

Adding Comments

Document your configuration with comments (start with # or //):

Input Types

By default, editable cells accept text input. Add attributes to create specialized input types.

Checkboxes

Checkboxes work well for yes/no questions, feature toggles, and boolean options. When checked, the cell receives the value 1; when unchecked, it receives 0. Your Excel formulas can then use these values in calculations or conditional logic.

Radio Groups

When users need to pick exactly one option from a set, radio groups enforce mutual exclusivity. Clicking any option in the group sets that cell to 1 while automatically setting all others to 0. This is ideal for survey questions, plan selections, or any “choose one” scenario.

Email and Phone Validation

Adding email or phone as an attribute tells NExS to validate the input format before accepting it. Email validation ensures the value follows standard email format (like user@example.com), while phone validation checks for valid phone number patterns. Invalid entries are rejected, preventing malformed data from reaching your spreadsheet.

Required Fields

Marking inputs as required integrates with NExS’s form validation system. On its own, this attribute flags the field visually. Combined with the %REQUIRED button macro, you can disable submit buttons until all required fields contain values—preventing incomplete form submissions.

Combining Attributes

Apply multiple attributes by separating with commas:

This creates a required email field.

Access Control on Inputs

When multiple people use the same app, you often need different people to edit different fields. NExS provides granular control over who can modify specific inputs.

By Access Key

In Access Code apps, different access keys can grant different editing permissions. An admin might be able to edit configuration fields while regular users can only fill in their own data sections.

Read vs. Write Access

Team mode apps can separate viewing and editing permissions. Use readACL to control who sees the view and writeACL to control who can modify its inputs. This lets you create dashboards where many people view the data but only designated users can make changes.

Building Forms

Example: Contact Form

Excel layout (Sheet1):

NExS.app configuration:

Cell A8 content: Submit {disabled: %REQUIRED, sendData: 'B3:B6'}

This creates a form where:

• Name, Email, and Message are required
• Email must be a valid format
• Phone is optional but validated
• Submit button is disabled until all required fields are filled
• Clicking Submit emails the form data to sales@company.com

Example: Multi-Step Form

Use multiple views to create a wizard-style form:

Navigation buttons:

• Step 1, cell A14: Next {disabled: %REQUIRED, setView: 'Step 2'}
• Step 2, cell A33: Back {setView: 'Step 1'}
• Step 2, cell A34: Submit {sendData: 'A1:F35'}

Form Validation Tips

1. Use required sparingly — Only mark truly essential fields
2. Group related inputs — Logical sections improve user experience
3. Provide clear labels — Users should know what each field expects
4. Use format validation — Email and phone validation prevent errors
5. Give feedback — Use conditional formatting to highlight errors

Next Steps

• UI Components — Add buttons, sliders, and status indicators
• Deployment Modes — Configure access control
• JavaScript API — Programmatic form control