Bug 3384

Native PDF Not Saving Newspaper Columns 29 July, 2020

Christopher Craft
25 September, 2019
Product: PowerBuilder Category: DataWindow
Version: 2017 R3 Build:
Classification: Enhancement Publishing: Public
Priority: P2
Status: Transferring Reason:
Mark Lee @Appeon 29 July, 2020
#36
Hi Chris,

Thanks for your feedback.
We fully understand the situation. We will transfer the information to our product team for consideration.
 
BTW, it doesn't mean the Bug is more important than Enhancement in issue classifications. We value them the same to make our products better.

Regards,
Mark Lee
Christopher Craft 29 July, 2020
#35
Mark,

I don't consider this an Enhancement as it is classified, it is a bug in the NativePDF generation.  Our customers expect to have a PDF document in the correct format. Like I mentioned when I submitted the bug, they use this report to show hundreds of prices for product that they are selling to their customers. When it shows all in one column then it becomes way too long of a report and so they don't use it. I hope you understand and will find a solution for R3. 

Thank you,
Chris Craft
Mark Lee @Appeon 28 July, 2020
#34
Hi Chris,

As far as I know, this issue will be further analyzed on the schedule listed in the next month. 
So I' not sure if this issue will be fixed in the upcoming PB 2019 R3.
We will keep you updated.
 
For the other issue, we suggest that you report a new bug.
This helps us to better manage our bugs. Our policy is one bug one ticket.
Thanks for your understanding!

Regards,
Mark Lee
Christopher Craft 27 July, 2020
#33
NewspaperTheme.docx (184KB)

Mark,

Has this issue been fixed for the upcoming 2019 R3? It has almost been a year since reported. I have been telling our customers that we are waiting on a fix from you.

Also, when using Themes and the report is rendered on the UI all the newspaper columns except the first will still be in the Theme. I debate if I want the Print Preview view to show the actual report colors or keep in in the Theme but I do know it should not be different by newspaper column. I have attached a print screen for you to see. Notice the headers for Description\Price\UOM on the 2nd and 3rd newspaper columns.

Chris Craft
Mark Lee @Appeon 27 March, 2020
#32
Hi Chris,

As far as I know, this feature is currently in the requirement queue list waiting for further analysis.
And according to our development team’s schedule, maybe we will add this feature in PB 2019 R3 which might be released in the second half of 2020 (PB 2019 R2 will be released recently).
And the exact release date is still not decided yet for now.

Regards,
Mark Lee
Christopher Craft 26 March, 2020
#31
Mark,

As more customers are moving the the latest release we are getting more calls about this.  Can we get an update on this? I need this to be addressed.

Thanks
Chris Pollach @Appeon 19 December, 2019
#30
Hi Chris;

    I am sorry that the workaround suggestion did not solve your issue.
Thanks for letting us know. 

Regards ... Chris
Christopher Craft 19 December, 2019
#29
It does not.  I tried that when I realized it worked as a nested DataWindow.
Chris Pollach @Appeon 19 December, 2019
#28
Hi Chris;

  Thought: As a workaround, what happens if you place the N-UP DWO into "Preview" mode before performing the SaveAs() command and then flip it back ... Does that make it work OK?

DC.Modify("DataWindow.Print.Preview=Yes")
DC.SaveAs (PDF!)
DC.Modify("DataWindow.Print.Preview=No")

Regards ... Chris
Mark Lee @Appeon 18 December, 2019
#27
Hi Chris,

Thanks for your quick update.
We'll transfer this information to our development team for consideration.

Regards,
Mark Lee
Christopher Craft 18 December, 2019
#26
Thank you Mark for the update. The odd part about this though is if you have that same newspaper DW as an embedded report then it works fine because the embedded DW is forced into preview mode and cannot be "un-previewed'. I am hoping all you need to do is force the DW into this mode just like if it was an embedded DW.

Chris
Mark Lee @Appeon 18 December, 2019
#25
Hi Chris,

Sorry to let you know that we are still working on it and will get back to you once there's any updates.
As far as I know, it is very difficult to use the PDFlib generator (the NativePDF is generated depended on it) to implement this Newspaper function whose content is not using the mode of 'What you see is what you get'.
 
So we need more time to further analyze it and we also don't know when this feature can be fixed.
You can refer to the bellow article, it introduces the PDFlib generator:
https://docs.appeon.com/appeon_online_help/pb2019/application_techniques/ch35s08.html#Using_the_PDFlib
Appreciate your understanding.

Regards,
Mark Lee
Christopher Craft 17 December, 2019
#24
Mark,

Any update on when this might get fixed?

Thank you,
Chris
Mark Lee @Appeon 04 November, 2019
#23
Hi Chris,
 
