http://www.ep800.com Knowledge Management, Collaboration, SAP Unification Server Sat, 28 Nov 2009 04:54:55 +0000 http://wordpress.org/?v=2.8.5 en hourly 1 http://www.ep800.com/limitation-epcm-donavigate-does-not-support-special-chars-23.html http://www.ep800.com/limitation-epcm-donavigate-does-not-support-special-chars-23.html#comments Thu, 02 Jul 2009 00:14:19 +0000 admin http://www.ep800.com/limitation-epcm-donavigate-does-not-support-special-chars-23.html Symptom
An error ‘Page Not Found’ will be displayed when calling EPCM.doNavigate and passing NavigationTarget or NavigationContext that contains special characters that was encoded.
For example:
iView ID is: pcd:portal_content/~1
Performing EPCM.doNavigate(’pcd:portal_content/%7E1′) will be encoded to EPCM.doNavigate(’pcd:portal_content/%257E1′).
This behavior can be reproduced on every SAP NetWeaver Portal versions.
Other terms
Page Not Found, encoding, special characters, decoding, EPCM, doNavigate
Reason and Prerequisites
Prerequisites:
Every SAP NetWeaver Portal is installed.
Reason:
The reason is because doNavigate function performs encoding on NavigationTarget and NavigationContext, so if special character is passed already encoded, double encoding will be performed.
Solution
Avoid naming Navigation objects (Roles, page, etc…) with special characters (~,&,%,$, etc…).

]]> http://www.ep800.com/limitation-epcm-donavigate-does-not-support-special-chars-23.html/feed 0