Account Style Field Extract
Provides a detailed reference of all account styles available to a client, including their data types, data fields, field mandatory status, help text, and configuration settings.
About this task
This report is designed to support users in understanding how to structure data for loading into IBM® Envizi ESG Suite, especially when working with complex or customized account styles across multiple data loaders.
Table 1 describes the columns in the report.
| Column | Description |
|---|---|
| Data Type Category | The broader category of data (e.g., Transport Fuels, Electricity). |
| Data Type | The specific data type (e.g., < 4.5t [kL], Electricity [kWh]). |
| Data Type Scope | The emissions scope associated with the data type (e.g., Scope 1). |
| Account Style Link | Internal identifier for the account style. |
| Account Style Caption | The display name of the account style. |
| Account Style Description | A description of the account style’s purpose or use. |
| Account Style Sub Type Setting | Indicates whether sub-types are selectable or locked. |
| Account Style Sub Type | Comma-separated list of sub-types, if applicable. |
| Account Style Field Label | The label of the field as shown in the UI. |
| Account Style Field Type | The type of data expected, for example, text, numeric, drop-down list). |
| Dropdown List Values | If the field is a drop-down list, the list of supported values. |
| Account Style Field Help Text | Help text associated with the field to guide data entry. |
| Account Style Field Setting | Indicates if the field is standard, mandatory, or hidden. |
| Account Style Field Column | The internal column reference, for example, C_1 - Primary, C_2 - Secondary. |
Procedure
- In the Global search field in the header, select Reports, and enter Account Style Field Extract.
- Select the report from the search results to open the Reports grid.
- Click the report in the Reports grid.
- Choose the output type.
- Click Submit.
- Click Download as CSV to export the report.
- Review the CSV file to understand the structure and requirements of each account style and their data fields.
What to do next
- Design or validate data loading processes.
- Understand field-level requirements for each account style.
- Support integration or automation efforts by referencing field types and constraints.