Skip to Content

Java WD drop-downs not working correctly

Apr 07, 2017 at 01:19 AM


avatar image

Hi all:

My company is upgrading from NW 7.0 2004s to NW 7.4 SP14. We've just recently gotten over a big challenge getting applications running GUI for HTML trans-iViews & Java WD applications requiring Classic Event Framework to live on the same portal server by using the following settings:

- Under Portal Content > Portal Users > Standard Portal Users > Classic Framework Page > Browser Document Mode, the Browser Document Mode setting is now “IE=EDGE”.

- Under each SAPGUI Report’s trans-iView, the ‘Default Document Rendering Mode’ is set to ‘Standard’.

We've done this because my company requires us to standardize on Internet Explorer 11, both on Windows 7 & Windows 10. Unfortunately, this has caused a number of serious Java WD UI issues (pictures attached), such as:

- drop-down boxes are now only 1-3 rows visible when selected, no matter how many values they contain, making it difficult to select, see and scroll between all possible values.

- input text boxes now overlap their description labels instead of being painted adjacent to them.

- within tables, 1st row dropdown values are the only ones ever displayed, even when selecting another row’s dropdown values, including when that lower row is the lead selection.

After reading, I thought the sap.valuesetlimit.maxondemand property would fix this, then realized that this doesn't control the default visibility of how many can be seen at once.

In Studio 7.0 you can can control the Size property of drop-downs by switching between Small & Standard, but after migrating all our Java WD code to NW 7.4, this value has been deprecated and is no longer under our control.

I'm out of ideas. Nothing like these ever happened in NW 7.0 portal servers. Have any of you experienced these or similar issues? Any suggestions for what we can do to fix them?

Please advise,


10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

4 Answers

Jun Wu Apr 07, 2017 at 07:22 PM

did u render wdj in standard mode?

Show 3 Share
10 |10000 characters needed characters left characters exceeded

Yes, I tried the WDJ iViews in both quirks and standards modes. All 3 problems still exist in both modes.


that is not what I mean

follow this, you have to inform wdj to render in standard mode.


Hi Jun: sorry for the delay; we had a major outage.

Unfortunately, setting the SapDocumentMode property didn't change anything. All 3 of the above issues are still with us.



Kiruthika S
Apr 11, 2017 at 12:54 PM


If you are using browser document mode in edge then all the application use standard

Refer below note:

1458799 - Limited supportability for IE8 and above in the Portal

1814711 - SAP applications iViews in EP: Rendering Modes



Show 1 Share
10 |10000 characters needed characters left characters exceeded

Hi Kiruthika:

As I tried to explain earlier we cannot use Browser Document Mode property value to IE=5, IE=EmulateIE7, because GUI for HTML trans-iViews that are also part of this same application will render incorrectly, specifically that F4 help and all inbox boxes are frozen and cannot be typed in, edited or changed.

We have standardized on IE11, but GUI for HTML trans-iViews & Java WD applications requiring Classic Event Framework must live on the same portal server.



Matt Fraser
May 08, 2017 at 10:42 PM

Hi Jonathan,

What release is your backend ABAP system? And, in your portal, have you tried using the Ajax Standards Mode Desktop instead of the Classic Standards Mode Desktop?

Beyond that, a couple other things to check, in your backend, in your WEBGUI and other "SAPGUI for HTML" based ICF services, set the GUI Parameter ~WEBGUI_NEW_DESIGN = 1. Also, have a look at Notes 2007142 and 2140417.

In your portal, in NWA, check Configuration -> Infrastructure -> Application Modules, filter on module, drill into component Common_Configuration and property Default value for Browser Document Mode and set the value to edge. You may find that for some iViews the portal will be sending documentMode=IE5 in the URL even though you think you're all in Standards mode if you don't do this.


Show 2 Share
10 |10000 characters needed characters left characters exceeded

Hi Matt:

Sorry for the very late reply; I gave up on getting a reply to my question 2 weeks before your message. Thanks again for getting back to me, but we figured out the problem.

Backend is HANA 1.0 SPS 12. We had to keep Classic Standards Mode Desktop because one of our Java WD apps required it. Because of this, we finally found an OSS agent who got us working with the following NW7.4 settings:

1. Under Content Administration > Portal Content Management > Portal Content > Portal Users > Standard Portal Users > Classic Framework Page, open the Browser Document Mode iView.

- Browser Document Mode: from IE=EDGE > IE=5, IE=EmulateIE7

2. Under Content Administration > Portal Content > (our company) > (our app) > Roles, open ('Our Supervisor') role. Under the ‘Role Content’ hierarchy, open the workset, then open the ('Report') iView underneath it. Set the following parameters:

- Default Document Rendering Mode = Standards

- Launch in New Window = Display in separate headerless portal window (standard mode)

Result: Good. History Report no longer paralyzed, but requires a separate popup window to continue using SAPGUI HTML.

Our team attempted these steps earlier but failed. The difference is that we applied Change (3) directly to the trans-iView, page, and workset definitions, but that was the wrong place! I’m not sure if this is because:

  • -our portal content was migrated from elsewhere
  • -a native NW 7.4 behavior
  • -something native to all NW portal versions

but when ('Our Supervisor') roles were created, the delta links we use when referring to our iView, page and workset definitions somehow don’t directly use those definitions, but use copies embedded within the “Role Content” hierarchy!! It’s here where we should’ve done our work. None of the documentation provided to us made that clear, but thankfully Edison from SAP knew better! I have replicated his steps in all (our company) portal roles, making the Change (3) settings to each page and iView definition tied directly to a workset being used within a given “Role Content” hierarchy.




Hi Jon,

Thanks for coming back to this with your eventual solution, although I'm not sure what you mean by "Change (3)," as I only see two bullet points in your solution list. I'm glad you got this resolved!

With your permission, I'd like to convert your reply to an "answer" so that it can be marked as the correct answer for others in the future. Or, I think you can do this yourself, if you prefer. And then we can close the question.


Asha Pillai
Nov 14, 2017 at 06:19 AM


Can you check if the note ##2430019 - Incomplete dropdown contents or incorrect position of dropdown in IE11




10 |10000 characters needed characters left characters exceeded