FileUploadField

namratak356 are you trying to look for temporary document id in your code as Appian generates a temp doc/content ID initially before the document is being persisted in the DMS

Here is the code snippet
-------------------------------------------------------------------------------
a!sectionLayout(
contents:{
a!fileUploadField(
label: "Supporting Documents:",
target: cons!REQUEST_DOC_FOLDER,
value: ri!documentIds,
saveInto: {
ri!documentIds

}
)
}
)
-----------------------------------------------------------------------
ri!documentIds-->Number(Integer)Array
When I am submitting the form it is giving error:
Could not display interface. Please check definition and inputs.
Interface Definition: Expression evaluation error at function a!fileUploadField [line 154]: Error in a!forEach() expression during iteration 1: Expression evaluation error at function fn!content_appian_internal [line 12]: Error evaluating function fn!content_appian_internal : Invalid Content ID

Here is the code snippet
-------------------------------------------------------------------------------
a!sectionLayout(
contents:{
a!fileUploadField(
label: "Supporting Documents:",
target: cons!REQUEST_DOC_FOLDER,
value: ri!documentIds,
saveInto: {
ri!documentIds

}
)
}
)
-----------------------------------------------------------------------
ri!documentIds-->Number(Integer)Array
When I am submitting the form it is giving error:
Could not display interface. Please check definition and inputs.
Interface Definition: Expression evaluation error at function a!fileUploadField [line 154]: Error in a!forEach() expression during iteration 1: Expression evaluation error at function fn!content_appian_internal [line 12]: Error evaluating function fn!content_appian_internal : Invalid Content ID

where did you have used forEach expression . Can you brief me.

 

Otherwise I have tested this is running perfectly fine.

Why do you save it into array? FileUploadField works with one file.

forum.appian.com/.../SAIL_Components.html

The permanent document id will be available when the user input task is finished. Variables of Document type will be update and you can use them. Integers are not updated and produce errors.

File upload fields support multiple files in 17.2, which is why you see an array in the example above.

docs.appian.com/.../File_Upload_Component.html

Ok. In this case the array should contain Document type, not Numbers. And they will be updated with the permanent file ids.

The type is not an issue...Type casting will happen automatically here..But the input that is mapped to process acps or pvs must be of type document, then only the document(s) will go to KC and permanent ids gets generated.

> the input that is mapped to process acps or pvs must be of type document

AC must be of type Document. Then you can save them into pvs of type integer.