Troubleshooting: UserData is not defined in the Data Service Layer configuration

When you load custom userData for business objects, an error can occur when the Data Service Layer (DSL) configuration mappings for the data is not in the expected directory. If DSL configuration mappings are in a custom extension directory, you must specify your WebSphere Commerce instance when you run the Data Load utility. If you do not specify your instance, the utility might not locate the DSL configuration for your userData, which can result in a userData is not defined error.


When you load custom userData data for business objects with the Data Load utility, an error can occur stating that the userData is not defined in the data service layer configuration. This error occurs because the Data Load utility cannot find the DSL configuration for the userData that you are loading. The utility uses the DSL configuration to determine how custom fields are mapped to database tables and columns. When you run the utility and specify only the required command-line parameters, the utility searches only the default WebSphere Commerce Version 7 and fix pack directories for DSL configuration mappings. If the mappings for the business objects or userData that you are loading are in a different directory, the utility does not find the mappings by default. For example, if your userData is being populated into custom extension tables or columns and the mappings are in an extension directory.


You are loading marketing content that includes multiple click actions (image map) and include custom userData in the field2 column of your CSV input file. If you run the utility and do not include the optional -Dinstance command-line parameter, an error occurs. Without the -Dinstance specified, the Data Load utility cannot find this DSL configuration mapping and the error occurs with a message similar to the following error message:

An exception was caught: 
The user data with the key field2 is not defined in the data service layer configuration.
Application message:
An error occurred while transforming the data object into physical objects.  
Data Object: 
(clickAction: <unset>, inputOption: <unset>, url: null, mimeType: null, marketingSpotBehavior: null, uIDisplayable: 
 null, managingTool: null, ovrMktLimit: null), Physical objects: 
Transformed Physical objects:
,Operation mode: I.

Exception message:
The user data with the key field2 is not defined in the data service layer configuration.
Stack trace:


For the utility to locate the DSL configuration mapping for your userData, you must configure the utility to search extension directories for the configuration mappings. To configure the utility to search these directories, include the -Dinstance parameter when you run the utility. By including this parameter, the utility includes the WebSphere Commerce EAR xml directory in the class path and is able to locate all DSL configuration files. When you specify the -Dinstance parameter, ensure that you have the files for the instance that you specify in the WC_installdir/instances/instance_name directory or its subdirectories. You must also have access to the files. The utility can then locate the DSL configuration mapping for your custom data.

You must specify this parameter when you load custom data for business objects that have a Data Service Layer configuration that is in an extension directory. For example, specify the parameter when you are loading the following types of data:
  • Custom JAR files or Data Service Layer configuration files from the development environment to the WebSphere Commerce server.
  • Any type of data into a workspace environment.
  • Catalog data when base change history recording is enabled. When this history recording is enabled, change history is recorded whenever an object that is approved content is created, updated, or deleted with Management Center or the Data Load utility. For more information about this change history recording, see Enabling the change history for approved and canceled task groups.
  • Catalog entry description override data with the mediator.
  • SEO information for catalog entry or category data. To load SEO data with catalog entry or category data, include the loadSEO parameter with a value set to be "true". You can load SEO data with the following mediators:
  • WebSphere Commerce search index requests. You can request search indexing to occur with the following mediators:
    • Custom mediators that support indexing custom data types and extend
  • Marketing image map content that includes data for custom fields. You can load marketing image map content with the following mediator: