I have a process, started through forms, that is utilizing collections to upload different types of attachments. I find that, for this form, collections work best, as tables do not allow for an attachment field, and there's no set number of files / attachments that are always going to be uploaded.
My problem is when it comes to saving these files in the repository. What is supposed to happen is that, based on the file type field above, the file in question should be renamed to that (ex., if type is "Booking Sheet," then the file should be renamed from whatever it was uploaded as to "Booking Sheet" once it is stored in the repository). I have found this more troublesome than expected though.
This isn't right because it just takes the different "types" of files, and combines their names. Example, if I have two files in that collection (one "Booking Sheet" and one "Case History") it renames both files on storage as "Booking Sheet; Case History" and "Booking Sheet; Case History (1)".
So then I thought I could have workflow handle it better. After reviewing some Answers posts, I came to the conclusion that this should work...
However, unless I'm doing this wrong - it doesn't work correctly either. It is just taking the first file in the collection and renaming everything that ("Booking Sheet," "Booking Sheet (1)".
Anyone else run into this and know the solution? It'd be greatly appreciated. Thank you!