User Override Problem? - Answered!

MagarG

MagarG

VIP Member
Got a response back from JDE and this is how it is designed to operate.
It copies them to the user ID once you click on one of the tabs. Now if
the *PUBLIC is changed and needs pushed out again, you have to delete
all the users that clicked on one of the tabs because the search order
goes by userid first. Seems to me if users are not modifying the grids
and you have *PUBLIC, they should use the *PUBLIC record, not a newly
copied one. If the user just goes into the application and doesn't
click any of the tabs, no extra records get created. Doesn't seem right
but maybe I'm missing something...

========================================================================================
1. I go into Address book (P01012) logged in as USER1 (Administrator)
and create two grid formats, TEST1 and TEST2. I then copy these to
*PUBLIC and then delete the ones for USER1. Search for P01012 yields 1
GF record for *PUBLIC which is ok.

2. Log in as USER2, go to Address Book and I can see both grid formats.
Click on the TEST2 tab. Exit Application and then OW.

3. Log back in as USER1, go to User Override Application and do a
search for P01012. There are now two records, one for *PUBLIC and one
for USER2. USER2 didn't create any new ones or modify any existing ones
yet a record was created? Is this normal or a bug? Why would just
clicking on the tab you want to view add a record to the user overrides
table...

ENT: AS400 V4R5 OW Xe SP16.1
DEP: NT 6a SQL 7 SP3
JAS: Win2000

,gm



AS400 V4R5 Coexist CO-NT Xe SP16.1
Websphere 3.5.4 on AS400 JAS SP16.1
 
Hi there

We had a similar issue at SP17.1_H1 B733.2. I was advised by GSS in Denver that this issue is fixed in SP18.1, SP19 and B9 by SAR 5635443. (Orphaned record cause user override not saving). I read the SAR and queried it with them, and was advised that it also fixes the problem of it creating personalised formats if no "changes" are made by the user.

By the way, I have found that since moving from SP11.1 to 17.1_H1, user overrides have continued to be a real pain and don't appear to have gotten any better - they may have even got worse !

Regards
Ian
 
"By the way, I have found that since moving from SP11.1 to 17.1_H1, user overrides have continued to be a real pain and don't appear to have gotten any better - they may have even got worse ! "

Did you delete all User Overrides after applying SP17?

User Overrides after SP17 (or is it SP17.1?) use XML BLOB instead of Binary BLOB for storage. Apparently XML is less succeptible to corruption but you do have to delete existing UO's and recreate them, thereby utilizing the new storage format. If you don't clear them you will continue to have issues.
 
Back
Top