Determining which project parameters are used

[andy_wilson02]

Inexperienced Revit user here, but design lead for a big project...

Can anyone advise how to determine which project parameters are used, as in one or more objects have an entry for that parameter? Members of the team, trying to be helpful, have merged parameters from multiple other projects. Now amongst the 1150 project parameters I have, for example, 7 named Acoustic Rating and 12 with variations of Fire Rating. Although all those are now embedded in families, only one of each variant has data. I need to ditch the rest, but I need to know which of the identically named ones is driving the view filters etc. first!

I've found 'Parameter-Purge-Unused.dyn' in the forums (that got me down from 2700 parameters), but this seems not to achieve the goal.

[RDAOU]

@andy_wilson02 

Which parameters are bugging you exactly? The project parameter list contains 3 types of parameters. The local project parameters added by user to the project (can be easily removed if null). these parameters cannot have duplicate/identical name and I am sure they are not the issue which leaves out:

1. shared parameters added by the user directly into the model(s) (can be easily removed if null)
2. shared parameters from loaded families (If it is in a family it would be considered USED even if its value is null and not easy to remove from the project you would need a dyn or addin that does the process in the background.)

If your intent is to keep the right shared parameter that corresponds to your company's  shareparamers database, purging out the nulls is not the right way to go. Those with values could be the the external or 3rd party shared parameters with a foreign GUID and are not the ones in your list. So unless you are certain I wouldnt advise that you proceed with the purging nulls. Your dyn graph should look up all shared parameters in the project >>> get their GUID, parse the .TXT sharedparmeterfile and compare GUIDs then

• remove the parameter with the odd GUIDs AND null values
• if value of the odd GUID parameters is not null, copy value to the right parameter to their  then remove the odd one out

Unless someone else knows of a plugin/addin/on which can solve this for you, sharing the dyn you have one may help you develop it further but from scratch, I hardly have time to log in and answer 2-3 question (Havent even had the time for that the past 2 years)