Hi there, ​@Jazzy3!

It’s possible to set conditional logic for form fields to show different fields based on certain conditions. Like if the Name field is not empty:

So that would get the color field to appear only if a name has been selected.

The option to set a Default Value appears in the form’s Field Settings however, it won’t set the default value if the Dropdown field is being populated dynamically from another table. It only works if the Selection source is set to Static list. So I’d recommend reaching out to Support team to put in a request to allow it to work for dynamically loaded dropdown options as well.

In the meantime, you could add some text to the Placeholder field to show that the selected color as Brown:

So the value “Brown” would appear to be selected by default but wouldn’t actually have the Brown color option selected:

Then as you say, you could have a Zap update the color in the table record for their submission if no color was selected.

Would that work?

This is what support suggested. when submitted it clears the boxes on the interface. 

Here’s one way you could set up a workaround using a text field and a Zap:
 

1. Interface setup

• • Add your first dropdown field in Interfaces that pulls in the “Name” values from your Zapier Table.
  • Right below it, add a text element (instead of a second dropdown). This text element can display the “default color” associated with the selected Name.

2. Trigger a Zap on form submission

• • When someone submits the Interface form, the Zap can look up the selected Name in your Zapier Table.
  • The Zap then finds the corresponding “Color” value for that Name.

3. Handle default vs. override logic

• • If the user wants to keep the default color, the Zap just carries that forward into Salesforce.
  • If they want to override it, you can add another dropdown in the form that shows all available colors (sourced from your “Colors” table).
  • In the Zap, use a step that says: If override color is blank → use default color. Otherwise → use override color.

4. Send to Salesforce

• • Finally, the Zap creates the Salesforce Case with the selected Name and whichever Color logic applied.

This won’t give you the “dependent dropdown” effect in real-time inside the Interface, but it does give your end users a way to see the default, optionally override it, and still keep Salesforce in sync. 
 

Thanks for sharing that ​@Jazzy3. With Support’s approach clearing the fields (boxes) when submitted - that would be because it’s using a form component so whatever is selected would then be cleared to allow you to select new values to submit next time. 

Can you give me more details about what the form is being used for exactly, curious as to why the form’s fields would need to keep their previous values? Is it that people will be submitting the form multiple times for the same name but would select different colors? 

And does the default color need to change based on the name value that’s been selected? For example are you wanting to allow users to select their own name, show them the color associated with their name (the default color?) then create a case in Salesforce automatically using the relevant name and color they select?

If it’s their own name that they’re selecting perhaps you could give them a prefilled link unique to them, I’d have thought that then the name selection should persist when the form is submitted. Or does the color value definitely need to persist as well? 

support said it cannot be done and we tried alternatives which could not accomplish what i was trying to accomplish. i ended up using the deafuly color that is already in the table and then in the KANBAN they are ablel to see and change if needed.

Scenario:
dropdown chooses the persons name from a zapier table and then shows the default color for that person (in same record in same table). another drop would be used to change the default if they wanted to. then submit