Hi All,
I’ve a weird issue happening with preference passing in Hidden Command in Google Chrome browser.

I’m passing a preference value over a hidden command once a dropdown in the form is selected. Hidden command is raised using an invoke script on value change present in the dropdown.
The problem with this in Google Chrome is that the preference value gets appended again with a comma. This issue is not seen when using a command button.
For Ex. if i pass “123” as a preference value when the hidden command is invoked then the preference is shown as “123,123”.

Please find attached sample for the same.
The same works fine in IE8 and Firefox.
I know that Google Chrome is not supported by webMethods but any help on this is greatly appreciated.

We’re running on MWS 7.1.3.

Please let me know if any other info is needed.
GoogleChrome.zip (13.9 KB)

Thank you very much for posting an example project. Every time i run the portlet (using sysadmin) and in 8.2, i see the output: Preference value using Hidden Command is 10001

What are you seeing in your environment (using Google Chrome)? I wonder if you a bug was fixed in this area between 7.x and 8.x?

Regards,
–mark

I’m attaching a screenshot for your reference of the o/p that i see in 7.1.3.
Is there anything that can be done to make it work in 7.1.3?

https://higherlogicdownload.s3.amazonaws.com/IMWUC/webMethods/Files3/b9c53a3e5b2bdb13c408567e11bc44ab0530c786_2_999x748.jpeg 1.5x, https://higherlogicdownload.s3.amazonaws.com/IMWUC/webMethods/Files3/b9c53a3e5b2bdb13c408567e11bc44ab0530c786_2_1332x998.jpeg 2x" data-dominant-color="FAFAFB">

preferenceIssue.jpg2144×1608 154 KB

Thanks again for providing the clear repro case. It’s clear to me that this doesn’t repro on 8.x, so we would need to backport an official fix to get this working on 7.1.3.

However, since Chrome isn’t supported i won’t be able to get approval to backport that fix. If Chrome support is critical, i’d recommend escalating a request through your local SAG account Rep.

Regards,
–mark