The field configuration is different for the fields that do not print -
you need to complain to the author of the file. Here is how the fields
that do print are configured:I selected the second field in the 13B row,
and the "Presence" setting shows "Visible". Now let's do the same for a
field that does not print:As you can see, "Presence" now is set to
"Visible (Screen Only)" - that means that the field will not print
(valid settings for Presence are "Visible", "Visible (Screen Only)",
"Visible ...
As Bernd mentioned, this is not an AcroForm, but a form created with
LifeCycle Designer. I will move your question to a more appropriate
forum. One thing you can do to make it easier for the experts to help
you with your problem is to make a filled out for available that shows
the problem. You can upload it to e.g. the Adobe Document Cloud, and
then share the link here. See here for more information about how to do
that: Share Documents via Adobe's Document Cloud - KHKonsulting LLC
The printable/non-printable property is on a per field basis, so just
because other field are printing OK does not mean that some of the
fields may not have a different configuration. With the free Adobe
Reader, you cannot view the filed settings, nor can you modify them, so
the author of the form is the only one who can actually help you.
Yes, even tough I don't think there is anything different between
enabling the form in Acrobat X vs. Acrobat DC. It all comes down to the
license that allows you to do that.
You mentioned that you are using Acrobat X - that version does have the
500 form limit. Acrobat DC no longer has that limitation in it's EULA.
You can check for yourself (or have your lawyer check) by reviewing the
Acrobat X EULA and compare it with the Acrobat DC version.
You've posted in the Acrobat JavaScript forum, but your problem looks
like it's related to LiveCycle Designer. I suspect that you are using
JavaScript code, but the language type is set to FormCalc and not
JavaScript.I've moved your question to the LiveCycle Designer forum.
Dean,As I mentioned before, the error message points to the
resolveNode() call returning null because it cannot find the field name
you've specified. In XFA forms, it's important that you know where your
fields are, relative to where you want to use them.I would suggest that
you let Designer figure out how it can "get to" the field in question.
You can do this by using the following approach.The line that is not
working is as follows:var cCCAddr =
xfa.resolveNode("ClientEmail").rawValue;Remove t...
This error message indicates that the script has a problem getting the
value of the field ClientEmail - this is not related to your overall
email issue you had when you started this question.
This again is a problem that has nothing to do with the original
question.I wish I could spend more time on your problem, but I am in the
midst ofracing agains a deadline. Your chances of getting somebody else
to chime inare much higher if you post a new question.
Again, what you describe sounds like you are running this in Reader and
not in Acrobat. Most of these error messages are about a validation
event. I would recommend that you post a different question about these
errors, they don't seem to have anything to do with your original email
submission problem. This way, you may get some new eyes on your problem.
This sounds like you are running the free Reader, and not Adobe Acrobat
Pro. When you go to the "Help" menu and look at the "About" option, what
does it say?
Does this happen on both Acrobat and the free Reader? if it also happens
in Acrobat, then open up the JavaScript console (Ctrl-J) and look for
error messages. If it only happens in Reader, open up Reader's
Preferences, go to the JavaScript category and enable "Show console on
errors and messages".Exception handing in JavaScript is nothing specific
to Acrobat, it's just standard JavaScript. Here is some information
about how to do that: https://www.w3schools.com/js/js_errors.asp
No need to distribute, just attach the reader-enabled file to an email
or upload it to a web page. When you "Distribute", Acrobat will actually
try to reader-enable the document as well. The script is form specific,
because it is trying to get information from certain fields. If these
fields are not there, you will have to either adjust the script, or make
it resistant against missing information. You can do that using a
try/catch exception handler.
Sorry for the delay, but participating here in the forums comes after
family, work, eating and sleeping, so sometimes it takes a bit longer
until I can reply I assume this is happening in the free Reader. The
reason for this is that even though recent versions of the free Reader
can fill and save AcroForms (the type of form you create in Adobe
Acrobat), XFA forms (the ones created in LiveCycle Designer) are not
supported by this "free" feature. You will have to reader-enable your
form in Adobe A...
There is noting wrong with your form, this is just the way XFA forms
(the kind produced by LiveCycle Designer) behave when you try to open
them in a PDF viewer that does not support this "flavor" of PDF
document. Chrome and FireFox now come with their own PDF viewers, and
the only way to turn them off is to have the browser open the PDF file
in an external application. See here for more information: Take a look
at these pages, they contain Adobe's troubleshooting tips for problems
with PDFs in t...
You are using an email submission button - which sounds like the right
thing to do, but in this case that's wrong: The stock email submission
button is a one-trick pony, and it does exactly what it's designed to
do: It submits the form to the email address you used when you first set
up the form. As you may have noticed, you cannot add a "click" handler
to this button (and I assume that's the reason why you added the script
as a mouse-up event handler), because it's already hard coded to do that...
I tried to send you a direct message with my email address, but the
forum software is not cooperating right now. When you click on my name
in blue just above this comment, you can find a link to my web site,
which has my email address in the lower right corner. I cannot promise
that I will get to your document right away - my paying customers always
come first.
This looks like this document is part of a "distribute form" workflow.
This means that you are very likely not even running the script that is
associated with the button. BTW: You should see some output on the
JavaScript console. There are a few "console.println()" commands in my
code to print the field information retrieved from the form. If you
don't see that, the script is not running, and therefore you are not
getting any of the behavior programmed in it. Are you using the
"distribute form" ...
So again my questions: Do you get any errors on the JavaScript console?
What do you see in the "CC:" field in the email that arrives at the
"To:" address?
There is no screenshot attached to your reply. You cannot attach images
when replying via email. Just log into the forums system and then use
the "Insert Image" button:
Maybe the forum system is removing information - do you have anything
between "(" and ")"?This is copied from my original
post:event.target.mailDoc({ bUI: false, cTo: cToAddr, cCc: cCCAddr,
cSubject: cSubLine, cMsg: cBody, })
Are you getting any errors on the JavaScript console (Ctrl-J or Cmd-J)?
Is it possible that the field names I am using are different than the
ones you are using?
When you look at the email header of the email that you receive, what is
in the "CC:" line? Does it also fail if you only have one email address
in the "CC" line (meaning, you are not specifying a beneficiary email
address)?
