All resources

FormFlow or FlexiForm?

Start with one question: are you changing how an existing field behaves, or asking a new set of questions?

Use FormFlow for existing fields.

If the data already has a column and a place on the model-driven form, FormFlow is the relevant module. Its baseline preview covers behavior such as showing a field, requiring a value, filtering a choice and validating input.

For example, an account form might show a detail field only when a supported choice value requires it. The data model stays the same; the experience becomes more relevant.

Consider FlexiForm for questionnaires.

If each new assessment would otherwise require another set of columns, the FlexiForm preview is worth exploring. It is designed around question definitions and structured answers connected to a record, with conditional questions, optional phases and scoring.

FlexiForm has a deployed preview with administrator checks completed; separate-user security acceptance remains open. Its initial scope is internal and online, rather than a public survey or an offline field experience.

Check the native fit first.

A simple requirement may already fit your existing form tools. Start there, and compare any added module against a concrete maintenance or experience problem.

For either approach, validate security in Dataverse itself. Hiding a control is not the same as restricting access to the underlying information.