| Summary: | MULTI choices in report dropdowns | ||
|---|---|---|---|
| Product: | Koha | Reporter: | Christopher Brannon <cbrannon> |
| Component: | Reports | Assignee: | Galen Charlton <gmcharlt> |
| Status: | RESOLVED DUPLICATE | QA Contact: | Testopia <testopia> |
| Severity: | enhancement | ||
| Priority: | P5 - low | CC: | andrew, blawlor, caroline.cyr-la-rose, hebah |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | All | ||
| Change sponsored?: | --- | Patch complexity: | --- |
| Documentation contact: | Documentation submission: | ||
| Text to go in the release notes: | Version(s) released in: | ||
| Circulation function: | |||
Hi Christopher, I think the problem is in how to make this work with the SQL query. <<branches>> is usually used with =, multi could be used with 'in (....)', but not sure how how to make an 'all' work in a good way. Great! Half way there. Now, if we could repeat the process of bug 23389 and give the option of <<branch|branches:multi>> where that would allow you to select several branches of your choosing, that would be fantastic. *** Bug 24568 has been marked as a duplicate of this bug. *** This would be a great addition to reporting and a request I've been seeing a lot of recently in reports. (In reply to Katrin Fischer from comment #1) > Hi Christopher, I think the problem is in how to make this work with the SQL > query. <<branches>> is usually used with =, multi could be used with 'in > (....)', but not sure how how to make an 'all' work in a good way. It seems like if you could do something like: homebranch IN (<<Branch|branches:all>>) If Koha could detect the parameter was in an IN statement, maybe it could use a dropdown that allows multiple selections. And if the all selection is made, all the selections would be in the IN statement. There would just need to be some logic to handle what to do if ALL was one of the multiple selections so it doesn't create strange results. |
When adding choices like <<branches>> to a report, it would be great if parameter could be added to the choice where ALL could be a choice at the top of the list. Maybe something like <<branches{ALL}>>. Similarly, it would be great if MULTI could also be a parameter, where the user could select several items from the list, like <<branches{MULTI}>>. Christopher