Hi @ismcagdas, I've sent this demo project to [email protected] again.
Hi @ismcagdas, Were you able to reproduce the problem?
Hi @ismcagdas, I've resent the demo project to you.
Hi @ismcagdas,
I've upgraded to the latest version of asp zero hoping this issue would be resolved, but unfortunately it's still there.
I've created a demo project using the latest version that shows you this issue. This has been sent to info@ via WeTransfer. You should have received it now.
In this demo you can set Date1 to a date using the calendar pop up and then it should set Date2 to the same date. But it just sets Date2 to the same date for a moment and then Date2 reverts to null.
I tried the (dateChange) method you mentioned initially, but this behaved the same way in my production project.
Unrelatedly, I used the ASP.NET Zero Power tool to create this demo DateForm entity and it didn't insert into the app-navigation-service.ts correctly. It inserted "new AppMenuItem('DateForms', 'Pages.DateForms', 'flaticon-more', '/app/main/dateTest/dateForms')" at the top of the page, rather than within the AppMenu structure.
Hi ismcagdas, Thanks for the quick response.
I changed the HTML to:
<input required class="form-control m-input" type="datetime" bsDatepicker datePickerMomentModifier [(date)]="campaign.goLiveMilestoneDate" id="Campaign_GoLiveMilestoneDate" name="Campaign_GoLiveMilestoneDate" (dateChange)="changeDate($event)">
<input required class="form-control m-input" type="datetime" bsDatepicker datePickerMomentModifier [(date)]="campaign.effectiveGoLiveDate" id="Campaign_EffectiveGoLiveDate" name="Campaign_EffectiveGoLiveDate" [@openClose]="highlightEffectiveDateOnChange ? 'open' : 'closed'">
and the TS to:
changeDate(event) {
this.campaign.effectiveGoLiveDate = event;
}
This has the same result unfortunately. The date that appears within the id="Campaign_EffectiveGoLiveDate" flickers between it's original default value and the new value.