Because the issue was reported in this September, it is currently in the requirements queue list waiting for further analysis before us deciding which version we shall add it into.  
So there is no sufficient time to add it into the upcoming MR yet, but will be considered in the future MR or major release.
Hope you can understand.
 
BTW, thanks for joining the conference of Elevate 2019. Appeon really appreciates it!

Regards,
Mark Lee
Christopher Craft 01 November, 2019
#22
Hi Mark,

I spoke with Julie Jiang at the conference this week to see if she knew when this might be addressed but she didn't have an update.  Has this been included in the upcoming MR for 2017 or in a 2019 MR release?

Thanks,
Chris
Mark Lee @Appeon 17 October, 2019
#21
Hi Chris,
 
1.       Is there any way to always force NativePDF into the mode of 'What you see is what you get'?
[Mark:] In fact, NativePDF always uses the mode of 'What you see is what you get'.
And Newspaper-style columns are used only when the DataWindow object is printed. They do not appear when a DataWindow object runs (or in Preview). You can refer to the following article:
https://docs.appeon.com/appeon_online_help/pb2017r3/pbug/ch18s04.html#ug41990
So this is the reason why.  
 
2.       Regarding "change this issue from an Enhancement to a Bug", it is easy for me to make this change. 
But the Classifications here is only used for us to record whether this issue is a bug or an enhancement. It doesn’t mean that Bug will have higher priority than Enhancement. 
For the issues all our customers reported, we treat them in the same way. Sometimes some enhancements will have higher priority than bug. These will depend on the specific circumstances. 
 
I hope you can understand.

Regards,
Mark Lee
Christopher Craft 16 October, 2019
#20
Hi Mark,

Is there any way to always force NativePDF into the mode of 'What you see is what you get'?

Using a Composite or Nested DW has other issues:

1) The user then cannot save the data to Excel because the DW engine only exports data in the first DW which would now be nothing. Our customers use that feature all the time.

2) We have a report engine that modifies the SQL of the DW during runtime. Composite DW's do not have a SQL statement to morph so that is not an option.

Can you please change this issue from an Enhancement to a Bug? NativePDF was suppose to support all DW features and this was missed. As soon as you have 1 issue that cannot be saved using NativePDF then it almost forces you to go back to GhostScript.

Chris Craft
Mark Lee @Appeon 16 October, 2019
#19
Hi Chris,

Thanks for sharing the info.
We suggest you work it around using the Composite or Nested DW which contains the Tabular DW.
And currently NativePDF will export the PDF file using the mode of ‘What you see is what you get’.
When you change the Tabular DW to Composite or Nested DW, you will see all data in the correct layout after DW retrieves.
After that, if you use NativePDF to export the pdf file, you will get the PDF file you expected.

Regards,
Mark Lee
Chris Pollach @Appeon 07 October, 2019
#18
Hi Chris;

  I totally agree. Its a bug as the DW.Print() command that does not currently check the DWO's print preview state.

