How to change schema properties

Hi Graziano,

Changing the schema properties of out of the box columns like this is something I would certainly not recommend.

What would be a better solution is to change the string you're receiving (M) to the integer values supported by the system.

If you look at the column value settings you'll see the list of allowed values (0, 1, 2, 9).

You can make a virtual property that does a data conversion from the values from your SQL DB to OIM DB.

0 - Unknown

1 - Male

2 - Female

9 - Unspecified.

Hi Jos,

Which "Type Data" should I use? When I select GENDER in the "Base Property" if I need to use the "String" item, the item is no longer available. THX

Hi Jos,

Which "Type Data" should I use? When I select GENDER in the "Base Property" if I need to use the "String" item, the item is no longer available. THX

What version are you using? 

In addition, a base property (column) called GENDER in uppercase looks like a custom column. The ootb one would be called Gender. 

OIM ver 9.2

Hi Graziano,

I can't see your screenshots (so I might be missing something :) ) but the case would be;

On the right column (your Oracle system) add a property, pick the type 'Data mapping'

Give it a nice name and display name, as the Base property select your 'GENDER' column from your SQL DB and add the 'Base values' (for the genders) that are in your SQL database. The data type should be integer (as that is what you want to be converting to)

On the 'Values to convert to' add the integers from One Identity (so 0 for unknown, 1 for male, 2 for female, 9 for unspecified). Give some thought to whether you want to ignore case, what you want to do with undefined values etc.

This new property you now have available on your SQL DB side can be mapped to the Gender column (on the person, on the 'left' of your synchronization) within One Identity as this now maps 'Integers' to 'Integers' and does the transformation based on the data mapping you've defined.

Hi Graziano,

I can't see your screenshots (so I might be missing something :) ) but the case would be;

On the right column (your Oracle system) add a property, pick the type 'Data mapping'

Give it a nice name and display name, as the Base property select your 'GENDER' column from your SQL DB and add the 'Base values' (for the genders) that are in your SQL database. The data type should be integer (as that is what you want to be converting to)

On the 'Values to convert to' add the integers from One Identity (so 0 for unknown, 1 for male, 2 for female, 9 for unspecified). Give some thought to whether you want to ignore case, what you want to do with undefined values etc.

This new property you now have available on your SQL DB side can be mapped to the Gender column (on the person, on the 'left' of your synchronization) within One Identity as this now maps 'Integers' to 'Integers' and does the transformation based on the data mapping you've defined.

Hi Graziano,

I can't see your screenshots (so I might be missing something :) ) but the case would be;

On the right column (your Oracle system) add a property, pick the type 'Data mapping'

Give it a nice name and display name, as the Base property select your 'GENDER' column from your SQL DB and add the 'Base values' (for the genders) that are in your SQL database. The data type should be integer (as that is what you want to be converting to)

On the 'Values to convert to' add the integers from One Identity (so 0 for unknown, 1 for male, 2 for female, 9 for unspecified). Give some thought to whether you want to ignore case, what you want to do with undefined values etc.

This new property you now have available on your SQL DB side can be mapped to the Gender column (on the person, on the 'left' of your synchronization) within One Identity as this now maps 'Integers' to 'Integers' and does the transformation based on the data mapping you've defined.

On the right column (your Oracle system) add a property, pick the type 'Data mapping'

Give it a name and display name, as the Base property select your 'GENDER' column from your SQL DB and add the 'Base values' (for the genders) that are in your SQL database. The data type should be integer (as that is what you want to be converting to)

On the 'Values to convert to' add the integers from One Identity (so 0 for unknown, 1 for male, 2 for female, 9 for unspecified). Give some thought to whether you want to ignore case, what you want to do with undefined values etc.

This new property you now have available on your SQL DB side can be mapped to the Gender column (on the person, on the 'left' of your synchronization) within One Identity as this now maps 'Integers' to 'Integers' and does the transformation based on the data mapping you've defined.

I verified that I am able to convert the column Person.Gender to a string in 9.2.

Hi Graziano,

To add a little bit on what Markus is saying

I can't see your screenshots (so I might be missing something :) ) but the case would be;

On the right column (your Oracle system) add a property, pick the type 'Data mapping'

Give it a nice name and display name, as the Base property select your 'GENDER' column from your SQL DB and add the 'Base values' (for the genders) that are in your SQL database. The data type should be integer (as that is what you want to be converting to)

On the 'Values to convert to' add the integers from One Identity (so 0 for unknown, 1 for male, 2 for female, 9 for unspecified). Give some thought to whether you want to ignore case, what you want to do with undefined values etc.

This new property you now have available on your SQL DB side can be mapped to the Gender column (on the person, on the 'left' of your synchronization) within One Identity as this now maps 'Integers' to 'Integers' and does the transformation based on the data mapping you've defined. (Note: In this case I'm converting the string to an integer, you could turn it around as well and convert the integer from One Identity to a string.).

Hi Jos,

Thanks with your latest information I was able to setup a custom property.