When we use the a!fileUploadField, we're saving the document Id to a CDT var

nickh647 over 8 years ago

When we use the a!fileUploadField, we're saving the document Id to a CDT variable.
The document is uploaded, but the document ID generated on the file upload does not match the document ID in the knowledge center (off by 1), so we're unable to use the ID stored in the CDT to access the document.

Has anyone run into this before, and how do you go about storing the correct ID into a CDT variable?

Discussion posts and replies are publicly visible

Parents

0 marco.molteni
Appian Employee
over 8 years ago

Hi Nick,
some more details to the correct answer of Akshaya: as explained in the documentation (scroll to the notes : forum.appian.com/.../SAIL_Components.html the Document object is updated with the final ID after the form is submitted but integer values that contain the ID are not updated even if they are in a CDT. From the upload form pass the Document variable to the process and not the id, you can add a Script Task with an output node that writes the Document variable in the field (Integer) of your CDT to store the final ID. This works with arrays of documents too.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 marco.molteni
Appian Employee
over 8 years ago

Hi Nick,
some more details to the correct answer of Akshaya: as explained in the documentation (scroll to the notes : forum.appian.com/.../SAIL_Components.html the Document object is updated with the final ID after the form is submitted but integer values that contain the ID are not updated even if they are in a CDT. From the upload form pass the Document variable to the process and not the id, you can add a Script Task with an output node that writes the Document variable in the field (Integer) of your CDT to store the final ID. This works with arrays of documents too.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data