My Oracle Support Banner

Import Object not working as expected when Import Fields are defined (Doc ID 2661247.1)

Last updated on APRIL 24, 2020

Applies to:

Siebel CRM - Version 19.7 and later
Information in this document applies to any platform.


Actual behavior:
After creating custom import object and specifying Import Fields, when standard import procedure is invoked in mapping step, can see all applet fields/columns, instead of seeing only columns that are described in import object.
In applet can see calculated fields and other fields that should not be imported, and these fields confuses end users.
Only need to see fields that are described in import object.

Expected behavior:
Expected to see only columns that are described in import object.



1. Create an import object on a custom Business Component and specify import fields that are to be displayed upon importing data into that custom BC.

2. Upon bringing up Applet belonging to custom BC and invoking import functionality, seeing additional fields that are not listed as part of corresponding import object for that BC.

3. Instead the additional fields displayed in the import window is from the list of available fields in that Applet.


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.