J
jb
I have a standard Query+Submit IP form, attached to webservice passing dataset.
Some of the fields can be nil/null in the dataset/SQL. All is well whenever:
1. I have not yet queried to fetch a row into form for update ---
nil/null-allowed controls are editable
2. I have queried and fetched row, and these fields contained something ---
nil/null-allowed controls whicj contian something are editable
BUT:
3. I have queried and fetched row, and these fields contained nil/null ---
these controls are now NOT editable, at all
But my user now wants to enter soemthing into these control(s). Why are
they disabled? What do I do? I can sort of guess there's something about
the dataset XML not having included such fields when their value is null? I
have found a couple of references here to do with "xsi:nil", but don't
understand if that's the problem or what to do about it?
Some of the fields can be nil/null in the dataset/SQL. All is well whenever:
1. I have not yet queried to fetch a row into form for update ---
nil/null-allowed controls are editable
2. I have queried and fetched row, and these fields contained something ---
nil/null-allowed controls whicj contian something are editable
BUT:
3. I have queried and fetched row, and these fields contained nil/null ---
these controls are now NOT editable, at all
But my user now wants to enter soemthing into these control(s). Why are
they disabled? What do I do? I can sort of guess there's something about
the dataset XML not having included such fields when their value is null? I
have found a couple of references here to do with "xsi:nil", but don't
understand if that's the problem or what to do about it?