<g:ui_input_multiline_field> VS. <g:ui_input_field> ISSUES

[Money]

Has anyone ran into any issues when using one input type vs the other? I've created a dialog window on a child task that requires a user to input work notes. The value of the field after the user has input information is then processed via processing script and entered into the parent tasks' work notes field. Using the multiline_field, this does not work. However, using the regular input_field works just fine. The id from the work notes field is "work_notes". I can get the value using the regular input field by using var test123 = work_notes; in the processing script. I've included a gs.addInfoMessage to confirm that the value is actually being pulled. It doesn't work with the ui_input_multiline_field

[Michael Kaufman]

I also had trouble with

<g:ui_input_multiline_field>

. I used this instead:

<g:textarea id="your_field" name="your_field" cols="80" rows="5" />

If that doesn't work you can post your code here. With your code we can really look into why

<g:ui_input_multiline_field>

doesn't work.

Hope that helps,
Mike

[Money]

Thanks Mike. I actually did the as a workaround:



I just wanted to make sure I am not crazy! lol...

[lilianm_vel]

Hello Monroe,

You are not crazy, but there is still a better solution. The tags you are talking about use UI Macros that you can easily find on any SNOW instance. Strangely, in the ui_multiline_input_field UI Macro, in the textarea object, name is set to ${ref} which has no sense. if you change name=${ref} by name=${jvar_name}, then, the behavior will be the same as the input_field.

Hope this helps

[German Alvarez2]

Great Lilian!

Does Mr SNOW know this issue?

Best Regards!