Dynamic Parameters in Portal Navigation with Web Dynpro

[gregory_hawkins1]

Hi everyone,

I was wondering if anyone has successfully passed a dynamic parameter into a Web Dynpro application via a portal iView. I have tried this several ways, but have not been able to ever get a dynamic parameter to be passed onto the Web Dynpro application. One of the Web Dynpro examples says that this is possible (Example 19), but I can't get the example to work either. (This example is distributed only as "slide ware" rather than an actual deployable project.) That example focuses around using WDPortalNavigation to pass in dynamic parameters and navigate within the Portal. The navigation works, but the parameters are not being received.

In a nutshell, I would like to know what does a URL need to look like when accessing an iView such that a dynamic parameter will be passed to the Web Dynpro application. I have tried various things using the NavigationTarget. The iView does receive the extra parameters, but only the built in display parameters ever seem to make it to the Web Dynpro application. Of course, when calling the Web Dynpro application directly on the WAS server, there is no problem passing the parameters.

Any help would be appreciated.

Thanks,

--Greg

[Former Member]

Greg,

One suggestion I was given in this regard was to append "app." for every parameter name. I couldn't verify this one. But did you try this?

Regards

Shakeel

[gregory_hawkins1]

Hi Shakeel,

Actually, currently no custom parameter passing is working through the iView onto the Web Dynpro application.

The app. feature is for passing parameters automatically to the startup plug as named parameters within a Web Dynpro application. (On my version this feature does not work either.)

Anyone else try this yet?

[gregory_hawkins1]

Hi All,

If the work around Sam suggests works, that's great. SAP for its part has acknowledged the problem and has inserted a fix starting in Service Stack 4.

Thanks,

--Greg

[Former Member]

Hi All,

The problem has been fixed with Stack 5.

Best regards, Karin