Another Revit 2018 Bug? - IndependentTag.Create with families loaded via the API

[matthew_taylor]

Hello All,

I can tell ya, I'm not enjoying the Revit 2018 ride so far.

I've got an issue with the new IndependentTag.Create static method.

See  the attached zip with

• 2 commands (with accompanying addin manifest).
  • 1 - Loads family symbol, then (tries to) create a tag for the picked floor slab. Fails at IndependentTag.Create .
  • 2 - (requires *manual* load of family first) successfully creates a tag for the picked floor slab. Succeeds.
• A floor slab tag family, fresh from the UK Metric family library.
• A test model. Created without a template (metric), with a simple floor slab added.

All API loaded FamilySymbols are activated.

If I'm missing something, let me know. Otherwise, please log and pass along to the development team.

[matthew_taylor]

Same issue with structural columns and their respective tags.

[jeremytammik]

Dear Matt,

Thank you for your report, precise description and reproducible case. They help a lot!

I am very sorry to hear the bad news and understand your frustration.

Your reports get well-deserved prioritised treatment, in case that helps.

I logged the issue REVIT-114468 [IndependentTag.Create fails for API-loaded family -- 13018698] with our development team for this on your behalf as it requires further exploration and possibly a modification to our software. Please make a note of this number for future reference.

You are welcome to request an update on the status of this issue or to provide additional information on it at any time quoting this change request number.

This issue is important to me. What can I do to help?

This issue needs to be assessed by our engineering team, and prioritised against all other outstanding change requests. Any information that you can provide to influence this assessment will help. Please provide the following where possible:

• Impact on your application and/or your development.
• The number of users affected.
• The potential revenue impact to you.
• The potential revenue impact to Autodesk.
• Realistic timescale over which a fix would help you.
• In the case of a request for a new feature or a feature enhancement, please also provide detailed Use cases for the workflows that this change would address.

This information is extremely important. Our engineering team have limited resources, and so must focus their efforts on the highest impact items. We do understand that this will cause you delays and affect your development planning, and we appreciate your cooperation and patience.

Cheers,

Jeremy

[matthew_taylor]

Hi Jeremy,

Thanks for reporting the issue, and your reply in general.

Having a well established template negates the issue to some extent, but not all of our company uses the same template.

I have trapped the exception and popped up an alert to advise the user to manually load a family. Not the end of the world.

Just another testing issue that sucks up a few hours of my (already busy) time, and slows down the switch to 2018.

Anyway, thanks again.

[matthew_taylor]

Noted in comments below https://forums.autodesk.com/t5/revit-ideas/known-bug-list/idc-p/7119086#M8547.