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.
zipking
I am a technologist and product builder dedicated to creating high-impact solutions at the intersection of AI and specialized markets. Currently, I am focused on PropScan (EstateGuard), an AI-driven SaaS platform tailored for the Japanese real estate industry, and exploring the potential of Archify.
As an INFJ-T, I approach development with a "systems-thinking" mindset—balancing technical precision with a deep understanding of user needs. I particularly enjoy the challenge of architecting Vertical AI SaaS and optimizing Small Language Models (SLMs) to solve specific, real-world business problems. Whether I'm in a CTO-level leadership role or hands-on with the code, I thrive on building tools that turn complex data into actionable value.
Dor Yaloz
SW engineer with 6+ years of experience,
I worked with React/Node/Python
did projects with React+Capacitor.js for ios
Supabase expert
Daniel Vázquez
Software Engineer with over 10 years of experience on Startups, Government, big tech industry & consulting.
Victor Denisov
Developer
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)
Luca Liberati
I work on monoliths and microservices, backends and frontends, manage K8s clusters and love to design apps architecture
Basel Issmail
’m a Senior Full-Stack Developer and Tech Lead with experience designing and building scalable web platforms. I work across the full development lifecycle, from translating business requirements into technical architecture to delivering reliable production systems.
My work focuses on modern web technologies, including TypeScript, Angular, Node.js, and cloud-based architectures. I enjoy solving complex technical problems and helping teams turn product ideas and prototypes into working platforms that can grow and scale.
In addition to development, I often collaborate closely with product managers, business analysts, designers, and QA teams to ensure that solutions align with both technical and business goals.
I enjoy working with startups and product teams where I can contribute both as a hands-on engineer and as a technical partner in designing and delivering impactful software.
AUXLE
I am a Full Stack Developer experienced in building Websites, Web apps and Cross Platform Mobile Apps for Startups and Companies.
MFox
Full-stack professional senior engineer (15+years). Extensive experience in software development, qa, and IP networking.
Matthew Jordan
I've been working at a large software company named Kainos for 2 years, and mainly specialise in Platform Engineering. I regularly enjoy working on software products outside of work, and I'm a huge fan of game development using Unity. I personally enjoy Python & C# in my spare time, but I also specialise in multiple different platform-related technologies from my day job.
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.