on 08-02-2010 7:47 AM
Hi,
I have added couple of new drop down fields (from the ISR controle) to my form and have bound them to generic services in Form scenario to populate them.
Now here is one wierd situation if I test it from backend (tcode HRASR_TEST_PROCESS) those fields gets the proper values and if I test the same process from Portal with the webdynpro application those fields have only three values "true, false, unknown". I have tried to delete and add those again to form and reactivate it. But still the same problem. My other dropdown fields work well though. Only these two new ones have this problem.
Looking for some help.
Thanks,
Amit.
Hi Chris,
Ran into similar issue with another Adobe form.
But this time no matter how many times I add "$record." instaed of "$."in the binding ($.WERKS.DATA[*].field), it disappears. And now none of the dropdowns are working in another Adobe form.
Does ALC 8.2 have to do something with it?
Now if the binding shows "$.WERKS.DATA[*].field", how should I specify the list items . It needs three inputs.
Binding = same as "$.WERKS.DATA[].field" ? or $.WERKS.DATA[] or $.WERKS
and since the field catalogue and actual list items are attached at runtime how do I specify other two inputs "Text" and "Key".
~Amit.
Edited by: Amit Molekar on Aug 11, 2010 7:14 AM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Amit,
Did you resolve the "But this time no matter how many times I add "$record." instaed of "$."in the binding ($.WERKS.DATA[*].field), it disappears. And now none of the dropdowns are working in another Adobe form." issue, as Im having exactly the same problem - $record is getting replaced.
Thanks,
JP.
You bound the control to your form field. But you did not bind the actual drop-down list to your help values. Check it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Chris.
Actually I had checked everything about those fields and found out that the binding showed "$.WERKS.DATA[].field" instead of "$record.WERKS.DATA[].field". I never typed it, i had used that kinda binding F4 help.
I think recent update to ALC 8.2 might have to do something with it.
But it was resolved when i manually corrected the binding.
~Amit.
PS: your blogs have helped me a lot in the past (and surely will in future).
User | Count |
---|---|
88 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.