Field SaveOptions not working!

HCL Domino Domino Forum
1

Hi,I need to prompt the user when he is closing by pressing ‘Esc’ or clicking on the ‘cross’ to close the document.

He needs to have the message ‘to save the document’…what i did is i have a field ‘SaveOptions’ already there in the document.In the queryclose event i put ‘@SetField(“SaveOptions”;“1”)’,still its not prompting the person,it just closes…when i checked the value of the Field ‘SaveOptions’ the field’s value indeed has changed form zero to one!!then why hasnt it prompted me??

Please help,thanking u in advance.

2

Subject: Field SaveOptions not working!!

Hi,

Please check if u r trying to save the document without making any changes. In that case, the user will never be prompted for saving the document when he tries to close the document even if SaveOptions is set to “1”.

Regards,

Dipen

3

Subject: RE: Field SaveOptions not working!!

Hi dipen,I did some changes…still its not working.

4

Subject: Field SaveOptions not working!!

You say you are setting SaveOptions = “1” in QueryClose.

But what is in your QuerySave?

5

Subject: RE: Field SaveOptions not working!!

The SaveOptions field lets you not prompt the user whether to save; you’re answering the question for them. The way to always prompt the user is to not have SaveOptions, and to modify some field after the document opens. But not in Postopen or Onload.

6

Subject: Field SaveOptions not working!!

Hi shamia,

Just adding to Andre Guirard’s comments, Let me tell a few points about “SaveOptions”:

a. By default notes prompts a user, whether to save the edits or not ? if he edits a document and hits ESC key or clicks the CrossMark(Close Icon) in the form to close it. So where is the need for “SaveOption” field?

b. SaveOptions field is only used to force a document to save/not save, without asking/prompting the user to save the document !

c. So i think, there is no need in using the “SaveOptions” field, for your requirement.

You can refer designer help for more info.

Hope that helps,

Jason.

7

Subject: RE: Field SaveOptions not working!!

“SaveOptions field is only used to force a document to save/not save, without asking/prompting the user to save the document!”

Nope. SaveOptions set to “1” will NOT force a save without prompting the user. The document will behave just as if no SaveOptions field was present.

8

Subject: Field SaveOptions not working!!

Hi,

‘SaveOptions’ field is a Reserved Field. And in addition it’s functionality will work only if you set it’s field type as Number.

So in this regard you need to write code as below,

‘@SetField(“SaveOptions”; 1)’,

instead of writting

‘@SetField(“SaveOptions”;“1”)’.

Let’s check the Domino Designer Help and try accordingly.

Bye.

Regards,

Abhishek SenGupta.

9

Subject: Field SaveOptions is NOT number field

Abhishek, please edit your comment and delete this piece of totally wrong information, before anybody picks it up and starts spreading this nonsense.

SaveOptions IS meant to be a text field (although Notes is pretty tolerant to using formulas like @SetField(“SaveOptions”; 1)).

10

Subject: RE: Field SaveOptions is NOT number field

Hi Harkpabst,

I know that pretty well, but while I tried it using values like “1” or “0” in Lotus Domino 7.0.0, it didn’t work properly; but it was ok with values 1 or 0 with everything else remained same.

Then what’s your explanation?

Regards,

Abhishek.

11

Subject: RE: Field SaveOptions is NOT number field

Without knowing your code, I can’t give an explanation.

But the fact that I never had any problems using SaveOptions in the documented way in any version from 4.5.5 to 7.0.3 indicates to me, that you most probably became a victim of some side effect caused by other parts of your (or your co-workers) code.