Auditing when upgrading families

[Isaac_Wall]

So, I have a whole library of files I want to upgrade from 2015 to 2017, and shortly to 2018 too. I'm sure I can write a dynamo script to batch upgrade all of these, but it won't audit the families.

Whenever I upgrade a project I'd always audit. From what I understand auditing when opening a file fixes broken elements in the file. Does this mean families don't need auditing or only need auditing when there are nested families within them?

Basically what I wanted to know is do families need to be audited on upgrade?

Does anyone have any experience with this?

Many Thanks

[sara]

If you load them into a project file and then audit the file, does it audit the families loaded in the file? Afterwards, you can batch save out the families.. not sure how unwieldy that output would be, but I think it at least separates by category. Theories...have never audited a library's worth of families. 

[barthbradley]

---

@Anonymous wrote:

 I'm sure I can write a dynamo script to batch upgrade

---

No need to write a Dyn routine.

https://apps.autodesk.com/RVT/en/Detail/Index?id=9014092593843843383&appLang=en&os=Win32_64 

Regarding batch auditing: I'm almost positive I saw a dyn routine posted for this on some forum.  

[Isaac_Wall]

Thanks for the responses guys. I've since heard from someone who knows more about it than me who said auditing is not required for families. I made a dynamo script to upgrade the families, its a very simple script, only took a few minutes so I preferred to write one myself. Many thanks for the suggestions everyone.

[lionel.kai]

@Isaac_Wall I don't suppose you could quote your source - or give more details on WHY auditing doesn't matter for families? Partly I'm curious, but also because we've had issues, and I'd like to know whether it's truly necessary or not.

Also, Auditing definitely doesn't catch/fix everything, so I've also wondered how effective it really is...