Here are some articles that explain how to use JavaScript to show and hide fields, and on how to program dropdowns. https://www.pdfscripting.com/public/Hiding-and-Showing-Form-Fields.cfm https://acrobatusers.com/tutorials/change_another_field/  https://www.pdfscripting.com/public/List-Field-Usage-and-Handling.cfm https://www.pdfscripting.com/public/Checkboxes-and-Radio-Buttons.cfm     ... View more

To do this sort of thing you'll need to learn a bit about PDF form fields and scripting.  You can get started here: https://www.pdfscripting.com/public/PDF-Form-Scripting.cfm   ... View more

The backgroud color of an annotation or form field can be controlled with a script.  So for example, this validation script for a text form field controls the grayscale of a form field named "ColorPatch" Gray scale values are between 0 and 1 if(!isNaN(event.value) && (event.value >= 0) && (event.value <=1)) {     this.getField("ColorPatch").fillColor = ["G",event.value]; }   This technique can be extended to include shading for other color values.      ... View more

First, don't mess with threads in a plug-in. The plug-in environment is heavily controlled. It's not like a regular DLL. If you need something to run (sort of) asynchronously, use an Idle cycle.    Next, Acrobat also uses another annot to implement the popup comment for an annot. They don't delete it, just hide and show it on mouse over operations. It's not a bad model. But if you really do want to timeout the tooltip, use the ::SetTimer() system function.    BTW: I use Windows drawing functions for tooltips.  Register a draw procedure with Acrobat that is called anytime the screen needs redrawing.    ... View more

Is the checkmark itself orange? or is the bacground of the checkbox orange? If it is the check, then te checkmark you see is called the "Appearance", which, in this case is a vector graphic of the checkmark. There is also a set of parameters in the PDF that define how the vector graphic should be drawn. It is possible that InDesign created the checkmark Appearance one way, but didn't set the drawing parameters. In this case Acrobat may  recreate the Appearance. If it does, then it uses the (default) drawing parameters, which would result in a different appearance than the one created by InDesign.  I've seen a similar problem many times, many years ago. The InDesign team provided more appearances of form fields than were actually creatable through the form field drawing parameters. Whenever certain things change on the form field, Acrobat redraws the form field appearance. You have to think the InDesign team never actually tested this feature before releasing it.     This of couse is speculation.  If you really want to know you'll need to prove a sample file and more specific information.    ... View more

If this is an AEM form, then the question needs to be asked on the AEM forum.    ... View more

So there are a couple of problems with this script, neither of which is a syntax error.   Your syntax error is somewhere else.    The main error is this line: var field = this.getField(fieldName);   The field object is already available in "event.target".  But this doesn't help you either because the value of the field is not the value entered by the user, but the previous value. The validate script runs before the new entered value is committed to the field value.  To get the newly entered value use "event.value".    So, there is no need to pass the field name into the scirpt.    But the second problem is that your script seems to be intended for a form level validation. You see, the validation script is only run when the user deliberately enters data into the field. So if they leave the field blank, the script will never be run.        ... View more

An Adobe Sign form is really the best option, unless there are complex calculations involved.  However, just to answer the issue. The signature fields need to have different names.  They are all filling in because they have the same name.    ... View more

I wouldn't be too quick to get into the JavaScript language details yet. All procedural programming tasks require a specific set of tasks. Define those tasks and the implementation will follow.  This is what's called flowcharting.  The "if" statement in any language is the basic decision structure. And yes, there are always "if"s.   Dealing with dates and times can be a pain.  So it's best to simplify where possible.  An easy way to do this would be to parse the start date and end date into parts, month day and year.  If the start and end day are the same, then process only the times.  If they are different, then process the times to determine number of meals on those days.  Then calculate the number of days inbetween.     I'd do the start and end date time processing by converting the time to decimal number of hours, which can be then checked against the meal times.  And process the number of days in-between by converting the start date plus one day and the end date into date objects. Then find the difference between the two objects.     ... View more

So first, a calculation script it needed for this task.  Next, you've described a complex situation, so some thought needs to be put into the approach.  It sounds like you want to determine the number of meals attended based on arival and departure date/times. To do that a table of when meals start is needed.   To simplify, I would divide the calculation into three parts. The arival day, the departure day, and all the days inbetween.  The only days the student may miss meals are the arival and departure.         ... View more

