Question Re: Nested datawindows being broken. in Technology Q&A

Nested datawindows being broken.

Former Member — Mon, 13 Oct 2014 07:58:57 GMT

after migrating from 12.5 to 12.6, my users immediately noticed that nested datawindows were pulling out wrong data.

running an odbc debug. I notice that (as you can see in the 2nd screenshot).

the invoiceno in the parent datawindow as retrieved from the database is 2003001526

the invoiceno PASSED from the parent datawindow, to the nested datawindow is 2003001472

ie: the odbc log shows the wrong value is passed to nested datawindow, yet it is the correct value as retrieved from the database.

the parent datawindow has the syntax of

select invoiceno from tblinvoice where jobreferenceno = :as_jobrefno and casefeeno = :al_casefeeno

the nested datawindow has the syntax of

select invoiceno,blah, blah2 from tblinvoiceassign where invoiceno = :al_invoiceno

I've made a test db and test datawindows containing of 2 rows in each table (ie by culling all data except those where related to invoiceno = 2003001526,2003001472), so its reproducible.

anyone has any clues? its affecting all os (win7 , win 8.1 , 32bit or 64 bit). database is sql server 2008 r2

I'm currently reinstalling 12.5 + ebfs.

Re: Nested datawindows being broken.

Former Member — Mon, 13 Oct 2014 14:35:43 GMT

Can you double check how you assign the retrieval argument of the nested datawindow in the composite datawindow?

Re: Nested datawindows being broken.

Former Member — Mon, 13 Oct 2014 15:05:49 GMT

in the painter, there is an option to choose the expression.

this same code/datawindow has no issue under 12.5 (lastest ebf). but is an issue under 12.6. I am literally unable to diagnose it

Re: Nested datawindows being broken.

Former Member — Mon, 13 Oct 2014 19:25:50 GMT

Do you create any computes on the fly? PB 12.6 has an issue when computes are created it returns the wrong result (KBA 2060375). Wondering if this might be related

Chris Craft

Re: Nested datawindows being broken.

Former Member — Tue, 14 Oct 2014 00:34:07 GMT

We had similar issue before. All we do is re-create the composite dw and the issue was resolved.

Re: Nested datawindows being broken.

Former Member — Tue, 14 Oct 2014 03:43:56 GMT

in this case, the problem is both the parent window and child datawindow are brand new created after i noticed the problem in my original application. the screenshots provided are from a custom build bug reproduction application.

invoiceno is not a compute, its the result of select invoiceno from tblinvoice where ...

it is passed to the nested datawindow as a retrieval argument. (both are numbers fields and sql server INT )

Re: Nested datawindows being broken.

Former Member — Tue, 21 Oct 2014 04:42:46 GMT

UPDATE!

After providing a 2nd debug build that literally shows

the parent being

SELECT

tblinvoice.invoiceno

FROM tblinvoice

WHERE

( tblinvoice.invoiceno = 2003001526 )"

and the child is somehow passed 2003001472

this is SAP's response/escalated to engineering

17.10.2014 - 11:31:42 CET - Info for Customer by SAP

Hi,

I have reproduced the issue.

Actually, no need to use the main DataWindow. When you retrieve the DW

r_cminvgen_noassign_test2 and you enter 2003001526

for the retrieval argument, it passes 2003001472 to SQL request. Very

Strange !

I modified the argument datatype from Number to Decimal and then it

works fine.

I will engage PB engineering for this problem.

Regards.

xxx

17.10.2014 - 14:12:45 CET - Info for Customer by SAP

Hi,

I Created CR772614 for PB engineering an pushed this CR into our

Hot-List.

I will let you know as soon as I have their feedback.

Regards.

xxx

Re: Nested datawindows being broken.

Former Member — Thu, 27 Nov 2014 04:18:14 GMT

the latest ebf23645

(pb12.6 build 4011) no longer has this issue.