var str = doc2.getItemValueString('MyField');

or 

var str = doc2.getItemValue('MyField')[0]; 

Hopefully this is a copy problem:

declres a variable named "NotesDocument" (which is dangerous) of class doc ;-)

 

 

 ...thanks everyone, I tried these suggestions but it frustratingly doesn't seem to be that simple.  It seems that if I qualify the datatype of the var, like so:

 

    var NotesDocument:doc = database.getView('MyView').getDocumentByKey(unid);

 

It returns an empty document (i.e. the fields I'm expecting in 'doc' are empty) but doc is not null.  However, this line: 

 

    var doc = database.getView('MyView').getDocumentByKey(unid);

 

...successfully returns the data I am expecting, but when I try to call: 

 

    doc.save(true,false); 

 

...I get the exception:   Exception occurred calling method NotesDocument.save(boolean, boolean)

 

Unfortunately that is all the details the logs offer.

 

Looking at the API a little closer I see that "getDocumentByKey" returns a "Document" object.  The "Document" object  (interface?) in turn DOES NOT have a method "save(boolean, boolean)" - it doesn't seem to have any "save" methods.  This may be why when I make the variable of type "NotesDocument", the "save" method works - but the data goes away.

 

Questions: 

 

** - I am basing my javascript on working LotusScript from from a previous programmer (but am much more comfortable in javascript than LotusScript).

 ...I should add that I have searched on the exception and have found pages like this talking about an authentication problem:

 

http://lotusnotus.com/lotusnotus_en.nsf/dx/the-lesson-of-the-day-think-simple-while-debugging-xpages.htm 

 

...and I have verified that I am indeed correctly authenticated - so this is not the issue. 

I think you should use code like 

var doc:NotesDocument = ....  

that's all, you just had the wrong notation.

Thanks Mic Stone - I definitely had the syntax wrong.  That said, this wasn't actually the problem.

 

For those who get these following errors in the future: 

 

 

...what fixed it for me was how I retrieved the document.  Changing this:

 

 

...to this: 

 

 

...fixed the problem!