View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
13458 | Feature requests | Other | public | 2018-03-07 17:45 | 2018-03-07 17:45 |
Reporter | tbart | Assigned To | |||
Priority | none | Severity | feature | ||
Status | new | Resolution | open | ||
Summary | 13458: Setting exportable, read-only data field | ||||
Description | This is a mix of a feature request and/or a question.. If the question cannot be answered, consider it a feature request ;-) I'd like to be able to have an added exportable field that could be shown on queXF PDF printouts. Let's call it eventID. I tried making an input field readonly with JS and setting a default value, which works perfectly for the online view, but the exported PDF prints the JS instead of interpreting in. I would not be able to scan & interpret the numbers anyway, as ICR does not quite work out with queXF (at least Adam Zammit of queXF more or less told me not to use ICR because it does not really work that well). As the surveys are cloned, the PDFs are identical (apart from the barcode). I'd just need to show the eventID on the PDF and also have it exportable in the resultset. Like a global property of a survey like the fax number, but in such a way that it can also be shown in the PDF (so people know which eventID this very PDF is meant for - once printed it is impossible to get this info). When (mass) exporting answers, I need to know which answers have been given for a certain eventID. | ||||
Tags | No tags attached. | ||||
Bug heat | 0 | ||||
Story point estimate | |||||
Users affected % | |||||
Date Modified | Username | Field | Change |
---|---|---|---|
2018-03-07 17:45 | tbart | New Issue |