0

So I'm currently working on the gui of an item checkout system that runs within a spreadsheet. It does everything it's supposed to and isn't returning anything null, usually I'd be really happy with how it's turning out.

However, I keep getting "error encountered, an unexpected error occured" whenever I press the submit button, after that the rest of the code runs as expected. Every once and a while I'll get no error, but the vast majority of the time it throws the error.

function onOpen() {
  var ss = SpreadsheetApp.getActiveSpreadsheet();
  var menuEntries = [{name: "Equipment Checkout", functionName: "testing"}];
  ss.addMenu("Equipment Checkout", menuEntries);
}

function testing(){
  var app = UiApp.createApplication();
  app.add(app.loadComponent("ImprovedCheckout"));
  var doc = SpreadsheetApp.getActiveSpreadsheet();
  doc.show(app);
}


function submitted(e){
  Browser.msgBox(e.parameter.requestor);
}

This is the simplest version of my code. I'm using the gui builder to create the gui and I'm also using it to make the event handler. I've been banging my head against the wall for the past hour because it seems like the error is happening before the first line of submitted(e) but it doesn't occur until I actually click the submit button. It doesn't happen every time but it does happen the majority of the time.

I imagine I'm handling events from the builder wrong but there is oh so little information on that feature yet.

Improve this question
3
  • You said that this is the simplest version of your code. Does this error happen when you use the code exactly like this? Please test it again to answer (do not make assumptions). Commented May 15, 2012 at 17:13
  • I just did again, refreshing all pages and I double checked all inputs. Are you saying that you got this to run without error? Perhaps I should just scrap everything and start anew... Commented May 15, 2012 at 18:55
  • yeah, I came across a post earlier that mentioned that, no luck :( Commented May 15, 2012 at 19:23

4 Answers 4

Reset to default
1

I've seen this error happen when people set two handlers for the same button. Normally one via the GUI editor and another on the code. One works and the other fails. Which gives this crazy impression that it throws an error and yet works.

But since you said this is the exact code you're using. Are you setting multiple handlers on the GUI builder? I don't know even if that's possible, I never use the GUI builder.

Improve this answer
Sign up to request clarification or add additional context in comments.

3 Comments

I think you're on the right track. I just deleted a few function calls that weren't supposed to be being called but I guess somehow they were. Now I'm unable to repeat the problem. I think I'm going to start slowly adding my more complex things and try to figure out what's causing this.
But the approach is still valid, start small and add things slowly, always testing between iterations, until you identify the problem. If you can't, I recommend you to not use the GUI builder, since we can't help you with it (there's no debug, or any way of sharing it with us).
sigh, yeah that's pretty much what I think I'll end up doing. That was what I originally had working but it always looks so BAD when I code it by hand...
1

FIGURED IT OUT! Instead of using a submit button, I changed it to just a regular old button. It looks like the submit button was trying to run something else at the same time.

It looks like submit buttons have some additional rules and requirements but for the time being, I'm just using a normal button.

Improve this answer

2 Comments

Oh! Indeed, the SubmitButton does not need a callback element, or even a handler. It's supposed to be used with a FormPanel and always calls the doPost method on your script. If this is not your usage, stick with the regular button. Nice catch!
ahhhh, I thought it was strange when they required it in a form panel. I really wish they had more of a tutorial for the UI stuff.
0

I have had no issues running the code you have supplied. Two things to mention that are key:

  1. Make sure that you're adding a callback element to the ServerHandler with the HTML name of "requestor" as you are using in code.
  2. When you add the callback element, use the ID in the GUI editor. Name != ID

Both Name and ID need to be set in this example.

Improve this answer

1 Comment

I do want to reiterate, it IS working. I have labeled everything properly (I did notice the name and ID fields, I'm using both and they both are using the same name) The problem is that it's also throwing out a "error encountered, an unexpected error occured" error 2/3rds of the time as well.
0

I have got this same error message when using getElementbyId('id") and having a wrong value as ID. The script itself don't really stop and everything might seem normal apart from the action this specific call is supposed to do (but this is not always 'obvious')

Improve this answer

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.