Question

How to get Import Agent to use a token in folder path?

Laserfiche Import Agent

Updated April 25, 2023

asked on January 12, 2023 • Show version history

We use Import Agent and have about 50 different monitored folders and each year I have to go in and manually change the destination path because it sends the stuff to a folder with the year in the name.

I'd like to not forget to come in manually and update automation settings every year.

Things I've tried:

Generic Text an Number token called Year with a default of 2023 | folder ends up being named %(lfField_Year)

Change year in the path to %(Date#"yyyy"#) | IA doesn't process the document at all

Really can't think of much else on how to solve this problem.

Edit: Both the below answers are great workarounds and I already built a Workflow to handle this but I would still like a way to get Import Agent to use the current year as to not need to rely on other process when I feel that IA has to have some way of making this happen.

0 0

Replies

replied on January 12, 2023 • Show version history

Hi Timothy - so you're manually changing the Import Agent Destination Folders to something like: RepositoryName\Folder\2023? .... so each year you have to come in and change the year in each Profile?

If so - perhaps setting up a workflow to do the year folder part for you would be a good idea?

So the Import Agent Folder path would just go as far as the level above the year (e.g. RepositoryName\Folder\ in my example) - then a Workflow takes over (launched by a condition on document arrival) that creates a Folder (if it doesn't already exist) at that level called %(Date#"yyyy"#)... so the full path is now RepositoryName\Folder\(Date#"yyyy"#)... and moves the starting entry into that.

Would that work for you? You should be able to get away with one workflow covering all 50 incoming folders if designed correctly.

That being said; I agree that token formatting in Import Agent itself would be easier!

3 0

replied on January 12, 2023

A workflow is the solution. Instead of importing documents on such a manual/granular level, what I would do is import the documents to a single generic incoming documents folder, and then use a workflow to process/move accordingly. If you want them to always be in a year folder, it would be very easy to make the workflow use the current year in the path.

2 0

replied on April 25, 2023

I don't know if you are still looking for suggestions on this but one thing that might work is:

Within Windows, setup a mapped drive or subst drive letter to point to your active year. eg.
X: -> c:\import\Years\2023
(There is plently of documentation online about the "net use" command or the subst command).

Then setup your watched folder location to point to the X drive.

Then each year just change the mapping. You only have to do this once per year and it "flow through" for all your agent profiles.

The above is all "in theory" & I have not tested it.

0 0

You are not allowed to follow up in this post.

Question

Question

How to get Import Agent to use a token in folder path?

Replies

Sign in to reply to this post.