Does anyone know of any issues with using Date fields within a repeat control? I’m having an issue with them but if I change them to text fields, it works perfectly. Shame the application really really needs date and time fields though :).
The error is occuring on the save and I’m using the tablewalker assistance.
-
Date field in repeat & text in notes form = HTTP 500 error
-
Date field in repeat & date field in notes form = HTTP 500 error
-
Text field in repeat & date field in notes form = success
-
Text field in repeat and text field in notes form = success
If anyone can assist - thanks !
Regards
Steven
Subject: Is it possible you coded the date field wrong?..
-
This is a stab in the dark at best, but typically HTTP 500 errors occur when the XPage has run-time code it can’t execute. Since the date fields are all that change to create the error, it sort of implies some manner of error in the date field. “Coding” may not be JavaScript, it could be you have a dateconverter on it that’s not set right, or something more subtle.
-
My experience with date fields is they are pretty much simply text fields with an automagic converter applied. In fact all of my date fields look like this:
<<xp:inputText value="#{dataSource.fieldName}" id="fieldName"
styleClass="dateBox">
<xp:dateTimeHelper dojoType="dijit.form.DateTextBox" />
<xp:this.converter>
<xp:convertDateTime type="date" dateStyle="short" />
</xp:this.converter>
</xp:inputText>
If you take out the helper and the converter you have a text field left.
Hope this helps…
Subject: repeat control date error reponse
Hi
Thanks for your input. I’m using the default and basic date input with no extra functions or coding etc other than the grouping for the repeat group. I’ve had another guy try it in another app and he came up with the same result as I did.
<xp:inputText id=“callDate”>
<xp:this.value><![CDATA[#{callGroup[2]}]]></xp:this.value>
<xp:this.converter>
<xp:convertDateTime type="date"
dateStyle="short">
</xp:convertDateTime>
</xp:this.converter>
</xp:inputText>
I wonder if it can work in a repeat control.
Subject: I’d take out xp:this.value and see if it works then…
Subject: taking xp:this.value out
Hi
I took the xp:this.value out and it still doesn’t work, but as it’s part of a repeat, I wouldn’t be saving all the respective fields back to the document so I’m not sure that it’d be erroring for the same issue.
Subject: Shot my wad…
- It was a guess based on the fact that everything between yours that fails and mine that doesn’t is the same, except xp:this.value. I presume you’re still getting the Error 500, not something else, in which case I’m outta ideas.
Sorry I couldn’t be more helpful…