Trusted function still giving permission errors.

[kennethr3585991]

I wrote a function in a js file in the C:\Program Files (x86)\Adobe\Acrobat DC\Acrobat\Javascripts folder.

mySaveAs = app.trustedFunction(function(myForm, path)

{

     app.beginPriv();

     var myForm = event.target;

     return rtn = myForm.saveAs(path);

     app.endPriv();

});

I added a button to the form which calls.

mySaveAs(this, saveAsFile);

The console showsNotAllowedError: Security settings prevent access to this property or method.

App.beginPriv:15:Field Button1:Mouse Up

Is there something I am missing or doing wrong?

[Bernd Alheit]

What is the value of saveAsFile?

Remove the line var myForm = event.target;

[kennethr3585991]

saveAsFile is a string that is supposed to be the filename.

var saveAsFile = "/c/output/" + getField("LastName").value + ".pdf";

saveAsFile is ok (app.alert shows me what I expect it to be). I got rid of that line and still get

NotAllowedError: Security settings prevent access to this property or method.

The security settings in Adobe is set to "No Security"

[Bernd Alheit]

Try this:

mySaveAs = app.trustedFunction(function(myForm, path)

{

     app.beginPriv();

     console.show();

     console.println(path);

     myForm.saveAs(path);

     app.endPriv();

});

[try67]

It's not a good idea to have a variable called "path" because there's a built-in property of the Document object with that name. Try using something else.

[Thom Parker]

The security error is often a misnomer. I've seen this message popup when functions fail because of other reasons.

Did you remove the line of code Bernd suggested? this is an important one.

Are you sure that "myForm" is a document object?

Do you know that "path" is a Safe Path? and that it exists?

Can you do the same save operation from the Console Window, without getting the error message?

[George_Johnson]

See this tutorial: https://acrobatusers.com/tutorials/how-save-pdf-acrobat-javascript

[kennethr3585991 · Accepted solution]

I put the "trusted function" in a js file under the user folder, as opposed to the app folder and now it is behaving as expected.

[Thom Parker]

That's ridiculous.  I can guarantee you the location of the trusted function is not the issue. Are you sure it wasn't the "path" variable that try pointed out?

I would suggest that you move it to the App folder and see if the issue persists. Make sure its in only one of the two locations.