Skip to Main Content

APEX

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

How to display a string with a special character # in Oracle Apex 4.2 text filed.

user12096102Jul 4 2016 — edited Jul 4 2016

Requirement : I have an interactive report where it pulls data from a table, when a user clicks on a column it has to show up the column value in a pop up window in Oracle Apex 4.2

   

We have implemented this requirements as follows converted the required column into Column Link with Target as URL, the URL field under column link will invoke the below function by passing the column value

javascript:callMyPopup('#PARTNAME#');

Here is the javascript defined at the page HTML Header section.

 

<script language="JavaScript" type="text/javascript">

 

  function callMyPopup (p_id) {

  var url;


  url = 'f?p=&APP_ID.:4051:&APP_SESSION.::::P4051_PDIS:'+p_id;


  w = open(url,"PartName","Scrollbars=0,location=800,resizable=0,menubar=no,width=350,height=150");

if (w.opener == null)

  w.opener = self;

  w.focus();

  }

</script>

 

The above function will invoke a popup page with a text filed P4051_PDIS by passing PARTNAME value to P4051_PDIS text field.

 

Everything is working as expected, except when the PARTNAME value has a special character HASH(#), the text filed is showing only partital string upto #.

   

For example below is the popwindow url with a PARTNAME string containing HASH

   

               http://dbweb-db-p.capgroup.com:7780/apex/f?p=102:4051:309688393005::::P4051_PDIS:Engine#125@BOX

   

In the above case the text field P4051_PDIS is displaying only "Engine" ignoring the rest of the sting

   

Any idea how to fix this issue?  it seems like the # is getting treated as some kind of special character

 

 

Thank you

Raj

Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Aug 1 2016
Added on Jul 4 2016
1 comment
987 views