Hi Rahul;

   I actually also reported this during beta testing and was informed by Engineering that this is the default reporting state that PB 12.6 returns you to also in the DWO Painter. The actual NativePDF! setting is adhered to internally within the DWO source code.

  The key to check is the DWO Source code itself. If the DW is using XLSFO! is till have the following statement ...

export.pdf(method=1 distill.custompostscript="0" xslfop.print="0" nativepdf.customsize=2 nativepdf.customorientation=2 )

  If the DWO is using GhostScript (aka Distill!) then the export statement will be ...

export.pdf(method=0 distill.custompostscript="0" xslfop.print="0" nativepdf.customsize=2 nativepdf.customorientation=2 )

 If you have chosen the NativePDF! option for data expport, then the export statement will be ...

export.pdf(method=2 distill.custompostscript="0" xslfop.print="0" nativepdf.customsize=2 nativepdf.customorientation=2 )

  So the key thing to look for in the DWO source code is the "Method=n" setting. This is what really determines the actual type of export method in effect. You can see this in the DW Painter when you return to the PDF property setting. However, the default for the DW Painter is to show you the XML property setting upon return - which makes it confusing when you close & the re-open the DW Painter.

HTH

Regards ... Chris

Hi,

PB 2017 behaves the same as that in previous PBs, such as PB 11. 5 and PB 12.6, that it could not be saved in a format other than xml.

You may try to export to PDF using the NativePDF method as follows:

 [Data Window]

NativePDF_Valid=1

Please refer to the local help Application Techniques > Deployment Techniques > Deploying Applications and Components > PDF and XLS-FO export > Using the PDFlib generator for details.

Regards,

Mark Lee