Keynote Legends and Keynotes not Updating 2018.3

In Revit 2018.3.2.7 I am seeing and getting reports that keynote legends are not updating to show the current state of keynote tags visible in views. The existing workaround to force a refresh by turning on/off the Annotation Crop Boundary works but is entirely impractical to expect a team to open every sheet and do that task for each and every view on a sheet.

This past Knowledge Network post seems relevant. A portion of the text at that article suggests...

Workaround:
There are a few ways you could work around this behavior, and the best method will vary depending on the model geometry and number of affected tags. Here are a few options:

Temporary fixes (these will restore the display keynote tags, but future view changes will clear them again): 
Temporarily adjust the location of the Cut Plane so that is above the affected elements (this will restore the value to the tags) and then restore the original cut plane location. Note: Some customers have noted that for views with dependent views, this process is required:

1. Open the parent view and adjust the cut plane upward.
2. open all sheets containing dependent views belonging to this parent view to refresh the keynote tags.
3. move the cut plane back to its original position in the parent view.

(Note: this may not work for some elements such as Duct; in that case, see the Non-temporary fix below.) Recreate the affected tags manually.

Non-temporary fix (This will prevent future changes to the view from clearing the keynote tag): Adjust view or elements so that the cut plane is above the affected elements. (This could be done with a Plan Region.)

We really need this fixed ASAP!!

Dept. of Reviteristics - A Legend isn't?

Language is hard at times. The use of the same words in the context of Revit for different tasks can be confusing. Take for example the Legend feature which is a specific type of view that can contain symbolic representation of content and text as well as dimensions. These legends can also be placed on multiple views whereas most other view types cannot.

Consider then the Color Scheme Legend, it is a legend in the conventional architectural language/usage but in the context of Revit and views it is NOT. So imagine the possible confusion for a new user when we use the same word interchangeably for different purposes.

A color scheme legend is not a view, it is annotation that is placed in a view. It/they are managed via the Settings menu > Color Fill Schemes. These are only available if you've chosen to apply a color fill scheme to a view. They are intended to provide a way to discern what each color is meant to represent.

When working with new users (or seasoned even) be vigilant as we use words and their meaning and how things that may seem obvious may in fact be confusing.

Legends - Face Based Families

Short and sweet...they don't mix unfortunately. When they created the capability they either missed the fact that legends didn't support them or they decided the feature was more important than them working in Legends to hold them back. I'm glad we have FBF's. I'm not glad about or happy with the Legend feature set.

Legends are compromised by (at a minimum):

- Inability to transfer them between project files.
- Face Based Families do not work in them
- Tags cannot identify the elements displayed in them
- A sheet includes a legend in its "Scale" display evaluation.

An element in a Legend view should be "equal" to a real element but not affect quantity. That means tagging as well as dimensioning. The current implementation sacrifices bIm for graphic representation as well as ease and consistency of use.