Invalid field object error

[daarkarcher]

I'm attempting migrate a small number of work items from on prem azure devops (source) to cloud azure dev ops (target).
I'm facing one particular issue which I cannot resolve - there is a custom field (called Locked) in the target project which does not exist in the source project, this results in the following error

[21:21:09 DBG] TfsExtensions::SaveToAzureDevOps: ChangedBy: AAA, AuthorisedBy: BBB [21:21:09 WRN] Work Item is not ready to save as it has some invalid fields. This may not result in an error. Enable LogLevel as 'Debug' in the config to see more. [21:21:09 DBG] -------------------------------------------------------------------------------------------------------------------- [21:21:09 DBG] -------------------------------------------------------------------------------------------------------------------- [21:21:09 DBG] TfsExtensions::ToJson [21:21:09 DBG] Invalid Field Object: { "WorkItemId": 0, "CurrentRevisionWorkItemRev": 0, "CurrentRevisionWorkItemTypeName": "User Story", "Name": "Locked", "ReferenceName": "Custom.Locked", "Value": "False", "OriginalValue": null, "ValueWithServerDefault": "False", "Status": 14, "IsRequired": true, "IsEditable": true, "IsDirty": true, "IsComputed": false, "IsChangedByUser": false, "IsChangedInRevision": true, "HasPatternMatch": false, "IsLimitedToAllowedValues": false, "HasAllowedValuesList": false, "AllowedValues": [], "IdentityFieldAllowedValues": [], "ProhibitedValues": [] }

any ideas on what I can do?

[MrHinsh]

If LOCKED is a required field and you do not have permission to bypass the rules engine then you will not be able to write a work item with an invalid state.

Enable bypass rules for your account. https://nkdagility.github.io/azure-devops-migration-tools/server-configuration.html

[MrHinsh]

@SabapathyKannappan which version of the tool are you using as your code lines do not match mine.

[SabapathyKannappan]

Hi, I am using the latest one 13.0

[MrHinsh]

I've updated all NuGet packages and pushed an update to 13.1

[SabapathyKannappan]

Thanks a lot... shall i use 13.1 and give a try ?

[MrHinsh]

Im not sure it will fix anything. I spoke to the product team and they would like you to raise a ticket for support.

If you send me the ticket ID they can match it to your data.