Skip to content
howtoifs.IFS CLOUD, EXPLAINED.

IFS client keywords and examples

Build a page, choose a control, and understand where its keywords belong. Start with a page and its projection contract, then use the lookup below to find a keyword such as lov, required, bulkexecute, or ganttchart.

Baseline: IFS Cloud 26R1. References reviewed 2026-09-28. Examples are original teaching fragments, not compiled or executed in IFS. Names beginning with Demo or Training are fictional contracts to implement or replace in your own development project.

Browse the ten practical guides, or look up an individual keyword below.

Find a keyword or control

Section titled “Find a keyword or control”

Search covers local guide keywords plus the official component and property indexes. Guide and examples links lead to explanations, snippets, prerequisites, and checks. Official reference only means this site does not yet provide an example for that entry. This is not an exhaustive grammar for every release or nested keyword. A property can be valid for one container and invalid for another; check its placement and value type.

Projection-contract entries belong to .projection models, not .client declarations. The projection header in a client simply selects its service. Some official pages are incomplete, including Image Viewer implementation details; the index does not invent missing syntax.

404 entries

Practical guides

  1. Client file structure, pages, and data binding

    Build a client page and understand client, projection, page, for, using, navigator, group, and selector.

  2. Fields, expressions, and validation

    Use field, static, required, visible, editable, computedfield, dates, Boolean controls, and specialized input properties.

  3. Lists, layout, cards, and reusable fields

    Bind detail lists and arrange groups, tabs, cards, sheets, and reusable fieldsets in a client page.

  4. LOVs, selectors, search context, and units

    Build a lookup with the correct reference keys, add filtering, and display currency and measure values.

  5. Commands, calls, messages, and navigation

    Use command, execute, call, into, variable, set, confirm, bulk operations, navigation, and stream transfers.

  6. Dialogs and assistants with explicit input and output

    Build modal input, cancellation, steps, finish commands, and single-step or dynamic assistants.

  7. Charts, badges, progress, and state indicators

    Create six chart types and status presentations with explicit data and reconciliation checks.

  8. Calendars, Gantt charts, maps, and Kanban boards

    Bind scheduling and spatial controls, then verify time ranges, relationships, drag behavior, and saved results.

  9. Trees, timelines, rich content, and AI controls

    Use tree, treediagram, processviewer, timeline, addressfield, images, JSON, signatures, and AI-related UI settings.

  10. Build, test, and troubleshoot a client keyword change

    A repeatable procedure for validating client syntax, projection contracts, permissions, bindings, and runtime behavior.

Follow the examples safely

Section titled “Follow the examples safely”
  1. Read the guide’s data contract and map the fictional types, fields, methods, and entity sets to your project.
  2. Add one control at its stated scope and include its reference in the page. Build the client and projection dependencies.
  3. Use a small dataset with known results. Test selection changes, nulls, boundaries, and allowed/denied users.
  4. For commands, test cancellation and server failure as well as success. Reload after a write to verify persistence.
  5. Record actual results with the build and acceptance procedure.

Downloads

Section titled “Downloads”

Official release reference

Section titled “Official release reference”

Use the IFS 26R1 component reference and control property list alongside the editor grammar for your installed release. This independent guide does not replace the vendor’s supported development workflow.