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
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.
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 : )
rayush33
JavaScript (React.js, React Native, Node.js) Developer with demonstrated industry experience of 4+ years, actively looking for opportunities to hone my skills as well as help small-scale business owners with solutions to technical problems
Richard McSorley
Full-Stack Software Engineer with 8+ years building high-performance applications for enterprise clients. Shipped production systems at Walmart (4,000+ stores), Cigna (20M+ users), and Arkansas Blue Cross. 5 patents in retail/supply chain tech. Currently focused on AI integrations, automation tools, and TypeScript-first architectures.
Victor Denisov
Developer
David Olverson
Solo dev shipping production apps with AI-assisted development. I specialize in rescuing broken Lovable/Bolt/Cursor builds and taking them to production. 10+ apps shipped including SaaS CRMs, gaming platforms, real estate tools, and Discord bots. Stack: Next.js 16, TypeScript, Tailwind CSS, FastAPI, PostgreSQL, Prisma. I use Claude Code with 50+ custom skills for rapid delivery. Average turnaround: 2-4 weeks from broken prototype to production.
hanson1014
Full-stack developer experienced in fixing and deploying AI-generated apps from Lovable, Bolt.new, Cursor, and Replit. I specialize in debugging Supabase integration issues (auth flows, RLS policies, database connections), fixing broken deployments, resolving routing/blank screen problems, and cleaning up messy React/Vite codebases. I also build production apps with the Claude API and have shipped a Mac desktop dev tool (Nexterm from scratch. Based in Hong Kong, fast turnaround.
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.
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.
Nam Tran
10 years as fullstack 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)
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.