You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The API GET /records call today returns the underlying values of Grist cells, for example:
Numeric values are returned as numbers in the JSON response
Date values (like '2024-03-04) are returned as numbers, seconds since epoch, e.g. 1709510400`.
Reference values are returned as row IDs
Sometimes it's helpful to get values as a user would see them, i.e. the display values. For example, display values are what gets exported in CSV or Excel exports. For example:
Numeric values with formatting, like $1,000.00 or 37%
Date values with formatting, like 2024-03-04 or March 3, 2024
Reference values as their corresponding display value (e.g. name of contact rather than row ID of contact)
Proposal is to add an optional query parameter includeDisplay=1 to GET /records call. When set to a true value, the response would include an extra display property for each record:
The display property would include only those values that are formatted and different from the value in fields (e.g. plain text values would be omitted, and probably booleans and unformatted numbers). The formatting used would follow the same logic as for CSV or Excel exports.
The text was updated successfully, but these errors were encountered:
The API
GET /records
call today returns the underlying values of Grist cells, for example:) are returned as numbers, seconds since epoch, e.g.
1709510400`.Sometimes it's helpful to get values as a user would see them, i.e. the display values. For example, display values are what gets exported in CSV or Excel exports. For example:
$1,000.00
or37%
2024-03-04
orMarch 3, 2024
Proposal is to add an optional query parameter
includeDisplay=1
toGET /records
call. When set to a true value, the response would include an extradisplay
property for each record:The display property would include only those values that are formatted and different from the value in
fields
(e.g. plain text values would be omitted, and probably booleans and unformatted numbers). The formatting used would follow the same logic as for CSV or Excel exports.The text was updated successfully, but these errors were encountered: