Problem Note 69119: You are unable to save the modifications that you have made to the "Customer" entity in SAS® Anti-Money Laundering
You might encounter an issue in which you cannot update some configurations (such as Page Associations, Facet settings, and field properties) in the Customer entity data object in SAS® Visual Investigator.
In this scenario, the Save button is enabled. However, clicking the button does not save the changes.
The issue occurs only in the Customer entity and not in other entities such as Account.
Hot Fix 8.2.2 might not fix this known issue if you use SAS Anti-Money Laundering 8.2 or 8.2.1.
Here is the workaround to address the issue in SAS Anti-Money Laundering 8.2 or 8.2.1:
- Download the revised PTY.json file.
- Log on to AML 8.2/VI 10.7 and export the PTY.json file in the SAND and datahub/documents only.
- Unzip and edit the svi-sand/PTY.json file by copying the following section from the revised PTY.json file:
From:
"inside_code" : {
"displayName" : "Insider Code",
"type" : "text",
"options" : {
"features" : [ ],
"indexed_for_search" : true
}
},
To:
"inside_code" : {
"displayName" : "Insider Code",
"type" : "object",
"options" : {
"indexed_for_search" : true
},
"innerFields" : {
"code" : {
"displayName" : "code",
"type" : "text",
"options" : {
"features" : [ "facet" ],
"indexed_for_search" : true
}
},
"label" : {
"displayName" : "label",
"type" : "text",
"options" : {
"analyzer" : "standard",
"features" : [ "search", "facet" ],
"indexed_for_search" : true
}
}
}
},
- Create a new ZIP file with the revised JSON.
- Import the configuration (the ZIP file that you created with the modified PTY.json content).
- Clear the cache.
- Re-index the data.
Click the Hot Fix tab in this note for a link to instructions about accessing and applying the software update.
Operating System and Release Information
SAS System | SAS Anti-Money Laundering | Linux for x64 | 8.2 | 8.3 | Viya | Viya |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
Type: | Problem Note |
Priority: | medium |
Date Modified: | 2023-01-11 15:10:50 |
Date Created: | 2022-04-22 15:07:10 |