Skip to Main Content
Forums

APEX

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Session state protection violation: This may be caused by manual alteration of protected page item

BaonergesJun 23 2020 — edited Jun 23 2020

Hi Everyone,

I am back with the age old question above. There are forum posts dating back to APEX 4 asking this. I want to keep the look of my radio groups and checkboxes while making them read only so hidden or display only will not achieve what I want. I got what I wanted by setting the read only property to always. This throws the error in the image below.

pastedImage_0.png

If I set Unwind Customer so it is not read only, it works. What is interesting is that the left side does not have this problem. I set all the items to read only on the left side and I can submit with no error. I am not manipulating any of these items. They are just there so that the left side and right side forms look the same. Initially users were supposed to be able to modify the entire right side but my end users changed their minds........ I'm sure they'll change their minds again so I am leaving everything as read only for now.

There is no debug message. Nothing comes on the console. I just get the error on screen. There is not javascript manipulating that data. Any help would be appreciated.

Comments

Matej D.

Change LOV property Automatic Skip to NO.

Regards

user5345

Dear Matthew,

Yes I have done the same, but still it is jumping to next column.

Please help me

Thanks,

user5345

Please some advise,

Thanks

Matej D.

Are there any triggers on the item with lov?

user5345

no sir, nothing is there

Matej D.

Forms version?

user5345

version is 10g

user5345

No reply from any one, please suggest me some idea.

Manu.

Dear,

without knowing the code, no one can help. How you are populating the LOV? what are the codes written in the KEY-LISTVAL triggers in item level, block level and form level?

Manu.

user5345

I dont have any tiggers for that item or block level, i have only LOV to the item.

Manu.

Dear,

Then can you post the properties of that item and LOV?

Manu.

user5345

pastedImage_0.png

pastedImage_1.png

pastedImage_2.png

pastedImage_3.png

pastedImage_4.png

pastedImage_5.png

pastedImage_6.png

This all the LOV and item property palette.

Thanks,

MLBrown

I notice you are using popup menus which I have only used one time.  Is there logic in the POPUP popup menu that could be causing this problem?  Maybe remove it from the property palette and try running the form again just to see if it behaves the same way.

Also, you don't show your form-level triggers.  Could there be a pre-text, post-text, when-new-item-instance, etc... trigger causing this behavior?

Robert...

Check Field level triggers like key-next-item or when validate item - if you have dont have then check block level. somewhere your trigger/code is telling to move next field. also best way to find references made to this field, so find all pl/sql with this field name and check...

user5345

pastedImage_0.png

No tiggers is there, it's a simple form,

ben_g

This is only a guess as your text on the image says: "When I select one of these and Enter, the cursor is going to the next column..."

You may be encountering the behaviour for the default key mapping of Enter.

https://docs.oracle.com/middleware/1221/formsandreports/deploy-forms/configure.htm#CACCGDGF

By default, whether deploying client/server or over the Web pressing the ENTER key takes the cursor to the next navigable item in the block. To override this default behavior it is necessary to modify the forms resource file to revise the key mapping details.

Modify fmrweb.res and change the Forms Function Number (FFN) from 27 to 75 for the Return Key. The line should be changed to the following:

10 : 0 : "Return" : 75 : "Return"

By default, the line is displayed with an FFN of 27 and looks as follows:

10 : 0 : "Return" : 27 : "Return"

This line should NOT fire the Key-Enter trigger since the Return or Enter key is actually returning the Return function represented by the FFN of 27. The FFN of 75 represents the Enter function and fires the Key-Enter trigger.

Mary2020

Set the property 'Automatic Skip' to no for both the text item and LOV.

1 - 17

Post Details

Added on Jun 23 2020
#apex, #apex-discussions, #form
8 comments
27,467 views