Setting Target Version in Designer ES Not Working

[Former Community Member]

I am using LiveCycle Designer ES and I save the form target version to Acrobat and Adobe Reader 8.0 or later. However, whenever I open the form in Acrobat I receive the JavaScript Warning Window telling me that "The PDF form requires a new version of Adobe Acrobat....". However it opens in Reader perfectly fine.



Is there a fix for this?

[Former Community Member]

Hello,



Should only get the warning when you try to open the file in an older version than the target version. Which version of Acrobat are you running?



Hélène

Adobe Systems

[Former Community Member]

I am using Adobe Acrobat 8 Pro Version 8.0.0

[Former Community Member]

Morning,<br /><br />Can you go to the XML Source and copy the first 4 lines so I can see the template version of your form? I'd like to see the <?xml?>, <?xfa?>, <xdp:xdp>, and <template/> tags.<br /><br />Then, can you search for the FormTargetVersion processing instruction? It will look like <?templateDesigner FormTargetVersion 25?>. I'd also like to see what version is specified here.<br /><br />Thank you<br /><br />Hélène<br />Adobe Systems

[Former Community Member]

<?xml version="1.0" encoding="UTF-8"?><br /><?xfa generator="AdobeLiveCycleDesignerES_V8.1" APIVersion="2.6.7185.0"?><br /><xdp:xdp xmlns:xdp="http://ns.adobe.com/xdp/" timeStamp="2007-11-09T14:39:53Z" uuid="216a7f98-3f33-4262-8184-1dfe5f203b75"><br /><template xmlns:xfa="http://www.xfa.org/schema/xfa-template/2.1/" xmlns="http://www.xfa.org/schema/xfa-template/2.6/"><br /><br /> <?PDFPrintOptions duplexMode 0?><br /> <?templateDesigner DefaultPreviewType interactive?><br /> <?templateDesigner DefaultPreviewPagination simplex?><br /> <?templateDesigner XDPPreviewFormat 19?><br /> <?templateDesigner FormTargetVersion 25?><br /> <?templateDesigner Zoom 100?>

[Former Community Member]

Thanks.<br /><br />Designer generates a PDF version 1.7 for the target versions 8.0 and 8.1. Acrobat is able to tell the difference from the xfa template version. So an xfa template version of 2.5 is 8.0 compatible while 2.6 is 8.1 compatible.<br /><br />The xfa template of your form is 2.6 therefore Acrobat thinks its an 8.1 compatible form.<br /><br /><template xmlns:xfa="http://www.xfa.org/schema/xfa-template/2.1/" xmlns="http://www.xfa.org/schema/xfa-template/2.6/"><br /><br />The xfa template is set based on the target version. However, it will be bumped up if the form contains features not supported by the target version. So to fix your problem, you need to find out which xfa 2.6 feature the form is using and disable it. See if there is any target version warnings in the Report palette.<br /><br />Does that help solve your problem?<br /><br />Hélène<br />Adobe Systems

[Former Community Member]

When I select 8.0 as the target version LiveCycle does not report any target version warnings.

[Former Community Member]

So what you are telling me is that Designer does not have to report all target version warnings and I have to figure out which feature I am using and disable it. Isn't Adobe Acrobat 8.0 the latest version...or is there another version that has been released. The form works perfectly fine in Reader - just not Acrobat.

[_Aandi_Inston_]

> Isn't Adobe Acrobat 8.0 the latest version...



No, 8.1.



Aandi Inston

[Former Community Member]

LiveCycle Designer does not give me any target version errors and there are still functionality issues when the target version is set to 8.0 and the .pdf is opened in Acrobat 8.0. Is this a bug and is there a fix....



One of LiveCycle Designer ES new features is to show "Target version warnings" and it is not working properly if it does not give me a warning for 8.0 but it still does not function properly.

[Former Community Member]

Can you be more specific about what is not working properly? We recognize how critical this Target Version Warnings feature is, and especially that it be both "complete" (always warn you about anything that won't work for your current target) and "accurate" (never warn you incorrectly)



Thanks

Mike