Questions? Feedback?powered byOlark live chat software
Bug 2223

[GENERAL] computed field format in .NET assembly 11 February, 2019

Don Olliver
30 January, 2019
Product: PowerBuilder Category: DataWindow
Version: 2017 R3 Publishing: Public
Status: Reproducing Priority: P1
Classification: Resolution:
Mark Lee 11 February, 2019
Hi Don,

Thanks for your update.
We will wait for your test case.

Regards,
Mark Lee
Don Olliver 11 February, 2019
(In reply to Mark Lee from comment #4)
Hi Don,

Thanks for reporting this problem.
Kindly can you please provide a simple test case(PBL and C# code) to us to
reproduce it?
Thanks in advance.

Regards,
Mark Lee
Mark, This is a complex item to reproduce, and is taking us some time to create a test case. We will submit it as soon as we can. Thanks, Don
Mark Lee 30 January, 2019
Hi Don,

Thanks for reporting this problem.
Kindly can you please provide a simple test case(PBL and C# code) to us to reproduce it?
Thanks in advance.

Regards,
Mark Lee
Don Olliver 30 January, 2019
Thank you Chris.

Don
Chris Pollach 30 January, 2019
Hi Don;

  Thank you for bringing this issue to our attention. I looked through the other current "open" tickets and could not find any similar issue.

 I do not know if we have a fix coming out for this problem in PB 2017 MR01 due out this week. I will transfer this ticket over to the main Support/Engineering team now for their review of the situation and what a possible workaround and/or fix might be.

Regards ... Chris
Don Olliver 30 January, 2019
Issue with Computed Field.docx (159KB)

When adding a new computed field to a datawindow for a .NET assembly target (PB 2017 R3 or PB 2019 B1), the format of [GENERAL] is used by default. This seems to work fine if the expression is a string. However, if the expression is the value of other expressions being added together, or the sum of a numeric column for all rows + the sum of another numeric column for all rows, a computed field using [GENERAL] does not display on a report. Changing the format to [General] does not have the same problem. See the attachment for steps to reproduce.

The same datawindow in a PB .exe target does display the computed field. We tried changing the the DW syntax at runtime in the .Net assembly, by doing a global replace of format="[GENERAL]" with format="[General]", but this broke other fields. Note - this problem also occurs in SQL Server 2017.

We have spent nearly a year migrating our PB 12.5 application and PB 11.5 COM components into PB 2017 targets. We are submitting this with P1 priority, because until this issue is fixed we cannot move our migrated application and components into production.
OS:
Windows 10 
Platform:
64-bit 
Database Type:
SAP SQL Anywhere 
Database Version:
17