I have modified the above using the xfdf Draft Arc Document however i am having
difficulty bringing it up due to an XML parsing error. Here is my modified
code.
<cfcontent type="application/vnd.adobe.xfdf">
<cfoutput>
<?xml version="1.0" encoding="UTF-8"?>
<xfdf xmlns="<a target=_blank class=ftalternatingbarlinklarge
href="http://ns.adobe.com/xfdf/"">http://ns.adobe.com/xfdf/"</a>
xml:space="preserve">
<f
href="#siteRoot#v#Session.versionID#/contact/forms/acord/#VarStruct.PDFURL#"/>
<ids original="7A0631678ED475F0898815F0A818CFA1"
modified="BEF7724317B311718E8675B677EF9B4E"/>
<fields>
<cfloop collection=#VarStruct# item="VarName">
<field name="#VarName#">
<value>#Evaluate("VarStruct.#VarName#")#</value>
</field>
</cfloop>
</fields>
</xfdf>
</cfoutput>
Is there something wrong with using that cfcontect type?
glossen - 30 May 2006 21:59 GMT
Im gonna post this resolution because I found absolutely no resources on this
topic on either google or adobe's site. Maybe because its so new. Anyways I
had 2 problems the first being none of my data from my xfdf converter was
getting on my pdf document. The resolution there came in digging through the
xml source. When naming a field and value in the xfdf file you cant just name
the field name like "date" you have to go through the whole tree of your
document: ..."F.P1.date"><value..." With that it sent my values over.
My second problem was now the data was going over but it only showed up if you
clicked on that field =(... so i had to go into Lifecycle Designer and
highlight the field and go to the Object tab then under to the field tab and
uncheck "plain text only".. even though the field was sporting a nice yellow
error icon it worked like a gem.
I hope this helps someone because this XML implementation of pdf is freekin
great!
- Aaron