My Oracle Support Banner

Application Form In Access Policy Forcing To Enter As First Value For The Field Marked As Account Discriminator Before Any Lookup Selection (Doc ID 2717398.1)

Last updated on DECEMBER 08, 2022

Applies to:

Identity Manager - Version and later
Information in this document applies to any platform.


Application form in access policy is forcing users to enter as first value for the field which has been set with Account Discriminator flag to true while searching any lookup field in the application form.

Steps to reproduce the issue:

1. Install a connector that has lookup fields in its form, for example OUD
2. Create an Application Instance for the OUD connector.
3. Set any of the fields (for example Department Number) of the connector as an Account Discriminator "true" using the Design console.

-Follow section "17.6.1 Enabling Multiple Account Provisioning" from the below document to see how to set the account discriminator

4. Using the sysadmin console, create a new form for OUD.
5. Attach the new OUD form to Application Instance created above.
6. Create an Access Policy and under Provisioned Applications add the OUD Application previously created.
7. Click Finish,it will show "Error creating access policy The discriminator field XXX value is empty." error message as per below screenshot and Select Ok.

8. Under Provisioned Applications click the OUD application added (in the above screenshot OUD Server).

9. Once application form opened, provide any value to any of the fields that is not a lookup field before providing a value for the field set as account discriminator (department number), however while trying to provide a value for any of the lookups existing before providing a value for the account discriminator, will get an error "Error: A value is required" first for the field makes as Account Discriminator.

In the below screenshot, when providing a value for lookups Container DN or Communication Language,before setting a value for Department (account discriminator), the following error shows up.

If the same step is done for any of the other fields like Title, Middle Name, Location etc, it works fine.


Setting "Account Discriminator" to "true" for one of Form fields of the application.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.