The cmdlet Edit-ChangeOrder within the Sample.SyncChangeOrders.psm1 module terminates with exceptions when:
-
passing the -AttachmentFullFileNames paramter and the according Vault Change Order already has Attachments:
ERROR: Ausnahme beim Aufrufen von "UpdateChangeOrder" mit 20 Argument(en): "180"
-
passing the -AttachmentFullFileNames paramter and the according Vault Change Order has no Attachments:
Ausnahme beim Aufrufen von "UndoEditChangeOrder" mit 1 Argument(en): "109"
(After assigning the $AttachmentFileMasterIds parameters default value to empty array, the passed files are attached to the specified Vault Change Order in both the previous situations)
-
passing an empty array to the -AttachmentFullFileNames or -AttachmentFileMasterIds paramter, the existing Attachments of the Vault Change Order are not removed
Similar issues exist even for the FullFileNames and FileMasterIds parameters beause the cmdlet terminates with exception when:
-
passing files to the -FullFileNames parameter:
Ausnahme beim Aufrufen von "UpdateChangeOrder" mit 20 Argument(en): "1013"
(After assigning the $FileMasterIds parameters default value to empty array, the passed files are associated to the specified Vault Change Order)
-
passing files to the -FullFileNames parameter a Vault Change Order that has no File Records does not become updated with these files
-
passing File Record associations to the -FullFileNames parameter that already exists on the Vault Change Order does not remove the not passed Files Records
-
passing File Record associations to the -FullFileNames parameter that already exists on the Vault Change Order:
ERROR: Ausnahme beim Aufrufen von "UpdateChangeOrder" mit 20 Argument(en): "1689"
-
passing an empty array to the -FullFileNames or -FileMasterIds paramter, the existing File Records of the Vault Change Order are not removed
~Weiss Martin
The cmdlet
Edit-ChangeOrderwithin the Sample.SyncChangeOrders.psm1 module terminates with exceptions when:passing the
-AttachmentFullFileNamesparamter and the according Vault Change Order already has Attachments:passing the
-AttachmentFullFileNamesparamter and the according Vault Change Order has no Attachments:(After assigning the
$AttachmentFileMasterIdsparameters default value to empty array, the passed files are attached to the specified Vault Change Order in both the previous situations)passing an empty array to the
-AttachmentFullFileNamesor-AttachmentFileMasterIdsparamter, the existing Attachments of the Vault Change Order are not removedSimilar issues exist even for the
FullFileNamesandFileMasterIdsparameters beause the cmdlet terminates with exception when:passing files to the
-FullFileNamesparameter:(After assigning the
$FileMasterIdsparameters default value to empty array, the passed files are associated to the specified Vault Change Order)passing files to the
-FullFileNamesparameter a Vault Change Order that has no File Records does not become updated with these filespassing File Record associations to the
-FullFileNamesparameter that already exists on the Vault Change Order does not remove the not passed Files Recordspassing File Record associations to the
-FullFileNamesparameter that already exists on the Vault Change Order:passing an empty array to the
-FullFileNamesor-FileMasterIdsparamter, the existing File Records of the Vault Change Order are not removed~Weiss Martin