You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Save failed: {"fieldReferenceName": null,
"fieldStatusFlags": "none",
"errorMessage": "TF401320: erreur de règle pour le champ Travail restant. Code d'erreur : ReadOnly, InvalidNotOldValue. 2 erreurs supplémentaires se sont produites durant la validation de l'élément de travail. Corrigez toutes les erreurs, puis réessayez.",
"fieldStatusCode": 0,
"ruleValidationErrors": [
{
"fieldReferenceName": "Microsoft.VSTS.Scheduling.RemainingWork",
"fieldStatusFlags": "readOnly, invalidNotOldValue",
"errorMessage": "TF401320: erreur de règle pour le champ Travail restant. Code d'erreur : ReadOnly, InvalidNotOldValue.",
"fieldStatusCode": 16777218,
"ruleValidationErrors": null
},
...Same for Microsoft.VSTS.Scheduling.OriginalEstimate and Microsoft.VSTS.Scheduling.CompletedWork}
I think Aggragator CLI send all values in one query. It's possible to do intermediate save in rule?
The text was updated successfully, but these errors were encountered:
Sorry for the delay.
Well the SaveChanges method is public and can be called, but it would be my second choice. In fact it isn't documented.
My first choice would be to set the bypassRules flag except that you cannot set it independently but it is tied to the impersonate directive.
It is not a complex change but I do not have time at the moment, so if you can submit a PR, I would be grateful... or be patient.
I try migrate rule from the old Aggregator plugin. This rule aggregate effort from children to parent.
When a item has children, the effort fields is read only by custom Hosted XML process rule (fields["MyOrg.HasChildren"] == "true").
The Aggregator rule is 3 step
This is the old rule :
I write this rule to Aggregator CLI :
But this get the error :
I think Aggragator CLI send all values in one query. It's possible to do intermediate save in rule?
The text was updated successfully, but these errors were encountered: