@Phil.E wrote:
Can you please explain what you mean by " ...the version appellation convention broke with the update"?
I thought this related to Keqing Song's @keqingsong recent blog post- perhaps it does not:
💪 Fixed: latestVersionNumber issue Well this was embarrassing. We fixed an issue where latestVersionNumber was returning the wrong version number for the latest document.
After the most recent update, a couple things happened in my Data Panel: some Saves of existing documents without name changes or unique Version names spawned new Version 1 documents; some Saves spawned Verision appellations on top of Versions appellations, such as "Example Document Name Version 4 Version 2". Frankly, time demands require me to decide which failures are worth, in the moment, documenting and reporting. Typically it is my want to create a quick Screencast of an error, then re-record a refined narrative to aid address by your team; however, with the number of aberrations as of late, that would amount to a significant portion of my time. The Screencast here is merely one such I didn't have budget to properly address or explore. I figure it's my responsibility as a non commercial user to do what I can to help squash bugs- at the moment I have time, as I've been waithing 40 minutes for Fusion to open a design. As soon as it cracks that nut, the moment will be past, as my client is concurrently pleading for product.
Screencast will be displayed here after you click Post.
61ac8ec0-811e-4ff2-a952-79d01b79afc9