-
The easiest way to do what you want is to first create your condition on a field that is NOT in a preserve code block -- then look at the restulting XML and copy it to your field that IS in your preserve code block.
-
I think you might have missed drgkreddy's point... you don't have to write code if you use the built in date formatting.
If your field is of type ''date'' or ''date and time'' then you just need to go into the field properties (i.e. double click the control), and then on the Data tab, click Format. From here you can select how your generic date ...
-
You must use a 3rd party tool for this, or use InfoPath 2007 -- but even IP2007 will requrie a forms server to be installed on the backend, while the frontend is just a browser.
Otherwise, you will need to go through the DHTML work to make all the fields editable, etc., and tie into a backend storage system--not a pleasant thought!
-
Your explanation is somewhat confusing. Are you saying that the value 1 is sotred in B and the value 2 is stored in C, etc.? If so, where does Text1 and Number1 come from?
What it kind of sounds like you are asking is for the ability to have multiple tables bound to the same set of data nodes, and each table only showing a few of the fields. If ...
-
''Control stores duplicate data'' is not an error. It is only informational. It just means that you have more than one control bound to the same data node in your schema. Sometimes this is good.
This is just telling you that if you aren't careful how you present the duplicate field, that the user might enter one value into one copy and then ...
-
-
1. If your data is structured in such a way, you might not need to use the date. For example, if you always add new records at the end of the table, you would assume that the last row is your current appointment, that the second to last row (i.e. row[position() = count(row)-1] ) is the last appointment, and the third to last row (i.e. ...
-
What you can do is place your repeating table inside of a scrolling region. Place the headers outside, just above the scrolling region.
This way the headers are always visible, and the repeating table scrolls within the scrolling region.
-
That's great! I'm glad you got it working.
One tip for you on this topic: You don't need to actually have a field in your view in order to change its value. You can change the value of any field in your DOM regardless of whether it appears in any view.
Thus said, you don't need to have that text box ''hidden'' somwhere on the screen. You can ...
-
Great! Glad to have helped out!