You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the latest "Word16" template PlantUML_Template_v35.dotm in Microsoft 365 Word I'm getting a VBA error when trying to open the Preferences on the PlantUML tab:
Run-time error '457':
This key is already associated with an element of this collection
As usual the message is "very helpful", not specifying which key of which collection is the culprit...
Any ideas what conflict might be happening here and how to fix it?
The text was updated successfully, but these errors were encountered:
I get the same error but it seems to have something to do with OneDrive for me.
If I put the Word document (so not the template but the working document) file in OneDrive I get this error.
But if I put the file anywhere else it works fine.
Thanks for the pointer @LilMouse, indeed I saw the problem with a SharePoint document, and when I download the file to a not-OneDrive/Sharepoint-"managed" location I can access the setting. This is an unfortunate limitation, because I'm not sure settings are "per-file", or general "per-Word-installation". Possibly there is a properties name conflict between the plantUML "per-file" option and some SharePoint/OneDrive option that happens to have the same name.
Anyway, now that I was again able to access them, I note that the options are very limited (VectorGraphics on/off, and FTP settings which I don't need/see the use of).
Since I'm not sure about the stability of including big diagrams directly in a big Word document, I'll probably opt for generating the diagrams externally from separately stored source files and including the images in the Word doc.
Hi,
With the latest "Word16" template PlantUML_Template_v35.dotm in Microsoft 365 Word I'm getting a VBA error when trying to open the Preferences on the PlantUML tab:
As usual the message is "very helpful", not specifying which key of which collection is the culprit...
Any ideas what conflict might be happening here and how to fix it?
The text was updated successfully, but these errors were encountered: