search

OfficeDev / office-js-docs-reference

Microsoft Office JavaScript API Reference
https://learn.microsoft.com/javascript/api/overview
MIT License
118 stars 67 forks source link

Unclear on how a unique 'add-in' is determined #991

Closed theboyknowsclass closed 3 years ago

theboyknowsclass commented 3 years ago

in the docs it's stated as -> "The settings created by using the methods of the Settings object are saved per add-in and per document. That is, they are available only to the add-in that created them, and only from the document in which they are saved."

How is this determined? e.g. i the same manifest for the addin used in both Excel Desktop (windows) and Online. However if i create a document in one platform, it is not guaranteed that the document settings can be read in Desktop.

Is this intentional behavior?

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

AlexJerabek commented 3 years ago

Thanks for the question @theboyknowsclass.

@Rick-Kirkham, can you please provide clarification?

Rick-Kirkham commented 3 years ago

@theboyknowsclass What is the source of your statement that "if i create a document in one platform, it is not guaranteed that the document settings can be read in Desktop"?

theboyknowsclass commented 3 years ago

hi @Rick-Kirkham @AlexJerabek thanks for the quick response (as always)

we have an add-in where we use the same manifest file on online and windows desktop - i'm testing in Word currently, but have seen the same behaviour in Excel and Powerpoint

when i create a document and add metadata using the settings API in the online version. this does not appear to be readable in the desktop version. (if i unzip and edit the file i can see it is added), and opening it back online reads fine

this seems to be related to the specific desktop version as my colleagues on the latest build do not see it - i am using 2103, they are on 2105.

was there any bugs fixed in this period affecting this?

Rick-Kirkham commented 3 years ago

@theboyknowsclass Yes. There were bug fixes. One of them was connected with this issue 1585 in the office-js repo. I suspect that you are seeing a variation of this same bug. So, the fix for you is to update to 2105 or later.

At any rate, since it is not happening on recent versions and the documentation seems to be correct, I'll close this for now. You can still add comments and request that it be reopened.