Revit Shared Parameter Conflicts: Repair Duplicate Names Without Losing Project Data

Written by

Revit duplicate shared parameters can have the same name but different identities, leaving schedules, and tags reading a different field from the one holding your data.

A shared parameter is a reusable definition for information such as an asset identifier or fire rating.

Revit identifies each shared definition using a GUID, or globally unique identifier. Two fields called “Fire Rating” can therefore look identical while storing values separately.

Changing a family or removing a parameter before recording those values can make the data harder to recover or cause it to be lost.

Thus, your first step is to find out which definition each family, tag, and schedule actually uses. Let’s nut it out.

Check Where the Duplicate Parameters Appear

Duplicate parameters can appear in family and project fields, while their effects show up in schedule columns and tag labels.

Start with an affected element and another whose schedule and tag work as expected. Record their family and type, the duplicated or blank columns, and any tags showing question marks.

Check the relevant categories under Manage > Project Parameters and inspect loadable families through Family Types.

At this stage, treat matching names as a clue. A tag showing a question mark may use a different shared definition, but the expected parameter may simply have no value on the element.

If the model is slow, record when the slowdown occurs. Autodesk reports poor performance among the symptoms in some projects with excess duplicate parameters, but other model conditions can also affect performance.

Back Up the Model and Capture the Affected Data

Back up the model and capture the affected parameters, values, and outputs before testing changes on an isolated copy.

Create a dated, restorable backup and a separate test copy. For a file-based workshared model, open the central model with Detach from Central selected and choose Detach and preserve worksets.

Save the detached model under a different name in a separate location as an independent central model. It cannot synchronise test changes back to the original central.

For a cloud-workshared model, use the team’s approved Autodesk Docs procedure to obtain a copy and confirm its version with the model owner.

Open it independently, preserve worksets where needed and save it as a separate test model.

Please note that detaching the host model does not automatically isolate linked files or shared family libraries, so check their paths and use copies where those files need changes.

Your baseline needs to cover the data and the places that use it:

  • Parameters: Record each field’s name, parameter kind and GUID if known. Include its data type, categories, Type or Instance setting and group behaviour. Note whether it comes from a family or project binding, and mark unknown identities for investigation.
  • Values: Capture every affected value, including blanks, against its source document and element or type identifier. For type values, record which instances use each type. Preserve raw values and units where display formatting could hide a difference.
  • Content: List affected families and types, including unplaced ones. Record the tag labels, schedules, filters, formulas, and family associations that use the parameters.

Create a diagnostic Revit schedule for each affected category and add the similarly named fields alongside Family and Type.

On Sorting/Grouping, select Itemize every instance and remove filters that would hide relevant elements.

Temporarily label the columns “Field 1” and “Field 2” to keep their positions clear; record their GUIDs once verified. Changing a column heading does not change the parameter definition.

Export the schedule through File > Export > Reports > Schedule. The export alone may not capture stable identifiers, unplaced types or every dependency.

Use a validated API or Dynamo extraction where needed, then check its record count against the model.

If you cannot distinguish the source fields, keep the backup, and resolve their identities before completing that part of the baseline.

Also, always remember that UniqueId is stable within a document. Confirm that the identifiers in the test copy match the baseline; a replaced or recreated element needs its own mapping. Where applicable, distinguish an unset value from empty text, and zero.

Check GUIDs and Parameter Settings

Different GUIDs identify separate shared definitions, while matching GUIDs still need their data types and Type or Instance settings checked.

If you have not confirmed a shared parameter’s GUID, use the steps after the table before deciding which parameter to change.

FindingWhat to check
Same name, different GUIDsDecide whether the definitions represent the same information. If they do, map their values to an approved destination.
Same GUID in a family and projectThe same shared definition can be used in both. Check its data type, Type or Instance setting, and category binding before changing either use.
Same GUID, different Type or Instance settingsAgree on the intended setting and check whether it can hold the existing values.
Same name, different data typesA family may fail to load. Compare the definitions and their GUIDs before deciding how to repair them.
Same name, but one field is built-in or non-sharedRecord the parameter kind and intended use. Matching names do not make the fields interchangeable.

To identify the GUID of a shared parameter:

  1. In Manage > Shared Parameters, create or select a separate diagnostic shared parameter file for the Revit session.
  2. Select the field in Family Types, Project Parameters or the schedule’s field properties. Open its properties and use Export where available.
  3. Inspect the exported definition and its GUID. If Export is disabled, check whether the selected definition is already in the current file.

Use separate diagnostic files if necessary to distinguish same-named definitions. Where the interface cannot resolve a field, a validated API routine can enumerate matching parameters and report GUIDs for those that are shared.

Avoid relying on a name-only lookup that returns just one match: when several parameters share a name, it may return the wrong one.

Update the provisional baseline labels with the confirmed identities.

Using the same shared parameter in a family and project is supported and does not, by itself, require deletion.

However, completely removing the underlying shared-parameter data can delete associated data used in loaded families. Capture the values, and investigate dependencies before any removal.

If a parameter appears to have the same GUID but different data types, stop and investigate the definitions before making changes.

Autodesk documents family-load conflicts involving same-named parameters with different data types, but that error alone does not establish that their GUIDs match.

Also, keep in mind that data type, and value scope are different checks:

  • A data type might be Text or Number
  • A Type value applies to a family type
  • An Instance value can vary between placed elements.

If doors of the same type hold different instance values, one type value cannot preserve them all.

Find Where Each Parameter Comes From and Who Manages It

Compare the definitions in affected families and project bindings with the project’s shared parameter file or Parameters Service, then confirm who manages that source.

Check the relevant family libraries, contributed models, and project bindings. Confirm who manages the approved standard and can authorise changes to the affected content.

The shared parameter file currently selected in Revit may not be the one originally used by every loaded family.

A definition can also be stored in a family or project, so changing the selected file alone does not replace existing parameters.

Record which families and categories use each definition, including nested or linked content within the agreed scope.

Do not manually edit GUIDs or recreate a parameter using the same name as a shortcut. If a populated field still cannot be identified, stop and seek specialist help before changing it.

Map Each Parameter and Its Values to a Destination

A usable mapping identifies each source and destination, and specifies how every affected value will be retained.

Record the source GUID or non-shared parameter identity and the approved destination GUID. Add the category, data type, and instance or type setting.

The register should also identify the affected families, the element or type identifiers, and who approved the choice.

For instance, imagine two door families with an instance text field called “Fire Rating”. The project standard uses GUID A, while the second family stores its values under GUID B.

For a door whose B value is 60/60/60 and whose A field is empty, the mapping records that 60/60/60 must be restored to A on that same door. A and B stand for the actual GUIDs in the register.

If both A and B contain different values on one door, stop for an owner’s decision. One destination field cannot hold both values unchanged.

Retain both in the model or agree a separate destination for one of them; an external archive alone does not preserve both as model data.

Thus, always check data types, units, and group behaviour before approving the map. Review formulas and read-only fields too, and record exceptions rather than assuming a blank or zero can be discarded.

Test the Repair on an Isolated Model Copy

Test the approved parameter changes on an isolated model copy, then restore and check the captured values before changing production content.

For the door example, start with one affected family and a small set of doors that includes populated and blank fields. Use the actual GUIDs and element identifiers from the register:

  1. Confirm GUID A. Open the controlled shared parameter file or service definition and check the GUID and data type against the register. The shared parameter file does not determine whether the parameter is Type or Instance; choose the approved setting when applying it to the family or project. Do not create another definition with the same name.
  2. Edit the family. In the test model, open the GUID B family for editing. Under Family Types, select the source parameter, choose Modify, and select the approved definition A. Save the edited family separately. If Revit will not accept the replacement, stop and investigate the conflict.
  3. Reload and restore the values. Load the family into the test model. Where offered, choose to overwrite the family definition without overwriting existing type values, unless the test specifically requires otherwise. The option that also overwrites parameter values replaces existing type values with those in the loaded family. Neither option proves that values moved from B to A. Restore the mapped B values to A for the same doors.
  4. Repair the outputs. In the tag family, edit the label to use definition A and reload the tag. Update the schedule field to A, retaining the required filters and formatting. Changing the label or schedule field does not transfer the values.
  5. Check the pilot. Compare each restored value with the baseline, including blanks, and any pre-existing A values. Check that the affected tags and schedule rows show the expected results.

Hence, a coordinator can restore a small number of editable values manually using the captured identifiers.

