#3855 - Named fields, and generally easier catalogue field relationship dereferencing
| Identifier | #3855 |
|---|---|
| Issue type | Feature request or suggestion |
| Title | Named fields, and generally easier catalogue field relationship dereferencing |
| Status | Open |
| Handling member | Deleted |
| Addon | catalogues |
| Description | Add ability to give each field its own name.
These names would be guaranteed globally-unique (i.e. if you used them for more than one field the system would give an error). You would not be able to enter a combination of only digits and underscores as the field names, to avoid ambiguity with IDs. These field names would influence the parameter names in Tempcode, so instead of... {FIELD_3} You might have... {FIELD_TITLE} An algorithm would map the names to valid Tempcode names. It would be cool to give a list of Tempcode field names as a 'preview action' when adding/editing a catalogue. The field names would also be usable for any Tempcode symbols that currently take a field ID. It would also be cool if the catalogue preview action gave you sample Tempcode for dereferencing any forward or backreference relationships that exist for your catalogue. |
| Steps to reproduce | |
| Funded? | No |
The system will post a comment when this issue is modified (e.g., status changes). To be notified of this, click "Enable comment notifications".


Comments
There have been no comments yet