Form Conditional Logic Not Showing or Hiding Fields
Your Base44 form has conditional logic configured (show shipping fields when 'delivery' is selected, hide company fields for individual customers, display additional questions based on previous answers) but the conditions don't work. Fields that should appear stay hidden, fields that should hide stay visible, and the form behaves the same regardless of user selections.
Conditional forms are essential for creating clean, user-friendly interfaces that don't overwhelm users with irrelevant fields. When conditional logic breaks, users either see an intimidating form with too many fields, or they miss required fields that should have appeared based on their selections.
The issue is particularly disruptive when hidden fields have validation rules — users can't submit the form because a hidden required field has no value, but they can't see the field to fill it in.
Error Messages You Might See
Common Causes
- Condition references wrong field ID — The conditional rule points to a field that was renamed, deleted, or has a different internal ID than expected
- Case sensitivity in condition values — The condition checks for 'Delivery' but the dropdown value is 'delivery' (lowercase)
- Multiple conditions with wrong AND/OR logic — Conditions are combined with AND when they should use OR, making them impossible to satisfy simultaneously
- Condition evaluates on form load only — The visibility check runs once on page load but doesn't re-evaluate when the user changes their selection
- Hidden fields still requiring validation — Fields that are conditionally hidden still enforce their validation rules, blocking form submission
How to Fix It
- Verify field IDs in conditions — Check that the conditional rule references the correct field by its internal ID, not its display label
- Test with exact condition values — Select the exact value the condition expects and verify the field visibility changes. Check for case sensitivity
- Simplify conditions to debug — Reduce conditions to a single, simple rule (one field equals one value) and verify it works before adding complexity
- Disable validation on hidden fields — Ensure that when a field is hidden by a condition, its validation rules are also disabled
- Test all condition branches — Systematically test each possible value of the controlling field and verify the correct fields appear/disappear for each
Real developers can help you.
Sage Fulcher
Hey I'm Sage! Im a Boston area software engineer who grew up in South Florida. Ive worked at a ton of cool places like a telehealth kidney care startup that took part in a billion dollar merger (Cricket health/Interwell health), a boutique design agency where I got to work on a ton of exciting startups including a photography education app, a collegiate Esports league and more (Philosophie), a data analytics as a service startup in Cambridge (MA) as well as at Phillips and MIT Lincoln Lab where I designed and developed novel network security visualizations and analytics. I've been writing code and furiously devoted to using computers to make people’s lives easier for about 17 years. My degree is in making computers make pretty lights and sounds. Outside of work I love hip hop, the Celtics, professional wrestling, magic the gathering, photography, drumming, and guitars (both making and playing them)
Costea Adrian
Embedded Engineer specilizing in perception systems. Latest project was a adas camera calibration system.
Pratik
SWE with 15+ years of experience building and maintaining web apps and extensive BE infrastructure
PawelPloszaj
I'm fronted developer with 10+ years of experience with big projects. I have small backend background too
AUXLE
I am a Full Stack Developer experienced in building Websites, Web apps and Cross Platform Mobile Apps for Startups and Companies.
ISHANTDEEP SINGH
Senior Software Engineer with 7+ years of experience in React, JavaScript, TypeScript, Next.js, and Node.js. I’ve also worked as a tech lead for startups, owning end-to-end technical execution including architecture, development, scaling, and delivery. I bring a strong mix of hands-on coding, product thinking, and technical leadership, and I’m comfortable building products from scratch as well as improving and scaling existing systems.
Matthew Butler
Systems Development Engineer @ Amazon Web Services
Franck Plazanet
I am a Strategic Engineering Leader with over 8 years of experience building high-availability enterprise systems and scaling high-performing technical teams. My focus is on bridging the gap between complex technology and business growth.
Core Expertise:
🚀 Leadership: Managing and coaching teams of 15+ engineers, fostering a culture of accountability and continuous improvement.
🏗️ Architecture: Enterprise Core Systems, Multi-system Integration (ERP/API/ETL), and Core Database Structure.
☁️ Cloud & Scale: AWS Expert; architected systems handling 10B+ monthly requests and managing 100k+ SKUs.
📈 Business Impact: Aligning tech strategy with P&L goals to drive $70k+ in monthly recurring revenue.
I thrive on "out-of-the-box" thinking to solve complex technical bottlenecks and am always looking for ways to use automation to improve business productivity.
Victor Denisov
Developer
Yovel Cohen
I got a lot of experience in building Long-horizon AI Agents in production, Backend apps that scale to millions of users and frontend knowledge as well.
You don't need to be technical. Just describe what's wrong and a verified developer will handle the rest.
Get HelpFrequently Asked Questions
Why don't my Base44 form conditions work?
The most common issues are: the condition references a field by display label instead of internal ID, the comparison value has a case mismatch, or the condition doesn't re-evaluate when users change their selection. Start by testing with the simplest possible condition.
How do I prevent hidden fields from blocking form submission?
When hiding a field conditionally, also disable its required validation. Otherwise users can't submit because a field they can't see is marked as required. The validation should only apply when the field is visible.