Configuratiom
Custom field values are shown in these tables only if the field has been configured for reporting. In Simplicate you can define which custom fields should be exposed to the Insights API by marking them as reportable in the custom fields settings.
Only fields that are marked as reportable will be included in the Insights API output. These fields are then mapped to the available report_column_1βreport_column_5 columns in the tables below.
To learn how to set this up and how Simplicate determines which fields are included, see:Using custom fields in the Insights API
This guide explains:
How to access and manage custom fields per module
How to mark fields as reportable for Insights
How each reportable field is mapped to the corresponding
report_column_xfieldsConsiderations when changing reporting configurations
Tables Covered
api_relation_custom_fieldsapi_project_custom_fieldsapi_sale_custom_fieldsapi_employee_custom_fields
Common Fields Structure
All custom fields tables share the same field structure:
Field Name | Type | Description |
| Integer | Identifier of the parent entity (relation, project, sale, or employee) |
| String | Value of the first custom field configured for reporting |
| String | Value of the second custom field configured for reporting |
| String | Value of the third custom field configured for reporting |
| String | Value of the fourth custom field configured for reporting |
| String | Value of the fifth custom field configured for reporting |
Related Tables
api_relations- Forapi_relation_custom_fieldsviakey_model_id=relation_idapi_projects- Forapi_project_custom_fieldsviakey_model_id=project_idapi_sales- Forapi_sale_custom_fieldsviakey_model_id=sale_idapi_employees- Forapi_employee_custom_fieldsviakey_model_id=employee_id
