SampleCustomizer on Table

First of all, what version are you using? And second, providing your own customizer should only be the last resort. Can you detail your use-case why you need your own customizer?

Hello, Markus.

>> First of all, what version are you using?
OneIM v8.1

>> Can you detail your use-case why you need your own customizer?
The Person table is expanded by a custom field (CCC_IsResident).
I need, if CCC_IsResident = true, the custom fields CCC_FirstName_en and CCC_LastName_en become mandatory.

Hello, Markus.

>> First of all, what version are you using?
OneIM v8.1

>> Can you detail your use-case why you need your own customizer?
The Person table is expanded by a custom field (CCC_IsResident).
I need, if CCC_IsResident = true, the custom fields CCC_FirstName_en and CCC_LastName_en become mandatory.

Do you need this in the Win32 Manager only or in the Web Portal?

Markus Weiss-Ehlers said:

Do you need this in the Win32 Manager only or in the Web Portal?

Both

The last question, do you change the flag on-the-fly or is the use-case that when you edit an existing person having the flag set, the two columns should be mandatory?

Markus Weiss-Ehlers said:

The last question, do you change the flag on-the-fly or is the use-case that when you edit an existing person having the flag set, the two columns should be mandatory?

By default the flag is unset and the columns are not mandatory. But if someone sets this flag, the columns should be mandatory.

Okay, so a customizer is needed for this use-case.

To register a customizer in the database

1. Create an entry for the CRL type.
   • In the Designer, select Base data I Advanced I CLR types.
   • Select Object I New.
   • Enter the following data:

Table: Master data of a CLR type

2. Create an entry for the customizer.
   • Select the Base data I Advanced I Customizer category in the Designer.
   • Select Object I New.
   • Enter the following data:

Table: Master data of a customizer

3. In the Designer assign the customizer to the table definitions for which you want it to be valid.
4. Save you changes

IMPORTANT: From this point on, the new object functions are enabled and all users need the new assembly to work with database objects.

Thanks! You have helped me.