Replace existing documents

RE: Replace existing documents

Kumar Agniwesh — Wed, 09 Oct 2024 11:46:32 GMT

I have the same code as what you have. I was asking you to check the Folder security in which the original document is stored. I am guessing users would need at least editor access to the folder in which doc is stored and also editor access on the original document

RE: Replace existing documents

Tomislav Fuček — Wed, 09 Oct 2024 06:07:53 GMT

Hi Kumar,

may I ask you for a code snippet? Thanks.

RE: Replace existing documents

Kumar Agniwesh — Tue, 08 Oct 2024 21:17:36 GMT

I just tried and worked fine for me, Only thing which you can check is if the users have edit permission to the folder inside which you have your original file

RE: Replace existing documents

Stefan Helzle — Tue, 08 Oct 2024 11:40:29 GMT

Not sure. I do not remember whether I have aver tried that. I suggest to implement a tiny simplified test.

RE: Replace existing documents

Tomislav Fuček — Tue, 08 Oct 2024 10:38:50 GMT

Hi Stefan,

Yes, that would be a viable workaround, and we do have a similar document representation in the database. However, I was aiming for a more elegant solution, as it seemed from the documentation and previous discussions that we could simply replace or create a new version of the already existing files using the a!fileUploadField component.

I’m just curious as to why this approach isn’t working as expected.

RE: Replace existing documents

Stefan Helzle — Tue, 08 Oct 2024 10:32:22 GMT

In my world, I manage all documents in a database table and just store the file itself in some folder. Then, "replacing" means to upload a new file, add a new record to the table while maintaining relevant relations, and then delete both, the old record and the old file.