You are viewing limited content. For full access, please sign in.

Question

Question

Document naming - Table with Upload File

asked on October 30, 2018

Hi, 

Has anyone had a Form that has a Table containing an Upload File column and a single line column that is being saved? If so, how do you save the two documents with the correct Index?

 

Right now, the uploads are named the same name but one has a (02) attached to the end. Can Forms do Indexing for columns or is this something I have to handle with Workflow (in which case, how?)?

 

Thanks!

1 0

Answer

SELECTED ANSWER
replied on October 30, 2018

As of Forms 10.2.1 you can reference specific rows of the table while saving to the repository. 

The Save to Repository Service Task now supports process variables that can retrieve values from a specific row in a table or a set in a collection for use in document name or template fields. For example, design a table with a "single line" field and a "file upload" field. If the table then has 2 rows of values, setting the file upload document name in the Save to Repository Service Task to {/dataset/Table_variable_name/Single_Line_variable_name[Row()]} will set the first file with with the first row's value and the second file with the second row's value. 

Just add [Row()] after the variable name but before the }

6 0
replied on October 30, 2018

Thank you so much!!

0 0
replied on June 21, 2021

Works in a collection too!

0 0

Replies

replied on April 30, 2019

Is there a way to get this to work with the path as well?  My table has the following columns:

  • Date
  • Single Line
  • Upload
  • Single Line (Year extracted from the Date column)
  • Single Line (Month extracted from the Date column)


My path statement is as follows:

\CCS\{/dataset/customer_lname}, {/dataset/customer_fname} - {/dataset/client_id}\Provider Reports\Progress Notes\{/dataset/provider_name}\{/dataset/progress_notes_table/progress_notes_year[Row()]}\{/dataset/progress_notes_table/progress_notes_month[Row()]}

My test data has 2 rows with 2 different dates, 3/26/2019 and 3/27/2019.

The folders created in my repository are named:

2019; 2019
    03; 03

My goal was to have the following folders:

2019
    03

 [Row()] added after the variable name does work for naming the document but I cannot get it to work to create the correct folder structure.

 

Thanks!

 

1 0
replied on November 30, 2020

I normally use a filing workflow to place the files within a repository after they are saved from forms. If you can get the information you need into metadata fields before saving, this should get your uploads filed where you need them.

0 0
replied on October 19, 2021

Hi, 

I have a question that goes along this thread (I think). I'm attempting to do the same thing a table with more than one row as shown here:

I want them to be 2 separate lines in my repository so I set up the Document Name as follows:

 

I even named the table and the single line variable the same as the example shown above in an attempt to get this to work.

Here's what I have in my repository:

it may be hard to see, but what it shows is the first table row (with the 63) followed by a semi colon, then the second table row (with the 8) followed by the rest of the dataset.

What I'm looking for and what I thought was shown in the thread above was that the first row of the table (with the 63) would be a file and the second row of the table ( with the 8) would be another file.

Am I way off base here?

0 0
replied on October 19, 2021

Hi Donnie-

My experience with the [ROW()] logic for indexing is that it works with an upload field specifically in the table/collection. The idea being that the ROW number that the upload comes from will be used for the associated metadata (haven't tried it in document name so not sure if that's supposed to work).

I don't see any upload fields in your table so I'm guess that you're using ROW in a way other than what the developers expect.

0 0
replied on October 20, 2021

Pieter,

Thanks for the info. I didn't realize that was only for uploads.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.