Reassign Refnote callout to different refnote

OK. yeah I guess the match/mimic would be the right way. Because I wouldn't be needed to change every instance of 1-Paving to the same P-Division.

Clay, it looks like we were looking for a particular example.
I think for you example, you could just make a 1-Paving refnote to begin with, and then create the 4 P-division refnotes later or separately, but all within the refnote manager. Or you can make the Paving area as a concept area, but still have the P-division 4 refnotes in the refnote manager.

Either way, when it comes time to change them to the P-division versions, you would use the match object (about to be renamed to "Mimic" in the coming months) and match/mimic the original 1-Paving objects to the needed P-division ones.

I'm thinking through this and not seeing anything where it would need a whole new type of object. Or is there something you're thinking is missing from this workflow?

-Amanda

Did this ever progress?

I'm at a place in a project where it would be nice to be able to use a "placeholder" reference note callout just so I can start to wrap my head around what needs callouts but not to the point of any sort of known information. Having a placeholder that could then be reassigned to an final reference note at a future time would be helpful. It could be like a "concept" reference note.

EX:
1 - Paving

Reassigned to either of these:
P-101 - 8' Concrete Sidewalk
P-102 - 6' Concrete Sidewalk
P-201 - Concrete Paver
P-202 - Travertine Paver

Daniel,

In that case, is there a reason the placeholder refnote cannot just become the final item? It all really depends on the workflow, and we're happy to see examples, and how it can better respond. For instance I've certainly seen plans that have multiple callouts all stacked next to each with a single leader pointing to the item. At some point in the future we definitely will tackle this in some fashion, as it is an obvious need.
Another thing is to have the placeholder refnote item still be the correct object type. As in, if it is going to eventually be an Amenity, it should be initially placed as such, and not as a notation. But along those lines, I can certainly see it being handy to be able to "upgrade" a generic notation, to now be pointing to a placed amenity or chosen layer.

--J

Jeremiah,

No reason that is not an option. Just exploring a scenario where placeholder refnote callouts can be placed, then the data populated and link to the refnote updated once the descriptions have been fleshed out. In some circumstances, multiple callouts may need to reference the same refnote.

Thank you,

Daniel,

Just delete it and place a new one, or is there some reason that is not an option?

--J