Is there a difference in how start_date, end_date, and duration are calculated in 5.2 vs 4.0?

Hi,

I’m in the process of upgrading to 5.2. Out of the box my index level 0 data has undefined for start_date, end_date, and 0 for duration.

I’m pretty sure these values were auto calculated based of its children dates before, because I’ve never seen this issue in 4.0. Were there some changes with the product?

Thanks,
testuser3

Hello,
Please try to reproduce it with the sample of your data in the following snippet:
https://snippet.dhtmlx.com/b3e34d9d5
After it is reproduced, click on the “Share” button and copy the link.

And please tell me exactly what issue you have.

Hi ramil,

It looks like my issue was actually with auto_scheduling_strict and task types. For some reason these break my index level 0 tasks start_date, end_date, and duration.

These worked for me in 4.0. Is there a reason why they would no longer work as expected in 5.2? Using pro edition btw so that’s not the issue.

Thanks,
testuser3

Hello,
I received your message in the support system. Let’s continue our discussion there.