In Portrait you can define how the data is shown on the users frontend and with column types you can define the style and behaviour of the data. Furthermore you can make use of Actions which lets you integrate "Call To Actions" that fits the situation and gives a more streamlined user-experience.
...
If a string contains formatting, for instance line breaks, they will be ignored. In case you need formatting features, see the column types:
| Code Block | ||
|---|---|---|
| ||
- label: 'Creator' key: 'creator' type: 'string' showInTableHeader: true showInDetailList: true |
...
Generally it is not recommended to use this data type if the column is shown in the table (showInTableHeader showInTableHeadershould be false).
| Code Block |
|---|
type: text |
...
Generally it is not recommended to use this data type if the column is shown in the table (showInTableHeader showInTableHeadershould be false)..
| Code Block |
|---|
type: html |
...
This column type is used to declare data as date. Make sure that you declare the data backend-wise in the correct format: 2018-02-28 or 201828 or 2018-02-28 18:33:56.01. A date-field shown in the User-Frontend will not contain the time-part.
How a date will be presented to the user depends on his used browser language, for example given the above date will look this:
...