Hi All,We've migrated from one Appian instance into another. Part of the application functionality is uploading the file and storing the document id in the database.After migration we continue to use file upload and the new Appian instance will assign the document ids. Obviously in such scenario those document ids will repeat and we will end up having two records referring to two different files with the same id.The physical storage of the documents is resolved by integration with Filenet and it's not really a problem.The question that I have is if we can manipulate the sequence of assigning the document id so we can prevent duplicates (other than via a manual dummy process).<Appian on prem, v22.4>
Discussion posts and replies are publicly visible
There might be some file in the configuration that can help you achieve it but honestly not a big fan of this method. Why not create a utility process on the source environment that can store all the documents in a constant and then you deploy this constant to the target and run a utility to update the document IDs in the DB? Or any similar method with which you can just update the document IDs? Or you can also use uuid and get documentId from it.
Thanks a lot for your response. We do consider the utility process but not exactly as you've described. The problems is with the files that we will upload in the future in new environment not with the files from the source environment. Basically we need to adjust a sequence of document ids systemically or through the process.
I am not sure about the previous document Id and how to handle it. For the the future document uploads, how about you name the document with your records unique id or a combination of User-ID and Record timestamp and call the document by its Name? Not sure if I understood your question properly. please ignore if this doesn't sound relevant.