Major A document initially created in Nuxeo then push to Frame.io, then gets versioned in Frame.io (e.g. using stack versioning), does not get versioned in Nuxeo when it is pushed back to Nuxeo, a new document is created instead.
How to reproduce:
- in Nuxeo, bind a Folder document to a Frame.io project
- in Nuxeo, create a Picture document (see document Come on do something JIRA.png in screenshot below)
- in Nuxeo, push the Picture document to Frame.io
- in Frame.io, upload a new file in the project used above (see `Come on do something JIRA-v2.png` in screenshot)
- in Frame.io, create a version (using e.g. the stack versioning feature) with the uploaded file above (see screenshot below)
- in Frame.io, publish the asset to Nuxeo
Expected result: the document initially created in Nuxeo gets unlocked and a version is added to it as mentioned in our documentation https://doc.nuxeo.com/nxdoc/2021/nuxeo-frameio/#version-13-use-case-push-assets-from-nuxeo-to-frameio
Actual result: the document initially created in Nuxeo does not get unlocked (see screenshot below) and a new document gets created instead of adding a version to the doucment (see screenshot below)
The fact that the filename for the version is different than the original filename could be the cause.
