Bug 4876

Can not importJSON 01 July, 2020

Martin Holodniok
30 June, 2020
Product: PowerBuilder Category: DataWindow
Version: 2019 R2 Build:
Classification: Enhancement Publishing: Public
Priority: P3
Status: Transferring Reason:
Ken Guo @Appeon 01 July, 2020
Hi Martin,

Thanks for reporting this problem and for your suggestion. 
We'll transfer this enhancement to our product team for consideration. 

Chris Pollach @Appeon 30 June, 2020
Hi Martin,

  Currently, the PB Application would have to perform a GetChild() command and ImportJSON for *each* child DW object. The same procedure that is used today for populating Drop Down DatatWindows (DDDW) from a parent DWO under PowerScript control. This process is not expected to change in the near future.

  I will now change this ticket however into an enhancement request and then transfer it over to the main Support / Engineering team for their review & feedback for this enhancement.

armando herrera @Appeon 30 June, 2020
Hi Martin,

Thank you very much for your report. We are working on it and we will get back to you after analyzing it.

We'll keep you posted here!

Martin Holodniok 30 June, 2020
We are using nested reports in our DataWindows. So far, we were populating them with stored procedures, now we want to switch to JSONs and that’s the problem. 
We can have multiple nested reports on one row. The problem is, that we can’t use ImportJSON function for each nested report (dw child) separately. What do we import to first report is automatically in others, but we need different data there. Are you planning to improve this and make it possible to ImportJSON to each child separately?
Database Type:
Database Version: