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.

Luca Liberati Luca Liberati I work on monoliths and microservices, backends and frontends, manage K8s clusters and love to design apps architecture AUXLE AUXLE I am a Full Stack Developer experienced in building Websites, Web apps and Cross Platform Mobile Apps for Startups and Companies. 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. Jared Hasson Jared Hasson Full time lead founding dev at a cyber security saas startup, with 10 yoe and a bachelor's in CS. Building & debugging software products is what I've spent my time on for forever Costea Adrian Costea Adrian Embedded Engineer specilizing in perception systems. Latest project was a adas camera calibration system. Milan Surelia Milan Surelia Milan Surelia is a Mobile App Developer with 5+ years of experience crafting scalable, cross-platform apps at 7Span and Meticha. At 7Span, he engineers feature-rich Flutter apps with smooth performance and modern UI. As the Co-Founder of Meticha, he builds open-source tools and developer-focused products that solve real-world problems. Expertise: 💡 Developing cross-platform apps using Flutter, Dart, and Jetpack Compose for Android, iOS, and Web. 🖋️ Sharing insights through technical writing, blogging, and open-source contributions. 🤝 Collaborating closely with designers, PMs, and developers to build seamless mobile experiences. Notable Achievements: 🎯 Revamped the Vepaar app into Vepaar Store & CRM with a 2x performance boost and smoother UX. 🚀 Launched Compose101 — a Jetpack Compose starter kit to speed up Android development. 🌟 Open source contributions on Github & StackOverflow for Flutter & Dart 🎖️ Worked on improving app performance and user experience with smart solutions. Milan is always happy to connect, work on new ideas, and explore the latest in technology. Yovel Cohen 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. 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. Meïr Ankri Meïr Ankri Full-stack developer specializing in React / Next.js / Node.js with 6+ years of experience. I've worked across various sectors including automotive (Reezocar/Société Générale), healthcare (Medical Link SaaS), and e-commerce (Glasman). I build web apps end-to-end, from architecture to production, with a focus on scalability, performance, and code quality. I also mentor junior developers and contribute to technical decisions and code reviews. Franck Plazanet 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.

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