[Feature Request] Custom field option "allow multiple" #5032
Unanswered
pm64
asked this question in
Feature Requests
Replies: 1 comment
-
I'm encountering this as well. My use case is that I have a list of transactions from my bank statements and want to match those to documents in my paperless. The transactions have an ID, and I want to put that ID in a custom field. I've messed up yesterday and transferred a wrong amount, and sent a second transaction today. Now I have two transactions that should be matched to the document as well. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Description
In organizing my documents, I had a scenario where I wanted the value of a custom field to be a list of dates.
I could have used the "text" data type -- but then when searching for dates, the format of the date in my search query would need to match the format used in the field value.
It then occurred to me that if individual custom fields had an "allow multiple" setting, which would lift the constraint of only being able to use the field once per document, we'd effectively have multi-value custom fields.
Aside from using the "text" data type, another workaround is to spread the values across multiple custom fields (for example, "MyDate0", "MyDate1", etc). This solves the search problem, but feels uncomfortable to me. Maybe others feel differently.
In any case, I'm wondering if an enhancement along these lines could have value.
Other
No response
Beta Was this translation helpful? Give feedback.
All reactions