I never noticed this before, but I seem to have issues now if an item being saved by forms matches an existing document. It won't simply rename it as (2) or (3), etc.
Any way I can fix this without have to add a unique identifier?
I never noticed this before, but I seem to have issues now if an item being saved by forms matches an existing document. It won't simply rename it as (2) or (3), etc.
Any way I can fix this without have to add a unique identifier?
I only ever save forms (and all other documents) to an "Incoming Documents" folder, which triggers a workflow that handles and organizes all incoming documents. This avoids naming conflict situations entirely, because the "Move Entry" activity will automatically rename an entry if an entry with the same name already exists in the target location.
That's a great work around.
Thanks.
I've used this approach in many cases, but another approach I use is to include the Forms instance and/or submission id in the entry naming.
This value will be unique to each instance of the process; submission id is unique to each form/task submission.
I have done this before as a solution, but it is not what the company preference is. Since Workflow auto renames, I was hoping I was missing something and Forms would do the same, but I'm guessing that is not an option. It is a shame.
Thanks for your suggestion.
Forms will also follow the profile options for the designated account; the issue is that the default is to prompt the user, and Forms can't be prompted.
I'd recommend creating a separate profile/account to distinguish which ones are using non-default settings, but you can temporarily give the desired account a license, log into the repository as that user, then change the name conflict options from "always prompt" to "automatically rename"
Once that is done/saved, you can remove the license, and any Forms processes using that profile will use the auto-renaming option. You can do the same with other settings like automatically generating pages for PDFs and such.
Believe it or not, I did the setting changes a few months ago. I'm still having the issue.
For now, I am relying on the workflow, but it could be problematic if I have to make workflows for such a routine task.
What version of Forms are you running? I tested it before making that post and confirmed that it was working as expected.