Managing normalization 2.0 configs
You can manage your saved normalization configs in two ways:
- Delete old configs that are no longer needed
- Modify an existing config and save it as a new config
Automations note |
Please note that editing the config won’t edit the original modification and instead create a new one. Please note that deleting a config that is being used in an automation will make it fail.
If you’re automating your onboarding, please remember to adjust your automation to use the right config after making your edits. |
Table of contents
1. Select the recordset that you want to normalize
2. Select the existing config you want to modify
Map new columns to the existing config
Remove normalized columns that you no longer need
4. Save your changes as a new configuration
How to delete a config
In the normalization screen, please click on the button on the top right hand side called 'normalization configs'
This will take you to a screen where you can see all the normalization configs for your company. You can then select the config you were looking for and click delete. The config will be deleted and cannot be recovered.
All associated automation will fail until you add a new config to the automation set up.
How to modify a config
1. Select the recordset that you want to normalize
In the normalization screen, select the recordset you want to normalize.
2. Select the existing config you want to modify
On the first screen of the normalization process, please select ‘use existing config’ and then select the config you wan to modify from the dropdown list.
Then click on Modify Configuration
3. Make your edits
In this screen you can make any modifications you wish in the same way as if you were creating a new config from scratch.
If your file has the same structure as the config expects, it will just display the config as it exists right now, this will include all your mapping and settings and which columns it refers to.
If your file has a different structure, it will show a warning message that not all columns were mapped, and will show the fields that aren’t mapped/configured, like below:
Map new columns to the existing config
by selecting the input column that should be mapped to the normalized column
Remove normalized columns that you no longer need
Instead of re-mapping them, you can simply click on the red bin icon to remove them
Add new normalized columns
If your recordset has more or different columns than the config you’re editing, you can bring them into the modification screen by clicking on the black + icon on the right-hand side. You can then create mappings for these columns as you usually would
Update Address mapper
If you see an orange warning at the top of the screen, that will mean that the address mapper has been disabled as the platform can’t find all the columns it needs to complete the mapping. Click on the orange warning to open the address mapper widget and complete it.
4. Save your changes as a new configuration
Give your new config a name and complete normalization.