I’m using a multi-step form (3 steps) with Formidable Forms, and I’m encountering an issue with populating default values across different steps.

Here’s my setup:

• Name Field: [1]
• Email Field: [2]

I want to use the values from these fields as default values in other fields later in the form. For example, in the 3rd step, I have a paragraph field where I want to display a summary of the user’s input from the 1st and 2nd steps. I’m using the “Default Value > Calculation > Type = Text” option to populate this paragraph field with shortcodes like [1], [2], and [3], each on a new line to show the summary of user data.

However, these shortcodes only seem to work in single-step forms or in a 2-step form where you can show values from the 1st step in the 2nd step. When it comes to displaying values from the 1st and 2nd steps in the 3rd step, the default values don’t populate as expected.

Additionally, I want to use field shortcodes to dynamically populate other fields’ labels and default values within a single-step form. For example:

• If the user fills in the “First Name” field ([1]), I want the label of the “Email” field to display as “What is your email, [1]?” so that it reads, “What is your email, John Doe?” (assuming [1] is “John Doe”).

This functionality isn’t working as intended. It seems that shortcodes can’t be used to populate labels or default values in the same step, and they only work in a 2-step form when moving to the next step.

Could you please update the plugin to include these features, or provide a workaround that would allow these shortcodes to populate field labels and default values across multiple steps?

Thank you for your continued support!

Best regards,
Zeeshan

I cannot use this survey until this is fixed!!

When elements are placed in a Group, their Default Value preset is not retained. Am I doing something wrong or is this a bug?

Thanks,

Jerome

So I thought, I bet there’s a default value. And sure enough, under Advanced Settings > Schema defaults > Review you provide a “Default Review Rating Min” value. So I thought it would be great to change that to .5 and no more worries.

Except, according to the error I got, this value can’t be set any lower than 1.

I know it’s easy enough to change this value, but I’m trying to reduce the drag on adding new articles for my team, and it’s already a pain to dig deep into the nested menus to update the rating. I’d love to take this one thing off their “I have to remember this” place.

This works fine so far, but if the user does not change the value of the ‘Multiple choice’ fields, the data is lost after saving. (If they change it (add or delete values), everything still works super well. )

So why does it happen that the default values (if not changed) are clears the fields values and the field becomes empty (or corrupted) after submission?

Make a text field, go to advanced, add {@ID} as the default value. Make a new record and hit save. It should auto save the post id in 2.9.19 and before but is blank going forward.