Google Apps Script前后端通信问题：提交按钮无响应求助

Hey Lucas, let's work through why your form submit button isn't firing the addRegistro function on either client or server side. Since you mentioned the core logic works in isolation, the issue is almost certainly a connection problem between the form, client-side trigger, and server endpoint. Here are the key things to check:

1. Confirm Form Submit Action is Linked to addRegistro #

Since you can't edit the client's script editor, focus on the platform's UI settings for the form:

• Many low-code/no-code tools require you to explicitly map the submit button to a function via their interface (not just define the function in code). If the button is set to a default action (like refreshing the page) instead of calling addRegistro, that's why nothing happens.
• Look for options like "On Submit" or "Button Action" in the form's settings—ensure it's set to trigger your addRegistro function, not a generic refresh.

2. Check Client-Side Function Accessibility #

Even if you can't edit the script, verify if addRegistro is in the global scope:

• If the function is wrapped inside a closure, module, or IIFE (Immediately Invoked Function Expression), the form's submit event won't be able to locate it. Some platforms let you register functions globally via their API for form triggers—check if that's required here.
• Open your browser's DevTools Console (F12), type addRegistro and hit enter. If you get undefined, the function isn't accessible to the form.

3. Inspect for Client-Side Errors with DevTools #

DevTools is your best friend here, even without editing client code:

• Go to the Console tab and submit the form. Look for errors like:
  • addRegistro is not defined: Confirms the function isn't reachable.
  • CORS-related errors: Means your server isn't configured to accept requests from the client's domain (you'll need to adjust server CORS settings).
  • Network errors: Indicates the request isn't even reaching the server.
• Check the Network tab to see if a request is sent when you submit the form. If no request appears, the client-side trigger isn't firing at all.

4. Validate Server-Side Endpoint Configuration #

Make sure your server is set up to handle the form's request correctly:

• Confirm the server's addRegistro endpoint accepts the correct HTTP method (almost always POST for form submissions).
• Check that the server can parse the form's data format—most forms send data as application/x-www-form-urlencoded or multipart/form-data. If your server expects JSON instead, it'll ignore the request.
• Verify the endpoint URL matches exactly what the form is targeting (typos here are a common culprit).

5. Rule Out Default Form Behavior #

Some forms perform a full page refresh on submit, which can abort the addRegistro call before it completes:

• Check if the platform allows you to disable the form's default submit behavior via UI settings (look for "Disable Auto-Refresh" or "AJAX Submission" toggles). Without this, the page might refresh before the function can execute or send data to the server.

内容的提问来源于stack exchange，提问作者Lucas Fernando