Hi,
We tried adding a constraint date and a constraint type : "mustfinishon" on each task to lock the end date for each task, but it seems that bryntum is ignoring this can you please let us know if we are missing something?
Hi,
we are using the importer class that we found in this bryntum example (https://bryntum.com/products/gantt/examples/msprojectimport/) to push data into the bryntum store.
We tried the following to see if the dates would not change after getting imported:
We removed the calendar entirely but that didnt change anything
Based on your suggestion to use a no non-working time calendar we simply passed an empty array to the interval feild for all the calendars that we pass with the dataset that we get from mpxj but just made all the activities into one day activities (same start date and end date)
We over rode the following 3 fields inside the project model hoursPerDay = 24,daysPerMonth = 30,daysPerWeek = 7 and repeated the 2 scenarios mentioned above but the results were the same.
Since we are using nx framework for our application some of our configuration is in the application and some in the bryntum package that we are creating
I have provided the config in one of the previous responses in this thread here:
many cyclic dependencies that I need to disable again and again and still can't see data.
Screenshot 2023-06-02 at 12.48.28.png (95.62 KiB) Viewed 281 times
Could you please review it again? You can use our advanced demo as a base and replace launch-sass.json with your file. We have to find the way to launch an application and see the problem on our side to go forward with that.
Apologies for the delay in our response since we had been trying to create a sample codebase which is similar to our current code architecture so that it would be easier to test, replicate and isolate issues. Please find the repo below
Please run this code and you would see the forward scheduling issue we have mentioned.
We suspect that the reason the issue was occurring was because of the "commitAsync" function which would commit changes to the store, and because of the "add" functionality for the resource and assignment store.
Both of these functionalities have been tested on this codebase and we found the forward scheduling to occur whenever we call the "commitAsync" function or the "add" function even if we commit nothing.
you will find them inside the ganttInstance.ts file
path = {rootdirectory}\libs\gantt\src\lib\ganttInstance.ts
function name = initializeData
Line number = 60
We have also included the same dataset that we had shared earlier
The following tasks have been tested forward scheduling and you can use the same
Actually, I don't see any difference via initial dates and dates I found in taskStore after data loaded. I uncommented both parts of your the code you mentioned in previous post.
I checked all mentioned tasks, compared startDate and endDate values with listed in data.ts file.
Sorry, but I need some clarifications, what exactly do you see. Please post actual and expected result.
Try to add active: false for all dependencies to disable any potential affect. It should be already working as expected, but let's use all possible ways.
Make sure you didn't use endDate together with duration value in initial dataset. Because duration always have a priority if provided and endDate might be recalculated according to available time in active calendar.
If you have conflicts and auto resolving handlers, original data might be changed during conflict resolving and will have difference. Make sure you did nothing with data and data is fully valid.
Apologies for the confusion, it seems a part of the test code that was supposed to be removed before sharing the repo was left behind which is why you were not getting the enddate discrepancy issue, i would request you to take the latest pull since we have rectified the changes in the repo.
I have attached the results for your consideration.
Attachments
This is the scenario where commitasync was commented out
matchingdata.png (61.46 KiB) Viewed 230 times
this was the scenario where commitasync was not commented out
notMatchingDatapng.png (61.69 KiB) Viewed 230 times
Thanks for the update and patience. I see you set calendar for every task. When I removed this together with following steps from my previous message, I see it's working as expected.