Define and manage component-level data fields with precision and flexibility.

The Fields tab in Xuda Studio App Builder is where developers define the structural elements of a component’s data model. Each field represents a variable or computed property that can be linked to the component’s logic, events, or UI bindings.

The screenshot shows a Virtual Field setup — a flexible placeholder that can store dynamic or computed values at runtime. Developers can define the Field Type (such as String, Number, Boolean, or Object), assign an identifier, and configure value behavior (static or computed). Additional attributes such as Mask and Comment enable contextual documentation and formatting control.

On the right, the Properties panel provides an intuitive configuration interface where users can set Type, Field ID, Field Type, and Value. Actions such as adding or deleting fields are streamlined, ensuring quick adjustments during iterative development.

The Fields tab integrates seamlessly with other builder sections like Datasource, Events, and UI, allowing developers to bind fields to event triggers, data sources, or visible UI elements — keeping data flow unified and modular across the entire app environment.

Dynamic Field Creation

Add, modify, and remove fields to define your component’s data structure in real time.

Virtual & Computed Fields

Use virtual fields for calculated or temporary values without altering persistent data sources.

Comprehensive Property Controls

Adjust type, mask, and computed state directly from the properties panel for precise data management.

Seamless Data Binding

Link fields with datasources, events, and UI components to maintain consistent data synchronization.

Modular Reusability

Reuse field structures across multiple components for efficient and standardized data modeling.

FAQs

The Fields tab allows developers to define, manage, and structure component-level data models by creating fields that store or compute values dynamically.

Developers can define static fields, computed fields, or virtual fields with types such as String, Number, Boolean, Object, or Array—depending on the data logic required.

A Virtual Field is a dynamic placeholder that stores computed or temporary values at runtime, enabling flexible data manipulation without altering the base schema.

Each field can have a static value assigned manually or a computed value linked to expressions, events, or logic operations for real-time updates.

The Field Type determines the data format—such as String, Number, Boolean, or Object—defining how the field stores and interprets its assigned value.

Mask defines how a field’s value is formatted or displayed, ensuring consistent input handling and output presentation across the component’s UI.

Yes. Developers can add comments or descriptive notes for each field, helping teams understand the field’s purpose, logic, and usage context.

Fields integrate with Datasource, Events, and UI tabs, allowing seamless binding between data, logic triggers, and visual components.

Yes. Field definitions can be replicated or referenced across components, maintaining consistency and reducing redundant configuration effort.

Accurate field configuration ensures predictable data handling, smooth runtime execution, and clean integration with UI bindings and event-driven workflows.

Develop. Deploy. Stay Productive.

Xuda is the platform for frontend developers, providing the speed and reliability innovators need to create at the moment of inspiration.

Schedule a demo