Adding fields to sys_user

[gm01]

This question is just for a sanity check to see about best ways to have user fields referenced.   I am building an application and am pulling information through REST from a external system.   This external system uses AD as well as ServiceNow so they would reference the same user fields.   There is a unique uuid linked to the user on the external system that I am pulling from the REST call.   So my question is, is it an acceptable and normal practice to insert a new attribute into the sys_user table for users or to create a new table and do mapping back.   Obviously easiest way is to add to the sys_user but is this a perfectly acceptable method?

[Chuck Tomasi · Accepted solution]

Hi Gabe,

Stick with adding fields to sys_user. For example, AD may have an attribute called "foo" that you want to import in to ServiceNow. Create a field called u_foo. Don't get overly complex with mapping fields and other tables when it's perfectly acceptable (and recommended) to add your own.

[Chuck Tomasi]

Reference:

http://wiki.servicenow.com/index.php?title=Creating_New_Fields