- In some cases you may want to use a User Directory column as a compensation custom column import key. This kind of configuration is not recommended (best practice is to define a unique import key for each custom field) but is possible. It’s usually used to avoid importing the same data twice.
- In some cases, custom column won’t be populated as expected. When exporting the User Directory compensation data, it will be empty.
Reproducing the Issue
Using standard columns as compensation custom column import key fails in some cases
- In a compensation form, you have defined two custom columns:
- Custom Country (import key: standard column COUNTRY)
- Custom Time Zone (import key: standard column TIMEZONE).
- Assuming that COUNTRY and TIMEZONE were properly populated through a standard User Import (no compensation data), when exporting your User Directory WITH compensation data, Custom Country is properly populated but Custom Time Zone is empty.
- This is happening because not every User Directory column can be used as import keys. Custom column import key can only use non system fields (fields stored in users_info table).
- Custom column import key can only use non system fields (fields stored in users_info table). System level fields (fields stored in users_sysinfo table) cannot be used.
Here the system level fields list:
KBA , sf comp import key , sf compensation manage data , LOD-SF-CMP , Compensation Management , How To