@Luis It's a defect. I ran into it a couple of years ago. The workaround is to add your custom field as a column on the transaction line.

Thank you!