Alfresco Collaboration Connector for Microsoft 365 - End Editing fails
Description
Current behaviour
When using O365 connector, "End editing" action fails, raising an error on the OOI side.
It seems that this issue wasn't there a couple of weeks ago… So, it can be related to some changes from Microsoft ... (APIs, SDK, ?)
Here is a StackOverflow thread referring to the same error that we can see in the logs : https://stackoverflow.com/questions/66075502/graphapi-com-microsoft-graph-core-clientexception-caused-by-java-lang-illegalst
Root cause could be the same : core library implementation needing an upgrade to fit with the newest MS API / SDK.
Expected behavior
When users finish editing with MS 365, initiator of the coauthoring process makes end to the edition through the dedicated ADW Action "End Editing". Then, a new version (minor / major) is created in ACS according to users modifications
Steps to reproduce the issue
Edit a Microsoft Office document via the 365 connector and ADW
Make some changes within the content of the document
Go back to ADW and "End editing" through the related action
Error is raised and new version cannot be created + document still locked...
Please see the attachment for more details.
Environment
Testcase ID
Activity
I’ve confirmed that OOI 1.1 resolves the issue, and is going out in an updated ADP (version 6.1.6) today. Thanks again for the quick response and attention on this issue!
ADP environment to be upgraded with latest version soon.
Thanks for your input!
for now I’ll put this Jira in “Verify” as this should be fixed in the latest version of OOI 1.1. Once ADP is upgraded please verify this bug, once we are good, we can close it. Thanks for bringing it to our attention.
Hi ,
I’m using our internal SE tool named ADP (Alfresco Demo Platform) maintained by . After a quick check on ADP documentation, it seems that the version 1.0 is used on the OOI side.
: up to you now
What version of O365 (OOI) are you using?
The issues caused by the referenced stackoverflow site were known in V1.0 and are fixed in v1.1 and the work was done as part of
See