FileUploadField

RE: FileUploadField

umaisa khan — Tue, 08 Feb 2022 19:58:19 GMT

its simple. Declare a local variable . In value and saveinto parameters pass that local variable. At last in submit button save local variable into rule input. Done

RE: FileUploadField

sravanis — Mon, 07 Aug 2017 10:46:56 GMT

Hi namratak356,

Go through the below link, it may be helps you.
docs.appian.com/.../File_Upload_Component.html

thanks,
sravanis.

RE: FileUploadField

sonalk — Fri, 04 Aug 2017 02:47:51 GMT

Hi namratak356 ,

How did you resolve the above issue? Can you please guide me.

Thanks,
Sonal

RE: FileUploadField

Pitla Mahesh — Tue, 25 Jul 2017 13:49:36 GMT

If I am not wrong the ri variable which we are using to capture the document Id should be of type document and in further usage we can use integer type to save it and this file upload supports only in start forms and tasks forms.

RE: FileUploadField

sergeiz — Wed, 21 Jun 2017 12:32:58 GMT

> 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.

RE: FileUploadField

Rama Thummala — Wed, 21 Jun 2017 12:27:26 GMT

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.

RE: FileUploadField

sergeiz — Wed, 21 Jun 2017 12:16:42 GMT

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

RE: FileUploadField

Josh — Wed, 21 Jun 2017 12:12:02 GMT

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

RE: FileUploadField

sergeiz — Wed, 21 Jun 2017 12:09:26 GMT

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.

RE: FileUploadField

Shivam Gupta — Wed, 21 Jun 2017 10:15:06 GMT

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

Otherwise I have tested this is running perfectly fine.

RE: FileUploadField

namratak356 — Wed, 21 Jun 2017 05:51:45 GMT

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

RE: FileUploadField

Jacob Grafenstein — Tue, 20 Jun 2017 17:21:58 GMT

I think the previously submitted replies are correct, but I'd just like to provide a little clarification on the matter. When you upload a document inside of a SAIL form, Appian generates a temporary document ID. It isn't until the form is submitted that Appian grants an uploaded document a permanent ID that can be used to reference the document. So, if you are attempting to reference the document ID inside of the foreach function, you'll run into issues because Appian will be attempting to look for a document that has not yet been persisted in the system. Consider chaining two forms together in your process model to reference a document ID that has been uploaded.

RE: FileUploadField

abhinavg712 — Tue, 20 Jun 2017 12:49:23 GMT

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

RE: FileUploadField

Rama Thummala — Tue, 20 Jun 2017 11:53:45 GMT

Hi namratak356 ,

Can you please share your code snippet here?
I am suspecting that the issue due to referencing the document or it's id (inside forEach() )before submitting the form.Make sure the uploaded document should be submitted to the process model before trying to access it.