Problem Note 66965: The error "Could not read JSON: Unrecognized field" occurs when a text field contains braces ({ }) in SAS® Customer Intelligence Studio
In SAS Customer Intelligence Studio, the following error occurs when you use braces ({ }) in a text-type input variable in a SAS® Real-Time Decision Manager campaign:
Could not read JSON: Unrecognized field ""year":1964,"active":true" (Class com.sas.analytics.crm.flow.inbound.client.IBVariableVO), not marked as ignorable at [Source: org.apache
.catalina.connector.CoyoteInputStream@79c2475e; line: 1, column: 638] (through reference chain: com.sas.analytics.crm.flow.client.controller.args.FlowTestCasesArgs["testCases"]->com.sas.analytics.crm.flow.inbound.client.TestCaseVO["requestVars"]->com.sas.analytics.crm.flow.inbound.client.IBVariableVO[""year":1964,"active":true"]); nested exception is org.codehaus.jackson.map.exc.UnrecognizedPropertyException: Unrecognized field ""year":1964,"active":true" (Class com.sas.analytics.crm.flow.inbound.client.IBVariableVO), not marked as ignorable at [Source: org.apache.catalina.connector.CoyoteInputStream@79c2475e; line: 1, column: 638] (through reference chain: com.sas.analytics.crm.flow.client.controller.args.FlowTestCasesArgs["testCases"]->com.sas.analytics.crm.flow.inbound.client.TestCaseVO["requestVars"]->com.sas.analytics.crm.flow.inbound.client.IBVariableVO[""year":1964,"active":true"])
Here is the value of the input variable in the example above:
{"year":1964,"active":true}
You might be able to work around this issue by enclosing the text value in double quotation marks. However, you need to verify that this workaround does not change the behavior of the campaign.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
SAS System | SAS Real-Time Decision Manager | Microsoft® Windows® for x64 | 6.6 | | 9.4 TS1M6 | |
64-bit Enabled AIX | 6.6 | | 9.4 TS1M6 | |
64-bit Enabled Solaris | 6.6 | | 9.4 TS1M6 | |
Linux for x64 | 6.6 | | 9.4 TS1M6 | |
SAS System | SAS Customer Intelligence Studio | Microsoft® Windows® for x64 | 6.6 | | 9.4 TS1M6 | |
Microsoft Windows 8 Enterprise 32-bit | 6.6 | | 9.4 TS1M6 | |
Microsoft Windows 8 Enterprise x64 | 6.6 | | 9.4 TS1M6 | |
Microsoft Windows 8 Pro 32-bit | 6.6 | | 9.4 TS1M6 | |
Microsoft Windows 8 Pro x64 | 6.6 | | 9.4 TS1M6 | |
Microsoft Windows 8.1 Enterprise 32-bit | 6.6 | | 9.4 TS1M6 | |
Microsoft Windows 8.1 Enterprise x64 | 6.6 | | 9.4 TS1M6 | |
Microsoft Windows 8.1 Pro 32-bit | 6.6 | | 9.4 TS1M6 | |
Microsoft Windows 8.1 Pro x64 | 6.6 | | 9.4 TS1M6 | |
Microsoft Windows 10 | 6.6 | | 9.4 TS1M6 | |
Microsoft Windows Server 2008 | 6.6 | | 9.4 TS1M6 | |
Microsoft Windows Server 2008 R2 | 6.6 | | 9.4 TS1M6 | |
Microsoft Windows Server 2008 for x64 | 6.6 | | 9.4 TS1M6 | |
Microsoft Windows Server 2012 Datacenter | 6.6 | | 9.4 TS1M6 | |
Microsoft Windows Server 2012 R2 Datacenter | 6.6 | | 9.4 TS1M6 | |
Microsoft Windows Server 2012 R2 Std | 6.6 | | 9.4 TS1M6 | |
Microsoft Windows Server 2012 Std | 6.6 | | 9.4 TS1M6 | |
Microsoft Windows Server 2016 | 6.6 | | 9.4 TS1M6 | |
Microsoft Windows Server 2019 | 6.6 | | 9.4 TS1M6 | |
Windows 7 Enterprise 32 bit | 6.6 | | 9.4 TS1M6 | |
Windows 7 Enterprise x64 | 6.6 | | 9.4 TS1M6 | |
Windows 7 Home Premium 32 bit | 6.6 | | 9.4 TS1M6 | |
Windows 7 Home Premium x64 | 6.6 | | 9.4 TS1M6 | |
Windows 7 Professional 32 bit | 6.6 | | 9.4 TS1M6 | |
Windows 7 Professional x64 | 6.6 | | 9.4 TS1M6 | |
Windows 7 Ultimate 32 bit | 6.6 | | 9.4 TS1M6 | |
Windows 7 Ultimate x64 | 6.6 | | 9.4 TS1M6 | |
64-bit Enabled AIX | 6.6 | | 9.4 TS1M6 | |
64-bit Enabled Solaris | 6.6 | | 9.4 TS1M6 | |
HP-UX IPF | 6.6 | | 9.4 TS1M6 | |
Linux for x64 | 6.6 | | 9.4 TS1M6 | |
Solaris for x64 | 6.6 | | 9.4 TS1M6 | |
*
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: | high |
Date Modified: | 2021-05-26 16:11:26 |
Date Created: | 2020-11-18 12:08:42 |