For larger sets, use a reviewed API or Dynamo routine that targets the correct parameter identities, reports missing or unwritable elements, and checks each result.

A name-only lookup is unsafe when names are duplicated.

If the source is project-bound, inspect Manage > Project Parameters in the test copy.

If A is already bound, check whether its categories and setting need adjustment; otherwise, test adding the existing A definition with the approved settings.

Since a binding can affect every element in its categories, include them in the baseline.

If the definitions cannot coexist safely, stop and plan a staged migration rather than deleting the source to make room.

If the GUID matches but Type and Instance differ, agree on the intended setting without replacing the GUID.

Before changing instances to a type parameter, compare the values of every affected instance within that type. If they differ, keep them at the instance level, or agree another way to retain them.

Once the setting is approved, select the parameter under Family Types > Edit Parameter, and change it where editable.

Inspect the project binding under Project Parameters > Modify, and test aligning it if Revit permits.

If it does not, stop and plan a staged repair rather than forcing the change.

For a move from type to instance, restore the captured type value to each affected instance and test what a newly placed instance receives. Check the results against the baseline after reloading.

Do not purge a hidden parameter to tidy the model. Autodesk documents a case in which a removed shared parameter remains hidden with its data and may return when the same GUID is reintroduced.

Completely removing the underlying shared-parameter data can delete associated data used in loaded families.

Recovery depends on what was removed and the available backup; recreating the name is not a restoration method.

Reconcile Values, Tags, and Schedules

Compare every mapped value with the baseline, then check that the affected tags, schedules, and families use the approved destination.

The pilot proves only that the method worked for the tested elements. Extend it to the remaining affected families in the test copy, then compare records by source document and element or type identifier.

Account for blanks, units, and any missing or new identifiers. Investigate every difference before accepting the result. Use the recorded outputs to check the rest of the repair:

  • Tags: compare affected tags with the expected values across the relevant families, and linked models. Recheck the labels that previously showed question marks.
  • Schedules: verify the destination fields, row counts, filters, calculations, and totals against the approved mapping. Unrelated results should remain unchanged.
  • Families: test affected types, formulas and associations, including unplaced types captured in the baseline.

Removing B from a schedule removes the displayed column, but B may still be used elsewhere.

Once all affected values and dependencies have been migrated and reconciled, test retirement of any obsolete family parameter or project binding as a separately approved cleanup.

Keep it if anything still depends on it, and repeat the checks after each removal.

Approve the Release or Roll Back

Release the repair only after the BIM lead and data owner approve the results and rollback plan; roll back if live-model checks reveal unexplained discrepancies.

Keep the approved GUID map with the affected families, bindings, test results, and exceptions. Record the responsible person and restoration point.

Agree a change window, repeat the proven procedure in the working model, and run the reconciliation again.

Before issuing an affected schedule in a tender package, confirm that the approved model and its outputs match.

Stop and restore the agreed backup if values disappear, conflicts remain unresolved, or tags and totals change unexpectedly.

This also applies if the repair affects categories outside the approved scope.

For workshared or cloud models, coordinate restoration with the project team and follow its established procedure.

Before the Repaired Schedule Reaches the Client

Duplicate shared parameters can leave fire ratings blank in a door schedule even when the values remain in Revit.

Changing the schedule field may clear the blanks, but it won’t confirm what the tags and families read.

If the client catches a mismatch at handover, the team is back tracing definitions instead of signing off the model.

An Interscale BIM audit service can map the conflicting GUIDs, identify affected families and schedules, and rank repairs in a findings report.

That gives the BIM lead a defined scope to approve before further changes.

Or, if reused families caused the conflict, Interscale’s Revit family services can help correct them too.

Book a free discussion with Interscale to decide whether your model needs an audit before handover.

Facebook
LinkedIn
WhatsApp

Author

Danoe Santoso

Danoe Santoso is a writer specialising in IT and technology within the Architecture, Engineering, and Construction (AEC) industry, covering digital tools, software solutions, and emerging technologies that help industry professionals improve productivity, collaboration, and project outcomes.

Technically Reviewed By

Januar Utomo

A BIM Engineer specialising in Revit and AutoCAD, with a focus on developing efficient BIM workflows and creating Revit Families to enhance design efficiency and improve project coordination.

Confirm your booking
for a Discovery Session meeting