Re: (RDMLX) Change DD to label bug?
Posted: Tue Apr 29, 2014 12:34 pm
What is GENATTR?
I am guessing, since it has ROW%N references, that it must be a table?
The property setting FORM.FIELDS.GENATTR.ROW%2.VALUE.ITEM%1.TEXT implies that there is a drop down literally named ‘VALUE’ in row 2 of the table named GENATTR?
If yes – and VALUE is meant to be a label – then you are either sending out ITEM% properties against a Type=Label element – or the new form setting is wrong and they are hanging about on the client in the old form that is to be updated (note: the 'old/original form' only exists when newform=false).
If VALUE is not the dropdown or label in question – then the full name FORM.FIELDS.GENATTR.ROW%2.VALUE.ITEM%1.TEXT looks like it might be structurally incorrect?
I am guessing, since it has ROW%N references, that it must be a table?
The property setting FORM.FIELDS.GENATTR.ROW%2.VALUE.ITEM%1.TEXT implies that there is a drop down literally named ‘VALUE’ in row 2 of the table named GENATTR?
If yes – and VALUE is meant to be a label – then you are either sending out ITEM% properties against a Type=Label element – or the new form setting is wrong and they are hanging about on the client in the old form that is to be updated (note: the 'old/original form' only exists when newform=false).
If VALUE is not the dropdown or label in question – then the full name FORM.FIELDS.GENATTR.ROW%2.VALUE.ITEM%1.TEXT looks like it might be structurally incorrect?