Document ID changed when deploying a document to a higher environment

RE: Document ID changed when deploying a document to a higher environment

David Jimenez — Thu, 26 Sep 2024 07:27:14 GMT

Yes, this is the expected behavior... Because the document instance is different in the new environment. Reference the document instead of its ID and it will work.

RE: Document ID changed when deploying a document to a higher environment

Soma — Thu, 26 Sep 2024 07:26:10 GMT

It should work when you have the document object in document type constant.

RE: Document ID changed when deploying a document to a higher environment

Stefan Helzle — Thu, 26 Sep 2024 06:27:13 GMT

That constant, is that a number? If yes, change it to the type "Document". It will then reference the UUID and become stable across deployments.

RE: Document ID changed when deploying a document to a higher environment

Mike Schmitt — Wed, 25 Sep 2024 12:28:55 GMT

Constants (of "document" type) which point to a specific document, should still point to the correct document after deployment to another environment, regardless of the fact that the deployed copy of the document will have a new/different underlying DocId. If you're seeing something other than this, then you might need to open a support case with Appian Support.

RE: Document ID changed when deploying a document to a higher environment

Kumar Agniwesh — Wed, 25 Sep 2024 12:10:49 GMT

rule of thumb, IDs changes from one environment to another environment. UUID remain same across environment.

RE: Document ID changed when deploying a document to a higher environment

Yogi Patel — Wed, 25 Sep 2024 11:59:00 GMT

Yes, replaced the document ID with a document in constant.

Thanks for your reply.

RE: Document ID changed when deploying a document to a higher environment

Shubham Aware — Wed, 25 Sep 2024 11:36:29 GMT

Yogi Patel
This is expected behaviour to maintain environment isolation and prevent conflicts.
I would recommend you put that document into a constant and use that constant.