3 Replies Latest reply on May 7, 2012 3:31 PM by Patrick M-Oracle

    Data Load (4.1) hardcodes the working schema of the table

    Mike Mac
      I've found an issue when using the data load facility in 4.1.

      The schema name of the table to be used for storing the upload is captured in the application.

      If the application is exported and re-imported into a different schema, the application is still looking for the upload table in the original schema.....
      This causes the upload wizard, not to find the table in the second page of the upload process, and consequently, the column mapping LOV has no entires and the process fails.

      I have managed to get around this for now be editing the application source code and re-importing the application.

      This can't be the intended behaviour :)

      Is this a bug?