Hello

I need to create a view-only version of a form, and then personalize out some of the fields.
I can create a new Function for this form in the Define Functions screen and then use the QUERY_ONLY="YES" to make it view only.
EG Existing form is called MYFORM1
My new function is called MYFORM1_VO (for view only).

I add this to my menu and it all seems hunky-dory.

However, when in this new version of the form i call up the personalization form, the function name at the top of the screen is the original form function (MYFORM1), not my new ready only version (MYFORM1_VO).
This means i cannot attach personalizations just to the function.

Is there a bug with this, or is there some devious configuration step that i have missed?

Curiously, i added some function level personalizations whilst in this screen and saved them.
When i go back into my view-only screen the personalizations do not fire, but when i go into the standard screen they do - proving that they are only attached to the original function.
As a further experimental step, i extracted the personalizations using FNDLOAD, edited the LDT file to change all references of function MYFORM1 to MYFORM1_VO and then uploaded them back in.
After this, the personalizations worked on my custom form but not the standard, but it still would not show them to me in the personalization screen!

Help!

Did the ldt upload work?

I ask because I have very recently been a victim of FNDLOAD's tendancy to withhold errors/warnings unless explicitly instructed to report them.

I found myself doing, for a concurrent program upload:

FNDLOAD <do-be-do-be-do> DETAIL_LOG=TRUE

wherupon some interesting issues were revealed, involving last_update_date comparisons of some things which were not expected to fail, but did! As an aside, this was fixed in the short term by adding the command line argument CUSTOM_MODE=FORCE (as recommended by Oracle Support)

The FNDLOAD is not the issue (which worked perfectly fine thank you for asking).
I did the FNDLOAD upload to test that you could hold personalizations at custom-function level - which you can.

Its just i cannot get the personalization form to show me the correct function name.

As a PS to the FNDLOAD (and not wanting to send this thread down another alley) i find the combination of UPLOAD_MODE=REPLACE CUSTOM_MODE=FORCE to do the trick in any situation