Inputfields View are sometimes disabled

[Former Member]

I have a View with dynamic created Contextnodes and Inputfields.

I had to do so,because i get the Information about the Type and so on only at runtime.

The Metainformation are in a Tree structure.

Every element has some Information about a set of Fields.

At the first time I start the Fieldview of a Elemnent, it is all okay.

I can edit the Fields and save it.

I can close the Window an edit the element twice, also all things okay.

When I edit an other Element and then edit the first one, all my Inputfields are disabled.

I searched:

my Contextnodes have Elements,

my Inputfields are enabled after I have created it.

all looks fine.

Another strange thing in this case. When i add at Designtime a table

with other modelinfo to the Fieldview. I can select the a Table Item

and then my Inputfields are enabled.

Has anyone a Idea ,suggestion or a guess.

Thanks

Marlies

[Former Member · Accepted solution]

Can you please describe the exact context structure, context content at runtime and the binding of the UI elements?

"Schuss ins Blaue": Perhaps there is no node element selected at some times, you might set selection cardinality to 1:1.

Armin

[Former Member]

Hi Valery, Armin,

<b>I have solved the Problem.</b>

Next Time I ask earlier in this Forum.

Now I understood.

Let me tell

The Valuesnodes that I have created dynamic in the FieldView have as ParentNode

a Fieldnode. And this FieldNode has no LeadSelection.

Now the Valuesnodes have the rootNode wdContext and all works fine.

Thank you very much.

Now I solved it and understand it.

<b>The Forum is very good and fast to get the right Idea.</b>

In my Firm I have no one to discuss the my problems.

<b>Thank you very much!!!!!</b>

Message was edited by: Marlies Goeman

[Former Member]

Hier werden Sie geholfen

Armin

[Former Member]

Thanks Roelof, it was a guess and I didn't know that, but

...

I saw in my Code. I think I had done it right.

I added the node with this methode. I think the cardinality should be 1..1

IWDNodeInfo soNodeInfo = rootNodeInfo.addChild(NodeName,
null,//java.lang.Class elementClass
false,// boolean singleton
<b>true,// boolean mandatory
false,// boolean multiple</b>
false,//boolean mandatorySelection
false,//boolean multipleSelection
true,//boolean initializeLeadSelection
null,//java.lang.Object dataType
null,//IWDNodeCollectionSupplier supplier
null);//IWDNodeCollectionDisposer disposer

Any clues?

Your help is much appreciated.

Many Thanks,

Marlies

Message was edited by: Marlies Goeman

[Former Member]

Marlies,

1. Your node is non-singleton, hence it is a dependend node and parent node exists.

2. If you are using table and selecting row, are you selecting row in this parent node???

Sounds like lead selection in parent node is droped (i.e. no selection) under certain conditions, hence dependend node element is not available...

Valery Silaev

EPAM Systems

http://www.NetWeaverTeam.com

[Former Member]

Hi,

If the cardinality of a context node that is bound to an inputfield is grater that one (0..n or 1..n), then you get this behaviour.

So check if the cardinality of the context nodes bount to the input fields are 0..1 or 1..1.

Good luck,

Roelof