A calculation script cannot use the field it is on, as input. The input has to come from somewhere else.  Let me put this a different way, once the entered value is changed, it's changed. There's no going back because there is nowhere to get the original value that was entered.  But that's not the real issue. Calculations are called everytime a field on the form is changed.  In your script, the field will keep halving itself.    So, the user needs to enter the value into a different field. Then the script will work.     ... View more

There are three possible solutions. #1  Flatten all the PDFs before combining. Flattening removes the fields, and puts the text in the fields into the document content. So it's still there, but not accessible or modifiable. Here's a link to a free flattener:https://www.pdfscripting.com/public/Free_Acrobat_Automation_Tools.cfm   #2  Rename the offending fields on each form.    A script can be made for this. The reason you'd do it this way is if you needed the field data to be accessible programatically.    #3  Combine files as a portfolio. This method uses the PDF as a kind of zip file. Each of the combined PFS are still separate documents.     ... View more

Two text fields with the same name are the same text field.  Your description doesn't make sense.  Please explain more of what you mean, in detail.    ... View more

As Radzmar implies, It's not the PDF, it's the viewer.  Try opening it in the Mobile Adobe Reader.  Or use HTML forms. \   ... View more

See this article: https://acrobatusers.com/tutorials/change_another_field/   ... View more

So first, there is no script in the "Nom" field. The script in this field should be set as shown by Tariq.  The 3rd field, places the name of the stamp file in the field, not the name of the file being stamped.  The document object for the file being stamped is in the  even.source.source property So the script should be    event.value = event.source.source.documentFileName.replace(/\.pdf$/,"");    BTW: Tariq did a fantastic write up. You should read it.      ... View more

Different type of JavaScript. Context is important.    ... View more

The answer is yes and no.  The 3D API is not well explained. Once you understand the overall structure of API it all makes sense, but you have to get there first.    So all events are set through the "runtime" object, which is a standalone global object.  First create a MouseEvent handler and then use the runtime.addEventHandler function to add it.  The Event handler object includes an OnEvent function that you add. This function is called anytime the user clicks the mouse on the 3D annotation.   The MouseEventHandler object provides a "target" property that reports the thing hit by the mouse.     The runtime object is inside the 3D scripting context. If you add your script directly to the 3D annotation, then that script operates in the 3D scripting context.  But if your script is on a regular PDF form field button, then the script is operating in the Document context.  The 3D context is acquired using the "this.getAnnot3D().context3D".  The "this" keyword is always the current context, which is why "getAnnot3D" was undefined. It was being used in the wrong context.    I'm an not crystal clear on all the details because I haven't done this in a very long time, but that's the basic method.        ... View more

That is correct. Missed it in the Ref.  However, if it's "undefined", then it is not being run from the document context.    ... View more

So, did you check the browser console window to see if any errors were reported?  The function is probably returning "Text"  because "jsAction" is not a string. Perhaps you should do some debug to figure out what type of animal it is?  Probably an object with some sub-parts that contain the actual JS code.     However, this is all irrelevant because this forum is for questions about Adobe Acrobat.  You'll need to ask about this on another forum, one that is for browser scripting.      ... View more

The function name is "getAnnot3D", no "s". Here's the reference entry: https://opensource.adobe.com/dc-acrobat-sdk-docs/library/jsapiref/doc.html#getannot3d   This function is meant to be run from the document context. For example, a button on the PDF. It also has two input parameters, the page number and the annot name. I suspect that both are required since the return value is the 3d annotation object.     You're code looks reasonable, i.e., there are no obvious syntax or structure errors and it follows the pattern I rember from when I was doing 3d programming in PDF.  However,  the JS model has be revamped since that time, so I couldn't comment on the specifics.     3D scripting is a highly specialized topic and requires spending some time learning the details. That said, your code might just work as is, once you fix the function name.            ... View more

So, clue #1, Read the manual, don't use ChatGPT   ... View more

You'll need to explain more. On what platform is this script being used? And using what SDK, library, or toolset?       ... View more

Strange isn't it. That the backlash against the new UX is universal amoung those that actually use it, and not only haven't the obvious errors been fixed, but there has been no move to make any real changes.  There is something going on here with Acrobat development.  I'm quite anxious to see where this goes.     ... View more

The sensible assumption would be that One Drive is not just storing the file, but modifying it. I suspect this has something to do with security settings, One Drive doesn't like JavaScript. To verify this, post a form that was saved and retrieved from One Drive, and we'll take a look at it. Post the file before and after.      ... View more