Concatenating (1) to a document's name if it already exists in the target folder

SamuelHamann

Hi!

I'm trying to figure out a way to automatically add (1), (2), etc… to a document's name when adding a document to ContentServer using the REST API. Ex: If "name.pdf" already exists, change the name to "name (1).pdf" or something similar

I'm currently recursively calling the /validation/nodes/names/ route to check for collisions with "name.pdf", "name (1).pdf" and so on. I'll like to know if there's a setting that does something similar automatically so that I can simply insert an object without having to think about it.

Using CS 23.3

Thanks! 🙂

appuq

in case you do not know this REST API finally becomes Oscript and Oscript API has the methods available, but not many people know how to work in Oscript or its programming.

Your options are in the order of simplicity.

1. Check the container before adding using pure rest api methods
2. Check the container by writing a Live Report and exposing it as a WR. All WR's have a way of masquerading as a REST API. Check developer.opentext.com for examples. I haven't checked anything recent but my guess is you still need a WR Wrapper to call a LR.
3. If Searching and indexing can be believed in your system one can quickly call a search API to see if the object exists although you may run into false positives that is the caller does not have rights to the object the search API will get filtered.
4. Here is a one liner using AnswerModules def node= docman.getNodeByNameFast(containerid, "appu.txt", true, true, true, true, true, true, true) which is like asking do you have that named node in your container. The code is in Groovy and AM relies on CWS oscript code and OT's REST api code.
5. using WR tag one can do this [LL_REPTAG_'1214136' NODEACTION:CREATE:DOC:1213580:appu.txt /] and in my attempt I got appu.txt,appu.txt2,appu.txt3 in subsequent runs without using UNIQUEONLY flag so it may be easy to do your RESTAPI by doing a WR masquerading as REST…