# Populate Form Based on Field (If/Then…)

**URL:** <https://community.noloco.io/t/populate-form-based-on-field-if-then/2073>\
**Category:** Ask for Help\
**Created:** [July 24, 2025, 4:43pm UTC](https://community.noloco.io/t/populate-form-based-on-field-if-then/2073 "2025-07-24T16:43:31Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![andrew](https://avatars.discourse-cdn.com/v4/letter/a/f19dbf/32.png) [@andrew](https://community.noloco.io/u/andrew)\
**Post date:** [July 24, 2025, 4:43pm UTC](https://community.noloco.io/t/populate-form-based-on-field-if-then/2073/1 "2025-07-24T16:43:31Z")

</div>

Is there a way to populate fields on a form based on previous fields input?

For example, I have a Type field with Type A, Type B, Type C.

After that there are Unit and Cost fields.

If a user selects Type A, then populate Unit with 5 and cost with $1.00.

If a user selects Type B, then populate Unit with 3 and a cost of $10.00.

Etc.

Unit and Cost fields would be Single Select options.

Thanks!

---

<div class="post-metadata">

**Author:** ![garyGHL](https://dub1.discourse-cdn.com/flex005/user_avatar/community.noloco.io/garyghl/32/555_2.png) [@garyGHL](https://community.noloco.io/u/garyGHL)\
**Post date:** [July 25, 2025, 8:40am UTC](https://community.noloco.io/t/populate-form-based-on-field-if-then/2073/2 "2025-07-25T08:40:09Z")

</div>

Hello, not an expert but could you use a formula field for Unit & Cost fields? I think this would only be feasible for a small number of options, if there were loads it may be complicated.

I use something similar for my app as follows. This checks the Model (field) to check if the word “ **Latitude** ” is there, if it exists the the output is **‘Dell’**

> IF(ISNUMBER(FIND(“ **latitude** ”, LOWER(Model))), “ **Dell** ”, “”)

**So in your example, maybe this (untested)**

Unit Field (Formula)

> IF(ISNUMBER(FIND(“TypeA”, LOWER(Model))), “5”, IF(ISNUMBER(FIND(“TypeB”, LOWER(  
> Model))), “3”, “”))

Cost Field (Formula)

> IF(ISNUMBER(FIND(“TypeA”, LOWER(Model))), “$1”, IF(ISNUMBER(FIND(“TypeB”, LOWER(  
> Model))), “$10”, “”))

etc etc

 ![image](https://europe1.discourse-cdn.com/flex005/uploads/noloco/original/2X/d/dacfb108b782a030d555d4ffc2405a9866c35585.png)

---

<div class="post-metadata">

**Author:** ![andrew](https://avatars.discourse-cdn.com/v4/letter/a/f19dbf/32.png) [@andrew](https://community.noloco.io/u/andrew)\
**Post date:** [August 11, 2025, 10:22pm UTC](https://community.noloco.io/t/populate-form-based-on-field-if-then/2073/3 "2025-08-11T22:22:22Z")

</div>

My use case is too complex for creating formula fields. It’s basically selecting a “type” of deliverable that then populates a dozen plus fields with prefilled data.

Would be great to have conditional forms in Noloco that would allow this.

---

<div class="post-metadata">

**Author:** ![darragh](https://dub1.discourse-cdn.com/flex005/user_avatar/community.noloco.io/darragh/32/12_2.png) [@darragh](https://community.noloco.io/u/darragh)\
**Post date:** [August 12, 2025, 1:25pm UTC](https://community.noloco.io/t/populate-form-based-on-field-if-then/2073/4 "2025-08-12T13:25:13Z")

</div>

I think you should be able to do this with Workflows @andrew

When you create the item, use workflows to conditionally populate other fields / related fields.

---

<div class="post-metadata">

**Author:** ![andrew](https://avatars.discourse-cdn.com/v4/letter/a/f19dbf/32.png) [@andrew](https://community.noloco.io/u/andrew)\
**Post date:** [August 18, 2025, 3:20pm UTC](https://community.noloco.io/t/populate-form-based-on-field-if-then/2073/5 "2025-08-18T15:20:51Z")

</div>

That makes sense. I was looking for something more flexible based on our needs, but I can create some workflows based on checkboxes to help streamline.

For clarity on what I’m doing, we create Deliverables (videos) for our clients. Those videos have specs (resolution, frame rate, codec, etc). In most cases, we use 2-3 standard set of specs, but there are regular needs to modify those specs.

I was hoping to pre-populate the specs based on Deliverable type, but also allow the user to change specs if there is a need. I don’t Workflows will work because they will change any modified specs based on Type selected. I can, and may, set up new checkboxes for our standard deliverable types so if that’s selected the workflow is trigged.

Quick example, every project gets a WEB deliverable type. Those specs are typically 1920 x 1080, H264 codec, 35 mb/s, etc.

A client may request multiple WEB deliverables and may need one that is 10 mb/s. That’s what would break a workflow unless there’s a separate field as mentioned above.