nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

FormAPI getValue for ReadOnly Field

Jeremy

TS552, Solaris

Hi,

We are trying to use FormAPI to getValue on a readonly field. ie this is what is in our DCT:
<item name="metadata">
<item name="id">
<label>Id Primary Content</label>
<description>Id Primary Content</description>
<readonly></readonly>
</item>
</item>

And using this code in the DCT:
<script>
<![CDATA[
function init() {
var item;
item = IWDatacapture.getItem("/metadata/id");
//item.setReadOnly(1);
alert("Value is: "+item+" getValue is "+item.getValue());
}
//Now do the initialization...
init();
]]>
</script>
However this returns a 'null' value in item.getValue().
But if we change our DCT to look like this:
<item name="metadata">
<item name="id">
<label>Id Primary Content</label>
<description>Id Primary Content</description>
<text></text>
</item>
</item>
And change our Javascript code to force that field to be readonly (uncommenting the following line from above:
item.setReadOnly(1);
Then it returns the correct value for that field. The field also shows up correctly as readonly.

I know this is a little bit of a way around it, but I couldn't get the value unless the field was initially a text field. Is this correct, or is there a better way of doing it?
Would there be any issues of this field ever being able to be edited by a user if the Javascript does not run?

Any advice here would be valuable.

Thanks,

Jeremy

Update! Just read the following in the FormAPI docs:
"The FormAPI does not support <readonly> items. It is anticipated that their use will be deprecated in future releases. "
So thats why it wasn't working.

Edited by Jeremy on 04/23/03 00:10 AM (server time).

Find more posts tagged with

Comments

Adam Stoller

Maybe it's me, maybe it's just your post - but I don't think you can have an 'item' nested directly within another 'item' as you showed - I think it has to be item->value->item, not item->item. At least that's my interpretation from looking at the DTD...

--fish
(Interwoven Senior Technical Consultant)

Jeremy

Thanks - good point but actually user error! I typed it in incorrectly!

<container name="metadata" combination="and">
<label>Metadata</label>
<item name="id">
<label>Id Primary Content</label>
<description>Id Primary Content</description>
<text></text>
</item>
</value>
</item>

Thats better, but that is how it has been all the time in the code.

Thanks.

Adam Stoller

Okay - I believe however that FormAPI can mark a field as readonly - though I don't have time right now to test this out, I think I recall doing this once before - perhaps it requires that the field not be readonly to begin with (in the DCT), but that on loading (or perhaps through interaction with another field?) you can denote that a certain field should be so marked.

Hopefully someone with more experience with FormAPI, or through your own testing, this can be clarified...

--fish
(Interwoven Senior Technical Consultant)

Whooops - just reread your original post - it wasn't the marking of a field as readonly which was the issue - it was getting the value from a readonly field - sorry - can't help you there - no time to play with it right now - the information you cited may be correct.

Edited by ghoti on 04/23/03 05:23 AM (server time).

Jeremy

Yeah Thanks Fish.

Thats the work around we came up with - to change all those readonly fields to <text /> and then at the begining of the init function in the FormAPI we set the value to readonly and then later when we read the value it is ok to be read.
Just a little strange thats why I was asking about it.

Thanks anyway.

Jeremy