Hi James.
We had a similar requirement which was a unique ID used across systems which we needed to store on Genesys,
We use an external platform to carry out surveys so within the survey flow we run a data action which takes the Agent GUID as input and outputs one of the fields available under the HR section of the profile. The unique ID is no available to our external survey system.
The key is you need to run expand=employerInfo to expose the extra information.
It appears you can rename these fields on the GUI to something more suitable but within the API they retain the old names,
We also found that although you could add extra fields and define then with exact names you wanted these additional fields weren't exposed to the API, hence having to rename an existing field. The fields are also editable by the user.
I hope this helps
Iain
------------------------------
Iain Martin
BNP PARIBAS PERSONAL FINANCE SA
------------------------------