We are progressing with our POC and hit an issue with an Oracle RPC call. This issue occurs in the initial screen of our main application processing and this is stalling our POC progression.
When we call this particular RPC, we are getting an error in the Web API console - "Input string was not in a correct format."
Details:
Dummy Declaration:
p_application(Integer S, String M, String A, String Mt, String Adv, String Fo, String sUs, Date Pro, String sA, Long bat, Ref Long out_bh_s, Ref Long status, Ref String msg) RPCFUNC ALIAS FOR "pack.proc"
API calling parameter:
SqlParameters": [
{
"Direction": null,
"Category": 1,
"ParameterName": "name",
"ParameterType": "int",
"ParameterValue": 1
},
{
"Direction": null,
"Category": 1,
"ParameterName": "name",
"ParameterType": "string",
"ParameterValue": "Data"
},
{
"Direction": null,
"Category": 1,
"ParameterName": "name",
"ParameterType": "string",
"ParameterValue": "Data"
},
{
"Direction": null,
"Category": 1,
"ParameterName": "name",
"ParameterType": "string",
"ParameterValue": "Data"
},
{
"Direction": null,
"Category": 1,
"ParameterName": "name",
"ParameterType": "string",
"ParameterValue": "Data"
},
{
"Direction": null,
"Category": 1,
"ParameterName": "name",
"ParameterType": "string",
"ParameterValue": "Data"
},
{
"Direction": null,
"Category": 1,
"ParameterName": "name",
"ParameterType": "string",
"ParameterValue": "Data"
},
{
"Direction": null,
"Category": 1,
"ParameterName": "name",
"ParameterType": "date",
"ParameterValue": "2016-05-16"
},
{
"Direction": null,
"Category": 1,
"ParameterName": "name",
"ParameterType": "string",
"ParameterValue": "Data"
},
{
"Direction": null,
"Category": 1,
"ParameterName": "name",
"ParameterType": "long",
"ParameterValue": 1
},
{
"Direction": null,
"Category": 1,
"ParameterName": "name",
"ParameterType": "long",
"ParameterValue": 0
},
{
"Direction": null,
"Category": 1,
"ParameterName": "name",
"ParameterType": "long",
"ParameterValue": 0
},
{
"Direction": null,
"Category": 1,
"ParameterName": "name",
"ParameterType": "string",
"ParameterValue": " "
}
Thank you for your replay. We are not using any array.
Looking at the Appeon community, I could see only one discussion on this, but it was for the earlier PowerServer release.
https://community.appeon.com/index.php/qna/q-a/input-string-was-not-in-a-correct-format
My registry key value for ‘NLS_LANG’ is ‘ENGLISH_UNITED KINGDOM.WE8MSWIN1252’.
NLS parameters in the database are: (SELECT * FROM V$NLS_PARAMETERS)
PARAMETER VALUE
1 NLS_LANGUAGE ENGLISH
2 NLS_TERRITORY UNITED KINGDOM
3 NLS_CURRENCY £
4 NLS_ISO_CURRENCY UNITED KINGDOM
5 NLS_NUMERIC_CHARACTERS .,
6 NLS_CALENDAR GREGORIAN
7 NLS_DATE_FORMAT DD-MON-RR
8 NLS_DATE_LANGUAGE ENGLISH
9 NLS_CHARACTERSET WE8ISO8859P1
10 NLS_SORT BINARY
11 NLS_TIME_FORMAT HH24.MI.SSXFF
12 NLS_TIMESTAMP_FORMAT DD-MON-RR HH24.MI.SSXFF
13 NLS_TIME_TZ_FORMAT HH24.MI.SSXFF TZR
14 NLS_TIMESTAMP_TZ_FORMAT DD-MON-RR HH24.MI.SSXFF TZR
15 NLS_DUAL_CURRENCY ¿
16 NLS_NCHAR_CHARACTERSET AL16UTF16
17 NLS_COMP BINARY
18 NLS_LENGTH_SEMANTICS BYTE
19 NLS_NCHAR_CONV_EXCP FALSE
Do you think the solution in the above link is still valid for PowerServer 2021 and I should try changing the NLS_LANG value in the registry and try again? If not, do we need to do anything else to resolve this?