URL problems when change application language to Spainish

Question

Using APEX 3.1.2
Our application is usually in English. For a quick test we've changed the application language to Spainish through the 'Globalization' part of 'Shared Components'. Things look OK, the date pickers are showing the correct language and the NLS numeric characters are as expected - except... some page branches (from buttons, etc.) are no longer working correctly. It appears to be related to timestamps being passed across, they seem to be interpreted as multiple parameters!
E.G. in the URL http://my_box/pls/apex/f?p=2000:5002:4461616080789919::NO:RP,5002:P5002_CALLING_PAGE,P5002_TS,P5002_ID,P5002_DT:5001%2C10-DIC-09%2006.00.00%2C000000%2C181618172273744521291303312596297592589%2C10-DIC-2009&cs=392CF7A0393244530EC469114C4996A8E
the fractional seconds of the parameter P5002_TS is being received by the third parameter, P5002_ID, etc.
What am I doing wrong?

Answer 1

Andy Hardy wrote:
Using APEX 3.1.2
Our application is usually in English. For a quick test we've changed the application language to Spainish through the 'Globalization' part of 'Shared Components'. Things look OK, the date pickers are showing the correct language and the NLS numeric characters are as expected - except... some page branches (from buttons, etc.) are no longer working correctly. It appears to be related to timestamps being passed across, they seem to be interpreted as multiple parameters!
E.G. in the URL http://my_box/pls/apex/f?p=2000:5002:4461616080789919::NO:RP,5002:P5002_CALLING_PAGE,P5002_TS,P5002_ID,P5002_DT:5001%2C10-DIC-09%2006.00.00%2C000000%2C181618172273744521291303312596297592589%2C10-DIC-2009&cs=392CF7A0393244530EC469114C4996A8E
the fractional seconds of the parameter P5002_TS is being received by the third parameter, P5002_ID, etc.
What am I doing wrong?Even more confused now!
Just created a quick test app: table has timestamp, number and varchar2 fields - another number field is used for the primary key and has a matching sequence. Populated the table with various acceptable values. Created two pages using form-with-report wizard - changed all fields to 'text' to get rid of problems with datepickers not liking timestamps. Created another page with an HTML region containing items to match those on the form. Used button wizard to add a 'go' button on the form page to go to the HTML page, modified the branch to populate the HTML region items with those from the form.
Run the report page, see the expected results, 'edit' to go to the form page, see the expected values. Press the 'go' button, goes the HTML page... the timestamp field is not populated correctly - the value is truncated at the fractional sections part i.e. where the '.' would be. Depending on where the timestamp appears in the URL, the following items will also not be populated. For example, here:
http://loordv01.ad.dom/pls/apex/f?p=115:2:4046922604148424::NO::P2_TS,P2_ID,P2_VAL1,P2_VAL2:10-DEC-2009%2000:00&success_msg=Action%20Processed.%2F6E98BFC3726F8950ADF64DADBB5E0A87%2F
The timestamp is the first field on the URL and none of the other values appear...
I seem to be able to workaround this by having a PL/SQL process that just sets the called screen TS value directly i.e :P4_TS = :P2_TS - any pitfalls with this approach?