Base44 testing

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

Required field hidden but validation still triggered Conditional field not appearing after selection Form submitted with missing conditional data Field visibility rule has invalid reference
Required field hidden but validation still triggeredConditional field not appearing after selectionForm submitted with missing conditional dataField visibility rule has invalid reference

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

  1. Verify field IDs in conditions — Check that the conditional rule references the correct field by its internal ID, not its display label
  2. Test with exact condition values — Select the exact value the condition expects and verify the field visibility changes. Check for case sensitivity
  3. Simplify conditions to debug — Reduce conditions to a single, simple rule (one field equals one value) and verify it works before adding complexity
  4. Disable validation on hidden fields — Ensure that when a field is hidden by a condition, its validation rules are also disabled
  5. 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.

Costea Adrian Costea Adrian Embedded Engineer specilizing in perception systems. Latest project was a adas camera calibration system. MFox MFox Full-stack professional senior engineer (15+years). Extensive experience in software development, qa, and IP networking. zipking 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. ISHANTDEEP SINGH 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. Stanislav Prigodich Stanislav Prigodich 15+ years building iOS and web apps at startups and enterprise companies. I want to use that experience to help builders ship real products - when something breaks, I'm here to fix it. Alvin Voo Alvin Voo I’ve watched the tech landscape evolve over the last decade—from the structured days of Java Server Pages to the current "wild west" of Agentic-driven development. While AI can "vibe" a frontend into existence, I specialize in the architecture that keeps it from collapsing. My expertise lies in the critical backend infrastructure: the parts that must be fast, secure, and scalable. I thrive on high-pressure environments, such as when I had only three weeks to architect and launch an Ethereum redemption system with minimal prior crypto knowledge, turning it into a major revenue stream. What I bring to your project: Forensic Debugging: I don't just "patch" bugs; I use tools like Datadog and Explain Analyzers to map out bottlenecks and resolve root causes—like significantly reducing memory usage by optimizing complex DB joins. Full-Stack Context: Deep experience in Node.js and React, ensuring backends play perfectly with mobile and web teams. Sanity in the Age of AI: I bridge the gap between "best practices" and modern speed, ensuring your project isn't just built fast, but built to last. Rudra Bhikadiya Rudra Bhikadiya I build and fix web apps across Next.js, Node.js, and DBs. Comfortable jumping into messy code, broken APIs, and mysterious bugs. If your project works in theory but not in reality, I help close that gap. Basel Issmail 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. Vlad Temian Vlad Temian 15+ years shipping production infrastructure for startups. Former CTO at qed.builders (acquired by The Sandbox). Cursor ambassador and agentic tooling builder. I've scaled systems, automated deployments, and built observability tools for AI coding workflows. I specialize in taking vibe-coded apps from broken prototype to production-ready: fixing Supabase auth/RLS, Stripe integrations, deployment pipelines, and cleaning up AI-generated spaghetti. I build tools in this space (agentprobe, claudebin, micode) and understand both sides: how AI generates code and why it breaks. https://blog.vtemian.com/ Krishna Sai Kuncha Krishna Sai Kuncha Experienced Professional Full stack Developer with 8+ years of experience across react, python, js, ts, golang and react-native. Developed inhouse websearch tooling for AI before websearch was solved : )

You don't need to be technical. Just describe what's wrong and a verified developer will handle the rest.

Get Help

Frequently 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.

Related Base44 Issues

Can't fix it yourself?
Real developers can help.

You don't need to be technical. Just describe what's wrong and a verified developer will handle the rest.

Get Help