Hi toad,
As far as I can see the multiplier is creating the new elements with exactly the same name and id so you won't get valid data submitted - only the last one.
There may also be a problem that the datepicker is attached when the page loads - at which point the duplicate elements don't exist. You'd have to add custom code to run when the Add button is clicked and attach the datepicker to the new DOB input then.
Bob
Getting back to this subject, I'm still struggling to get the datepicker inside a multiplier to pop up the calendar. There's an obvious conflict somewhere that is causing the pop up not to appear inside the multiplier, but yet it appears outside of it. I've replaced the 'datepicker' inputs from Chronoforms and replaced them with textboxes with the class 'datepicks' and using this code in the page template:
<script>
$(function() {
$( ".datepicks" ).datepicker();
});
</script>
Refreshing the page gives no calendar pop up...at all. Loading Chrome's Developer Tools > Console displays no errors. Therefore, I'm unsure as to why the code is not working.
So I decided to add just one Chronoforms Datepicker inside the Multiplier (no class name, to prevent conflicts). Same result. No calendar pop up. But if I was to add the Chronofroms Datepicker OUTSIDE of the Multiplier, then that one datepicker works fine, but still no response with the secondary date picker inside the Multiplier using the '.datepicker()' function.