Regards ... Chris
Christopher Craft 04 October, 2019
#17
(In reply to Chris Pollach from comment #16)
Hi Chris;

  I suspect that it knows that Nested and Composite DWO's are always in
"Print Preview" mode whereas the "N-UP Print Preview" option is not checked
as the tabular DWO type is normally not viewed that way.

Regards ... Chris
If that is the case then you would think if I set the DW to be in Preview mode before saving then it would work...but it doesn't. Would be nice for Mark to chime in...
Chris Pollach @Appeon 03 October, 2019
#16
Hi Chris;

  I suspect that it knows that Nested and Composite DWO's are always in "Print Preview" mode whereas the "N-UP Print Preview" option is not checked as the tabular DWO type is normally not viewed that way.

Regards ... Chris
Christopher Craft 03 October, 2019
#15
(In reply to Chris Pollach from comment #12)
Hi Chris;

  I'll let Mark respond to the this question in full but, I don't think that
the nested issue is any different that your basic N-Up print time DW to PDF
issue. The main restriction is that the NativePDF feature does *not* look at
the "print Buffer" during its rendering.

Regards ... Chris
Hi Mark - could you provide some insight to this? Why would a Composite DW or a nested DW work? Chris
Chris Pollach @Appeon 30 September, 2019
#14
Hi Chris;

  Good point. It might work. I have never tested this combination myself using the NativePDF driver feature.

Regards ... Chris
Christopher Craft 30 September, 2019
#13
(In reply to Chris Pollach from comment #12)
Hi Chris;

  I'll let Mark respond to the this question in full but, I don't think that
the nested issue is any different that your basic N-Up print time DW to PDF
issue. The main restriction is that the NativePDF feature does *not* look at
the "print Buffer" during its rendering.

Regards ... Chris
Don't know if I'm following you...when you use a Composite or Nested DW if forces the DW to be in print preview mode and cannot be undone. This is when NativePDF will properly save it in the correct layout.
Chris Pollach @Appeon 30 September, 2019
#12
Hi Chris;

  I'll let Mark respond to the this question in full but, I don't think that the nested issue is any different that your basic N-Up print time DW to PDF issue. The main restriction is that the NativePDF feature does *not* look at the "print Buffer" during its rendering.

Regards ... Chris
Christopher Craft 30 September, 2019
#11
Hi Mark,

The options Chris provided is not a workaround but a re-write. It is not feasible to create a Web Service to simply create a PDF document when using newspaper columns. Nor can I use the N-Up for the reason I stated earlier. The biggest issue I have is our customers customize their own DW formats so I don't have control over which type of DW to use.  I have no workaround except to make them go back to using GhostScript which is a real shame.

As a side note - it seems the Native PDF generation does support it in some way because I found another DW we have that uses newspaper columns except it is a nested report instead. Could there be some DW setting I apply just before firing a SaveAs that will make it render like a nested report?

Chris
Mark Lee @Appeon 30 September, 2019
#10
Hi Chris Craft,
 
We can reproduce it on our side.
Currently, the native PDF engine does not support setting the Newspaper Columns Across property.
We will record it as a new requirement/enhancement request and will transfer it to our product team for consideration.
BTW, please use the workaround provided by Chris for now.

Regards,
Mark Lee
Chris Pollach @Appeon 26 September, 2019
#9
Hi Chris;

  As you requested, I have changed bumped this ticket's priority to a #2 level. 

Regards ... Chris
Mark Lee @Appeon 26 September, 2019
#8
Hi Chris Craft,

Thanks for report this problem.
I will working on it and get back to your soon.
Thanks for your patience and understanding.

Regards,
Mark Lee
Christopher Craft 25 September, 2019
#7
Well this stinks. Can you please up the priority for me since there is no workaround? We have customers that send out their daily price/cost lists to customers and they are exponentially longer. We also have 3 column reports which exacerbates the problem even more.
Chris Pollach @Appeon 25 September, 2019
#6
Hi Chris;

  Thank you for the DWO source!  Yes, a proper N-UP DWO might render OK as it is already in N-UP sequence. However, the Tabular DWO with N-UP printing is OK when sent as a postscript print stream to a PDF render engine like GhostScript. However, the native PDF engine does not observe the Print N-UP setting.

  As a workaround, you could use a proper N-UP DWO but you are correct  that this will change the presentation order as you described. I will now transfer this problem over to the main Support/Engineering Team for their review and fix recommendations.

  In the mean-time, another way would be to a) use a Web Service to render the PDF in N-UP mode using distill and then send that back to the PB Client App (for example: http://chrispollach.blogspot.com/2017/10/pdf.html) or b) Send the PSR into a DB Table and have a trigger fire off a PBAPP.exe that uses GhostScript on the DB Server. The rendered PDF is then added back into a DB Table for the PB Client to grab via a SelectBlob command. Neither alternative that I can think of though would be a "quick fix" (unfortunately).

Regards .... Chris
Christopher Craft 25 September, 2019
#5
d_rpt_ar_printpricelist_1a.srd (29KB)

I have attached the DW Source
Christopher Craft 25 September, 2019
#4
This is not an N-Up. Just a simple datawindow with the newspaper columns set to 2. We needed the data to display on the left first then continue to the next column. N-Up goes from left to right by row.

Yes, Distill works but NativePDF does not...which is a problem for us now.
Chris Pollach @Appeon 25 September, 2019
#3
Hi Chris;

   FYI:  I can make it work OK using the DISTILL! option but not when using the NATIVEPDF! option. I am assuming that this is a Tabular DWO that uses the Print N-UP option as the DW does not display in N-UP until I turn on the "Print Review" option.

   FWIW: I am using my PSR Viewer to test with ... http://chrispollach.blogspot.com/2019/04/psr.html

Regards .... Chris
Chris Pollach @Appeon 25 September, 2019
#2
Hi Chris;

   Thank you for the PSR. I'll try & replicate this issue.

In the mean-time (since I do not have the DWO source .. can you tell me:

a) Is this an N-Up DW type  - OR -
b) Is this a Tabular DWO with the print specifications set to N-UP?

Regards ... Chris
Christopher Craft 25 September, 2019
#1
Newspaper.psr (171KB)

We have DataWindow reports which use the newspaper column feature. When these reports are saved as PDF (Native) the newspaper columns go away - it is all showing under one column just like it would if you took it out of preview mode. This makes the report double in size for every page.

I have attached a PSR for you to try it with.

Chris Craft
OS:
All
Platform:
32-bit
Database Type:
Database Version: