Keyed notes lose number

[Anonymous]

I use revit's "smart" keyed notes. I tag the element, select the appropriate key value from the .txt file. The correct number pops up in the keyed note, and the text shows on the sheet view. everything works great, just as expected!

then, I go to work on a different part of the model, and when i come back, it looks like this (see attached photos)

-the keyed note txt file is unchanged.

-the model elements have not changed or moved.

-the keyed note, in plan view, has not moved.

this happens very often for me, when it does i have noted the following, (among other instances, not limited to those listed below)

-the workset of the model elements has changed

-the visibility settings changed (i.e. keyed note hosted to a conduit loses its # when i turned off mechanical equipment in the VG)

[amorap]

Hello from Spain MFARB

A key note is a tag. And like other else tag, it is linked to an object.
If your object gets changed, or its vissibility, probably the tag / keynote will be affected.

Have you tried with different type of keynotes, like by  material or by user?
Have you tried to lock the objects / worksets before tagging with keynotes?

Regards

[barthbradley]

Are all these tags shown in your screenshot actually of the same family: “Keynote Tags”, and is your “Numbering Method” (under “Keynote Settings”) set to “By sheet”?    

[Jhallock!]

Just ran into this issue with a 2015 revit model that we upgraded to 2017 revit (I'm MEP but does that really even matter anymore?).  Was there ever a solution to this?

We ended up Cutting and then pasting our Keyed notes back in.  Seams to have worked for now but from what I have read on these forums I don't have much confidence in ever using the Revit Keyed Notes with .txt file again.

Was there ever a solution to this?

[Anonymous]

i was unable to find a solution on this particular project. i have since resorted to using "dumb" keyed notes (no txt file)

[Anonymous]

at our company, we are limited to user keyed notes, because of the nature of our work. i agree it seems to be an issue with visibility, i am searching for a solution, fix, or work around without locking every object i note

[Anonymous]

yes and yes, thats why i was so frustrated. youd think it would work consistently and error consistently. 

[Jhallock!]

Sometimes the best way to deal with an Autodesk product is to go with the dumb solution, or a work around. As this forum has proven (given the 6 months it's sat with no answer) they don't care to help sometimes, and have never offered a discount when it's time to re-up that $$$$$ subscription (no matter how much time issues like this one may take to correct).

[Anonymous]

I found no way to prevent this from happening, nor did I figure out why it was happening, nor did this ever happen to me again. However I found out how to fix it. Maybe it will lead to a solution. 

Go into the view, in the properties window, uncheck and re-check the "crop view" box, hit apply.

This "bandaid" of a solution makes me think its just a glitch. the screen recording attached is NOT the project this phenomenon occured. it only illustrates the way I was able to fix it.

[aaronXXYH5]

I don't know where the glitch came from but this hack worked.  Thanks so much for posting this.

[Anonymous]

No way! I'm glad it wasnt just me!!

[JohnW-OPM]

2021 and this is STILL an issue. The tip above still works to "fix" it. 

[Anonymous]

thats wild that it is still an issue. glad the quick fix worked for you too though

[sdiazE5ESC]

This is the way!

[macoburn]

This was a life saver I just tried it in Revit 2024 and it worked like a charm. I suspect the issue may have come from when I copied a previous model and put it on shared coordinates the tags got confused? Thank you for posting!