Conditional Fields in Brickworks

Feature Overview 

Conditional Fields make schemas context-aware by allowing field requirements to change based on other values in the same record. 

It helps teams avoid duplicating structures and adding manual validation logic. 

What Are Conditional Fields? 

Conditional Fields are a schema capability that allows you to define whether a field is required based on another field’s value within the same record. 

Instead of making fields always mandatory, you can ensure they are required only when relevant conditions are met. 

Why Conditional Fields Matter 

In many data models, some fields are only relevant in specific scenarios. Without this feature, teams typically: 

• create multiple similar schemas, or 
• rely on manual validation logic 

Conditional Fields solve this by: 

• reducing user confusion and input errors 
• ensuring only relevant data is required 
• minimizing schema duplication 
• simplifying maintenance of complex data models 

Key Capabilities 

Dynamic field requirement 

Fields become required only when specific conditions are met during record input. 

Field-to-field dependencies 

A field’s requirement can depend directly on the value of another field within the same record. 

Context-based schema behavior 

One schema can support multiple use cases, adapting dynamically to user input.  

How It Works 

1. Create or edit a schema in Brickworks 
2. Mark a field as conditionally required 
3. Define a condition based on another field (e.g., payment method) 
4. During record input, Brickworks evaluates the condition 
5. If the condition is met → the field becomes required 
6. If not → the field remains optional  

Example Use Case 

A payment form supports multiple methods: 

• If Card is selected → required fields: card number, expiration date 
• If BLIK is selected → required field: BLIK code 
• Card details are not required in the BLIK scenario 

Result: one schema handles multiple payment flows without duplication.  

FAQ 

Does this feature control only the required fields? 

Yes. Conditional Fields control whether a field is required or optional, based on other values in the same record. Showing or hiding fields is handled separately via Conditional Visibility. 

Can I define multiple conditions for a single field? 

No — the Conditional visibility documentation does not describe combining conditions (AND/OR) for a single field. 

What can I use as a trigger for Conditional Visibility? 

Conditional Visibility can be driven by the value of another field in the same schema (a field-to-field dependency).  

Does it work for all field types? 

Yes — in Brickworks, Conditional Fields can be applied to all schema field types. 

Is the evaluation dynamic? 

Yes. The requirement status is evaluated in real time, based on the current values in the record during input. 

Can Conditional Fields replace multiple schemas? 

Yes — and that’s one of the main benefits. Instead of creating separate schemas for each scenario, you can: 

• keep one structure 
• adapt required fields dynamically 

Does this impact data validation? 

Yes — positively. It ensures that: 

• the required data is enforced only when relevant 
• invalid or incomplete records are reduced 
• users are not forced to fill unnecessary fields 

Key Facts 

TL;DR 

Conditional Fields in Synerise Brickworks allow schema fields to become required only in specific contexts, based on other field values within the same record. This enables a single schema to support multiple scenarios, reduces duplication, improves data quality, and simplifies user input.