Who would benefit? |
Anyone wishing to programmatically examine the values of specific/all fields |
What impact would it make? |
Improved programmed access to the local fields and their values |
How should it work? |
Add a new function FIELDS() which returns a JSON object of field values indexed by their field type ids An optional parameter can contain comma separated list of fields to collect. When omitted it implies all fields. |
Why is it needed? |
FIELDVALUES() returns just a linear list of values but doesn't identify the field type id of each value and the order is not defined either. |