A custom field is a label you attach to emissions data so you can filter, group and report by something Avarni does not track as standard.
Use one for a business unit, a cost centre, a product line, a region of your own definition, or a data quality marker.
Work backwards from your report
Design custom fields from what you need to report on, not from what is in your data.
If your board asks for emissions by division, you need a division field. If nobody will ever ask, you do not need the field.
A field you add later can only be populated on data you import later, unless you go back and bulk edit. Decide before you load a year of data.
Create one
You need admin access.
Go to Settings › Custom Fields.
Select Add Custom Field.
Enter a Name.
Optionally enter Valid values.
Select Create.
Valid values
Leave valid values empty and the field accepts any text.
Set valid values and the field only accepts what you listed. Use this for anything with a fixed set, such as a division or a region, because it stops the same thing arriving as three different spellings.
Valid values are enforced when someone edits a row and when a spreadsheet is imported. They are not enforced on every route into the platform, so check your values after the first import.
Where custom fields appear
Once created, a custom field appears as:
A column in your upload templates and your general ledger import
A filter and a column in the Emissions Hub
A group-by option in the Emissions Hub and on graphs
A condition and an action on classification rules and Method branches
A column in your exports
Limits
50 custom fields per organisation
1000 valid values per field
Custom fields attach to emissions data only, not to suppliers, entities or facilities
Tidying values later
There is no merge function. If the same thing arrived as three spellings, filter to each one and use Bulk Edit to set them all to the value you want.
Setting valid values on the field prevents it happening again.