Hello Nina,

We recommend you use ngModel, instead of value, to bind the date and time picker templates' inputs. ngModel does not just give you two-way data binding, but also tells you if the user touched the control, if the value changed, or if the value became invalid. The code should be similar to the following:

<input igxInput name="dateInput" [(ngModel)]="displayData" required />

<input igxInput name="timeInput" [(ngModel)]="displayTime" required/>

Please, review this approach and let us know if you need further assistance on this matter.

https://stackblitz.com/edit/angular-o4xsa9

I tried your suggestion, but that didn't work, since displayData is passed down from the igxDatePickerTemplate, but we need to bind to the date property in the ts file. So I experimented a bit more and came to the above linked stackblitz demo. The only problem remaining is that the first time picking a date, the field remains marked as invalid. This leads me to believe either I am still doing something wrong, or this could be a bug. Can you have a look and help me? 

If I understood correctly, you need to include the validation of the date & time pickers' values in the form validation but without binding them to the model. If that's the case I would recommend simply extending the submit button's disabled condition as shown in this sample (I used the first stackblitz sample you sent us, as the latest one seems to have some configuration error and I can't see it).

Here is the correct link for the current version of my problem: https://stackblitz.com/edit/datepickerdemo

What has been added is the requirement that the form is invalid and cannot be submitted if the endDate comes before the startDate. I wrote a directive for this and put it on endDatePicker (it doesn't fire when I put it on the endDate input field in the template). I can see the directive work because if we set startDate to today and endDate to some days ago, the submit button becomes disabled, and also there is some info being printed to the console. But the endDatePicker does not get any invalid styles. 

Thank you for your patience. If you want to avoid using ngModel on the inner date input which is how controls get registered with the form so they get validated appropriately, I can recommend manually updating the valid value of the input as shown in this updated sample application.

Please, let us know if you need further assistance on the matter.

It seems I misunderstood some things about the ngModel. I'm now using this on the inner date inputs which solves a few problems and drops the need for some workarounds. In fact I think I now got it working correctly except for one thing: When the form loads the date fields are immediately marked as invalid. Is it possible to have them empty but without being already validated, like the required name field? Here is a new demo. 

This last issue you are experiencing is caused by the fact the inner input is bound to 'displayData' and not to 'value'. In general, this should be perfectly fine, but our internal logic currently changes the editor's displayData property value to an empty string even when no date value is set which triggers the validation. We logged this issue and it will be resolved in the component in our next version. Temporarily, you may tweak a little your code in 2 ways, so it does not surface in your application. The two options are:

- Change the binding from [(ngModel)]="displayData" to [(ngModel)]="displayData || startDate";

- Bind to a custom property which formats the date as per your requirements.

Both approaches I implemented in this updated sample.

Please, let us know if you need further assistance on the matter.