[ANSWERED] Assignment Sync: "updated" before "added"

[Jerther]

Hi!

Here's a simple Gantt:

import {Gantt, ProjectModel} from './gantt.module.js';

const project = new ProjectModel({
    autoSync: true,
    transport : {
        load : {
            url : 'data2.json'
        },
        sync : {
            url : 'sync',

        }
    }
});

new Gantt({
    adopt : document.body,

    project : project,

    columns : [
        { type : 'name', field : 'name', width : 250 }
    ],
});

project.load();

And here's the data:

{
	"success": true,
	"tasks": {
		"rows": [{
			"id": 2,
			"name": "AC8001 - Cavendish inc. - Fries depot",
			"children": [{
				"id": 3,
				"name": "Production",
				"duration": null
			}]
		}, {
			"id": 38,
			"name": "New task 1",
			"startDate": "2020-03-31 04:00:00",
			"endDate": "2020-04-13 04:00:00",
			"parentIndex": 3
		}]
	},
	"resources": {
        "rows": [
            {"id": 1, "name": "Doris"},
            {"id": 2, "name": "Stephen"}
        ]
	}
}

Edit a task and add a resource. Before hitting save, watch the network activity for the sync call. Hit save and examine the data of the sync call.

Here's what I get:

{
	"type": "sync",
	"requestId": "15863626625212",
	"tasks": {
		"updated": [{
			"effort": 13,
			"id": 38
		}]
	},
	"assignments": {
		"updated": [{
			"event": 38,
			"resource": 1,
			"id": "_generated_0x15cf271"
		}]
	}
}

Nevermind the "tasks" node and check the "assignments". Seems a bit odd, I was expecting a "added" subnode with a $phantomId!

Using Gantt v2.1.0

[saki]

Thank you very much for reporting the issue. The ticket is here: https://github.com/bryntum/support/issues/527

[Jerther]

Thank you saki, I'll follow the Github issue!

[Jerther]

Is there a workaround until this is fixed?

[pmiklashevich]

There is no known workarounds for now. The issue has high priority and going to be fixed in the next release. Please stay tuned.

[methode]

Hello all,

I got this issue too. I hope it will be fixed soon.

Thank you

[pmiklashevich]

Hello,

The issue is solved and you can find the fix in our nightly builds! Also the fix will be a part of the next release!

Cheers,
Pavel

[methode]

Hello Pavel,

fine, thanks

[methode]

Hello,

I found that the bug is related also to the successors and predecessors items.
I'm working with Angular.

Can you please verify it?

Open task in edit, no successors or predecessors are defined.
Add new successor, the request sends the newly created dependency in the updated collection instead of the added one.

Please, check the image attached.
Let me know if I have to open a new post.

Thank you

[pmiklashevich]

Yes, confirm! The fix fixes both cases!