Hi everyone, I'm currently working through the Mendix Academy learning path (4.2.2 — Task Achieved and Missed logic), and I've implemented the microflow exactly as described: If both dates (DueDate, CompletionDate) are filled in: If CompletionDate <= DueDate, then set SLADashboardStatus = SLA_Achieved Else, set SLADashboardStatus = SLA_Missed This part of the logic works fine — I’ve verified the microflow with Change Object actions setting the enumeration values properly based on date comparison. ProblemWhen I open the app via View App, I cannot manually set a DueDate that is later than the CompletionDate using the date picker. It seems like the field or something in the logic prevents it — even though my comparison allows it. What I’ve checked: Both DueDate and CompletionDate fields are editable and have no validation or conditional editability. There is no validation type set in the field properties. The logic is correctly implemented in a microflow (not directly in the page). SLADashboardStatus is only changed in the microflow based on the date comparison. There’s no custom logic in the Date Picker fields directly. My suspicion:Maybe the microflow is being triggered too early (via an On Change event on one of the date fields), causing the comparison to run while the user is still selecting a value, which could rollback or prevent input.
asked
Jamal Naghiyev
1 answers
0
There's one more place that could have validation - have you checked the attribute in your domain model?