Revit bug in IndependentTag TagText with link model

Revit bug in IndependentTag TagText with link model

BIM.Frankliang
Collaborator Collaborator
601 Views
1 Reply
Message 1 of 2

Revit bug in IndependentTag TagText with link model

BIM.Frankliang
Collaborator
Collaborator

Dear Friends,

         I found an interesting thing that I could't get IndependentTag TagText when door in Link doc and IndependentTag in main doc. I have attached zip file below:

 

        1. The red rectangle shows door of link model (image 1)

        2. The blue circle shows door IndependentTag which associated with door of link model (image 1)

        3. RevitLookup shows that the IndependentTag TagText is Internal Exception (image 2)

 

        That is strange, I could see TagText in Revit but I could't get.

        Wish it can be improved

 

        The attachments:

        a.  2.rvt(main model)

        b.  1.rvt(link model)

        c.   image 1

        d.   image 2

 

Best Regards

Frank Liang

TJAD BIM Software Dev Lead

0 Likes
Accepted solutions (1)
602 Views
1 Reply
Reply (1)
Message 2 of 2

JimJia
Alumni
Alumni
Accepted solution

Dear Frank, 


I am sorry to say that I can reproduce this issue as well.


I submitted the issue list item REVIT-145153 [IndependentTag.TagText getter throw exception when it is tagging to element of linked file] on your behalf for the issue you find, as this issue requires 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 us with additional information at any time quoting this issue list item number.


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


This issue needs to be assessed by our engineering team, and prioritized against all of the other change requests that are outstanding. As a result 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 Change Requests. We do understand that this will cause you delays and affect your development planning, and we appreciate your cooperation and patience.

 

 


Jim Jia
Autodesk Forge Evangelist
https://forge.autodesk.com
Developer Technical Services
Autodesk Developer Network
Email: Jim.Jia@autodesk.com
0 Likes