Thanks All, My issue got resolved now.

I've declared Datastore as instance instead of local and its working as expected.

Earlier it had been declared as locally and it was working as expected in PB08 but after migration into PB2019 R3 it was not working .

The code in the wf_populate_account_type script concerns me. In this script, the following actions are performed:

1. A local DataStore in created.
2. A data object is assigned to the DataStore.
3. A Transaction object is assigned to the DataStore.
4. The DataStore.Retrieve() method is called.
5. If any rows are returned to the DataStore, ShareData is called; The local DataStore is the primary data source and the DataWindowChild is the secondary.
6. The script ends, which destroys all local variables in the script, including and especially the DataStore.

The Help documentation on ShareData is pretty clear (I'm including an annotated partial screen capture below):

To me, this would appear to explain why the Account Number child DW is empty. The remaining wonky behavior may be due to this... I cannot say with any certainty.

HTH, John

Hi All,

Please find the attached "Prt Scr for account_type_dddw.PDF" file showing screenshots of the code to populate these 4 DDDWs.

Hi Mohan;

   I would suggest using those same DWO's and then creating a small Test Case PB App that reflects this issue.Then attach this test case to this thread. Also, you could create a support ticket for Appeon's tech support to review the test case if you think that this is a genuine bug.

Note: If you post issues like this, please give us detailed information about your PB environment.

Regards ... Chris

Hi, Mohan -

Difficult to say with any certainty without seeing code, but from the YouTube clip you made available it appears as if the DataWindowChild (DWC) for the Account column may be getting invalidated. Does the window perform a GetChild on the account column to obtain a reference to child DW? Is there any manipulation of DWC properties being performed in the code? If so, this typically causes the reference to the child DW to become invalid.

Regards, John

Mohan -

   Please show us your code to populate these 4 DDDWs.

   Some  thoughts:

1.  If the values are independent of each other why are you using a shared DW behind the scenes?

2. When populating the dddw, have you inserted a row into the host dw (the dw that holds the dddw)?

3. Have you retrieved the data?

4. Have you determined the pointer to the datawindowchild, checked the rowcount > 0, then scrolled t orow 1?



Later -

Olan