Hi Jon,
The space issue is caused by the workaround of another issue in PowerServer 2020. Please try working around this issue by replacing the empty string with a space in PB script.
The traditional PowerServer uses the Microsoft built-in ‘System.Data.OracleClient’ which is being deprecated by Microsoft. This OracleClient has stored proc return value truncation issue, and this is an Oracle bug 【Bug 21616079】. You may refer to the below link for more information:
https://stackoverflow.com/questions/28508440/microsoft-iis-8-5-oracle-output-variables-are-truncated
PowerServer 2020 works around the issue when you select DB type 'Oracle 18C/19C'. This workaround only affects the varchar/varchar2 type parameters of the stored procedure.
We have done such kind of test and the only problem we found is that the space at the end of the return value of the varchar/varchar2 type parameters that the stored procedure outputs will be deleted. Everything works well except that.
Regards,
ZhaoKai
Sorry that currently there is no detailed plan to fix it in PowerServer 2020. You can select DB type 'Oracle 10g/11g/12c' and install Oracle 11G client to resolve the issue.
BTW, PowerServer 2021 will fix the issue. In the new generation of PowerServer, essentially 100% of PowerBuilder features are supported.
You can refer to the following link for more information on PowerServer 2021:
https://community.appeon.com/index.php/blogs/recent-blogs/new-deployment-options-coming-soon
Regards,
ZhaoKai