Parameter Catalog - Controlled parameter values

Parameter Catalog lets teams define parameter catalogs and allowed values for the model. The tool helps apply standardized values, validate compliance, and transfer configuration between the model, local cache, and JSON files.

General Description

The add-in organizes model parameters into an editable catalog, lets users assign allowed values, and then applies those values to selected elements. It also includes a validation layer to detect elements that do not comply with the defined catalog.

Key Features

• Three tabs: Standards (build the catalog), Execute (apply values), Validation (find non-compliant elements).
• Editable catalog: Add model parameters to the catalog, then define their allowed values (paste multiple lines at once).
• Value application: Pick a catalog entry and one of its allowed values, then apply it to selected elements.
• Model validation: Validate the whole model or just the current selection; only non-compliant elements are listed, with category, element, parameter, and current value.
• Storage and transfer: Save the catalog to the model (ExtensibleStorage), a local file, or JSON, with model data always taking priority over local when both exist.
• Work profiles: Save and reuse full catalog configurations.

Requirements

• Applying values requires the target parameter to exist and be writable on the selected elements.

Usage Procedure

Build the catalog (Standards tab)

1. Open Parameter Catalog from the Model panel on the Frata ribbon tab.
2. Under Model Parameters, select a parameter and press Add to Catalog to create a Catalog Entry for it (or Remove an entry you no longer need).
3. With an entry selected, add its Allowed Values — you can paste multiple lines at once to add several values in one go.
4. Press Save Catalog to Model to store the catalog in the project, or save it as a profile for reuse.

Apply values (Execute tab)

1. Select a Catalog Entry and the Value to Apply.
2. Select elements in the model and press Apply.
3. Review the result — if some elements couldn't be modified, press View Details to see which ones and why.

Validate compliance (Validation tab)

1. Press Validate Model to check the whole project, or Validate Selection to check only the elements you have selected (if nothing is selected, Revit prompts you to pick elements).
2. Only elements that fail the catalog rules are listed, with their Category, Element, Parameter, and Current Value.

Backup and transfer (Configuration / Import-Export)

1. Open Configuration (or Import / Export from the Standards tab) for Recovery, Model, Local, and Transfer options.
2. Use Save to Model / Load from Model for the project's own stored catalog, Save Local / Load Local for your local cache, or Import JSON… / Export JSON… to share a catalog as a file.
3. Remember: the model's saved catalog always has priority — local data is only used automatically when the model has no saved catalog of its own.

Recommendations

• Changes you make in the Configuration window are auto-saved to your local cache as you go, independent of whether you've pressed Save to Model yet — use Restore from Local if you need to recover from that cache.
• Export a catalog to JSON when you want to hand it to another project or teammate rather than relying on them opening this specific model.
• Validate the whole model periodically, not just your current selection, to catch drift introduced by other team members.

Frequently Asked Questions

I got the message "This parameter is already in the catalog." Why? You tried to add a parameter that already has a Catalog Entry. Select the existing entry instead of adding it again.

I got the message "This value already exists in the list." Why? You tried to add an allowed value that's already present for that entry — duplicates aren't allowed.

Some elements "could not be modified" after applying a value. Why? The target parameter is likely missing or read-only on those specific elements. Press View Details to see exactly which elements failed.

If both the model and my local file have a saved catalog, which one wins? The model's saved catalog always takes priority. Local data is only used automatically when the model has no catalog of its own — use Load from Model or Restore from Local explicitly if you want to override that.

Do I need to validate before applying values, or after? Either works, but validating after applying is the more useful check — it confirms the values you just wrote (and any values set outside this tool) actually conform to the catalog.