I was able to pinpoint the parts of the form causing the malware detection engine to block the PDF. See highlighted parts in the snapshot below.Script Object: FormLocaleTable: posBodyOnly when I delete the both the script object "FormLocale" and table object "posBody" then the PDF attachment will go...

I was able to pinpoint the source of the problem... still need to narrow down even further. I deleted a recently added subform, and the malware detection didn't block the Dynamic PDF. This subform uses formcalc script with predicates as such: form1.subform[26].posBody.Row1.Cell1.list_repairs.total_r...

We have about half a dozen of Dynamic PDF Forms. The problem happens with exactly one and only one PDF Form Template, and it is a Dynamic Form. All forms have large amount of javascript, and it only happens with only one of them.Following is the error we get from Office 365 malware detection engine:...

Certain types of forms which are based on the legacy Adobe LiveCycle PDF Forms (xfa), when added as attachment, are being blocked by all Enterprise Email (of different companies). Personal email accounts (gmail for example) are not blocking such attachments.Just checking if someone has come across s...

In my case, due to overall licensing cost and industry standard issues with plugins compatibility with recent browser, we are migrating all forms to HTML5 with AngularJS.Tarek

Hi, I am facing the exactly same problem in a recent form. Any progress on this issue? Was it resolved?Tarek

Sorry Tussha for late reply.As a matter of fact, we stopped working on HTML5 under Adobe LiveCycle due to many limitations we have faced when we developed a working prototype. We are rebuilding now all forms in pure HTML5/Angular (AngularJS)/Javascript/CSS/Bootstrap.At this stage, I won't be able to...

I believe this thread may have the solution I am looking for: Tarek

Following the very useful sample provided here:Re: SaveXML and LoadXML problem I noticed that if you update the field values, then the data model is updated immediately, however, if you update the data model node values, then the bound field values are not reflected unless you execute xfa.form.remer...

After some research and troubleshooting, I found out that I have to comment out the line below in XML View:   <!-- <?originalXFAVersion http://www.xfa.org/schema/xfa-template/2.8/ v2.7-scripting:1?> -->Then, the problem just disappeared !!!!I hope this will be of help to others.Tarek