Hi Andrew, it works with cardnumber - but I agree borrowernumber would be nice, especially since I think we allow empty cardnumbers now.

Ahha! Cardnumber to report added in Bug 23206. Thanks!
As you say, though, it'd still be good to be able to use borrowernumber when cardnumber is null.

Hi,
I just wanted to express interest in this change. As Andrew mentioned in situations where the cardnumber field is null, it would be a great help to be able to use the borrowernumber instead.

I also wanted to mention one other thing, and apologies if this is out of scope of this bug, but some of the libraries I support have raised that if you use an alias for the cardnumber column in a report then the option to send the results to the batch patron modification tool does not come up. 

Example:

SELECT borrowers.cardnumber AS 'Student Number', borrowers.firstname AS 'First Name', borrowers.surname AS 'Second Name'
FROM borrowers

The results of a report like this would include a column of cardnumbers with the name "Student Number", and the option to send the results to be batch modified will not come up.


I don't know if it is alright to mention that on this specific bug or if there is anything that could be done so it would be possible to use aliases and still get the option to send report results to the batch patron modification tool, but I thought I'd chance it!

Hi Holly! Bug 23390 created a syntax for renaming columns without loosing your batch processing options. 
"This enhancement allows for renaming columns used to trigger batch modification actions in reports. Before this patch, a column had to be called 'itemnumber' to be sent from reports to batch modification. With this enhancement, you can specify `[[itemnumber| Koha_internal_id]]` to allow for a clearer name for the end-user and to allow translation of terms like 'itemnumber' while preserving the batch modification functionality."

Thanks Andrew, you're great!