MDM - Customer 360
- MDM - Customer 360 10.3
- All Products
Reference Number
| Description
|
|---|---|
TCR-3034
| In Linux and WebLogic environments, when you run the
install-tcr.sh script, the install script fails with the following error:
Workaround: Perform the following tasks:
|
TCR-3033
| When you configure the Task Manager in the Provisioning tool, you cannot configure the action message to show when you perform an action.
|
TCR-3020
| In IBM DB2 or Microsoft SQL Server environments, you cannot migrate to the data model based on the Party table from the data model based on the Party Role table.
|
TCR-3019
| In IBM DB2 and JBoss environments, the dashboard view of a record might display the following error message in the Hierarchies panel:
Workaround: Perform the following tasks:
|
TCR-3014
| When you use the Java project that is included in the
Customer 360 installation files to extend the user exit, the Java project fails when you compile it.
Workaround: Before you compile the project, perform the following tasks:
|
TCR-3012
| In IBM DB2 environments, when you run the
lookup_localization script, the script imports the lookup data in all the languages except the Russian language. The script fails with the following error message:
|
TCR-2980
| After you update an active record, the dashboard view of the record shows the updated values even though the changes are not approved.
|
TCR-2966
| In environments that use the data model based on the Party Role table, when you add a relationship between two Person records, an empty Related Person record is created for one of the records.
|
TCR-2938
| In WebLogic environments, after you install or upgrade
Customer 360 , if you try to install or upgrade
Customer 360 again, you get the following error message:
[wldeploy] Target state: deploy failed on Server AdminServer [wldeploy] javax.naming.NameNotFoundException: Unable to resolve 'jdbc.ActiveVOS'. Resolved 'jdbc'; remaining name 'ActiveVOS' When you run the install or upgrade script again, the data source defined in WebLogic for the ActiveVOS database is deleted.
Workaround: Manually create the data source in WebLogic.
To create a data source in WebLogic, perform the following tasks:
|
TCR-2930
| In a localized environment, when you open a record, the hierarchy name is not localized in the Hierarchy panel.
|
TCR-2005
| If you update a verified email address, phone number, or address, the status of the email address, phone number, or address does not change to reflect the status of the updated value.
|
TCR-1908
| On the
Home page, when you sort the tasks based on priority, the tasks are incorrectly sorted.
|
TCR-1899
| When you edit a record, if you update an address child record, you cannot save the changes and get the following error message:
|
TCR-1647
| In WebSphere environments, Customer 360 integration with Product 360 does not work.
|
TCR-1527
| During a file import, if you configure the header row to a value other than 1, Customer 360 shows an incorrect preview of your imported file.
|
TCR-1358
| In a hierarchy, if you add a relationship from a B2C customer to a B2B customer, Customer 360 does not display the change history.
|
TCR-1297
| Customer 360 does not support the TIFF image format in the Product Details widget.
|
TCR-1169
| For the Organization customer type, when you edit a relationship or classification to add additional relationship attributes, Customer 360 does not save the attributes that you add.
|
TCR-1112
| The data mart service does not support the Microsoft SQL Server database.
|