A recent change in NotePlan permits use of AI to update Property structures. I think that the following are all true: The need to update property structures for notes of the same “kind” will inevitably arise. For example, after creating 30 notes with Property Set “Books Version 1” a need to add a new property will be identified with book 31. Then another new requirement will be identified with book 43, and still another with book 75. A proliferation of structures for the same basic “kinds” of information will create confusion and interfere with the efficiency of Eduard’s planned table views. Updating dozens of notes, one at a time, with new structure will be painful. Recommendation: a. NotePlan employ “named property sets” - each with a version number. Examples: “books”, “projects”, “clients”, “delivery orders”, “bug reports”, “feature requests”, “bird sightings”, etc. b. When a structural change to a “named property set” is made, all notes employing that property set should be updated - perhaps by using AI to do so. The version number should also be updated.