Review and Import the CustomerPK File in Hubble

If you have custom tables or ERP tables that Hubble does not support by default, you need to add them to the profile. Hubble requires information on what column combinations make the table unique (similar to a primary key). This information should be added to a file called CustomerPK.xml. For detailed information, refer to the Hubble Administration Guide.

If you do not have custom tables, a standard version of the CustomerPK.xml file is included with the application. If you are unsure whether you have a customized CustomerPK.xml file, follow the steps below to locate and identify modifications.

Finding the location of the customerPK.xml

In earlier versions of Hubble Desktop, customized CustomerPK.xml files needed to be defined on the administrator’s machine. Typically, the CustomerPK.xml file would be in the Hubble install directory. In later versions, you can import/export the CustomerPK.xml file into the Object Repository for central management.

Check for Central Management Support:

1. Log into your current Hubble Administrator.

2. Navigate to Data Sources > Profiles.

3. If you see the CustomerPK.xml Configurations option, your version supports centrally managed CustomerPK.xml files.

If Central Management is Not Supported:

1. The latest CustomerPK.xml will be in the install directory of the Hubble Administrator’s machine.

2. Ensure the master version is shared across all administrator machines.

If Central Management is Supported but Export is Disabled:

1. This indicates that a CustomerPK.xml file has not been imported.

2. Follow the same steps as if central management is not supported.

Importing the CustomerPK.xml File

If the master CustomerPK.xml has not been modified, no further action is required. If it has been modified, follow these steps:

1. Copy the File: Copy the file from its current location to the install directory of the version you are upgrading to.

2. Import the File: From the CustomerPK Configurations menu in the Hubble Administration tool, import the file into the centrally managed Object Repository.

3. If Export is Enabled: This means your master version has been imported into the Object Repository.

Identifying Modifications in CustomerPK.xml

1. Locate the Master CustomerPK.xml: Right-click on the CustomerPK.xml file and choose Open with Notepad.

2. Check for Primary Keys:

   • Scroll to the bottom of the file.

   • Look for primary key definitions under <Version Id="AllVersions"> or any other listed version.

   • If primary keys are defined, copy the CustomerPK.xml file from the current release to the install path for the latest version and import it as mentioned above.

If no primary keys are defined, proceed to the next section of your task.