Shared Query Migration Error

[Musket519]

I am attempting to move some shared queries and I am receiving the following error:

Exception thrown: 'Microsoft.TeamFoundation.WorkItemTracking.Client.InvalidQueryTextException' in Microsoft.TeamFoundation.WorkItemTracking.Client.dll

Its not stopping the program running and some queries get migrated but others dont and running it through VS isnt giving any good information as to what is causing this or why. I was wondering if you had any insight into what would throw this error?

Config:

{
  "ChangeSetMappingFile": null,
  "FieldMaps": [],
  "GitRepoMapping": null,
  "LogLevel": "Debug",
  "CommonEnrichersConfig": [
    {
      "$type": "TfsNodeStructureOptions",
      "NodeBasePaths": [],
      "AreaMaps": {

      },
      "IterationMaps": {

      },
      "ShouldCreateMissingRevisionPaths": true,
      "ReplicateAllExistingNodes": true
    },
    {
      "$type": "TfsWorkItemLinkEnricherOptions",
      "Enabled": true,
      "FilterIfLinkCountMatches": true,
      "SaveAfterEachLinkIsAdded": false
    },
    {
      "$type": "TfsRevisionManagerOptions",
      "Enabled": true,
      "ReplayRevisions": true,
      "MaxRevisions": 0
    },
    {
      "$type": "TfsAttachmentEnricherOptions",
      "Enabled": true,
      "ExportBasePath": "c:\\temp\\WorkItemAttachmentExport",
      "MaxRevisions": 480000000
    },
    {
      "$type": "StringManipulatorEnricherOptions",
      "Enabled": true,
      "MaxStringLength": 1000000,
      "Manipulators": [
        {
          "$type": "RegexStringManipulator",
          "Enabled": true,
          "Pattern": "[^( -~)\n\r\t]+",
          "Replacement": "",
          "Description": "Remove invalid characters from the end of the string"
        }
      ]
    },
    {
      "$type": "TfsUserMappingEnricherOptions",
      "Enabled": true,
      "UserMappingFile": "C:\\temp\\userExport.json",
      "IdentityFieldsToCheck": [
        "System.AssignedTo",
        "System.ChangedBy",
        "System.CreatedBy",
        "Microsoft.VSTS.Common.ActivatedBy",
        "Microsoft.VSTS.Common.ResolvedBy",
        "Microsoft.VSTS.Common.ClosedBy"
      ]
    }
  ],
  "Processors": [
    {
      "$type": "TfsSharedQueryProcessorOptions",
      "Enabled": true,
      "PrefixProjectToNodes": false,
      "SharedFolderName": "Horizon",
      "SourceToTargetFieldMappings": null,
      "ProcessorEnrichers": null,
      "SourceName": "Source",
      "TargetName": "Target"
    }
  ],
  "Version": "15.0",
  "workaroundForQuerySOAPBugEnabled": false,
  "WorkItemTypeDefinition": {
    "sourceWorkItemTypeName": "targetWorkItemTypeName"
  },
  "Endpoints": {
    "TfsEndpoints": [
      {
        "Name": "Source",
        "$type": "TfsTeamProjectConfig",
        "Organisation": "https://dev.azure.com/Source/",
        "Project": "Project",
        "ReflectedWorkItemIDFieldName": "Custom.ReflectedWorkItemId",
        "AllowCrossProjectLinking": false,
        "AuthenticationMode": "AccessToken",
        "AccessToken": "",
        "PersonalAccessTokenVariableName": "",
        "LanguageMaps": {
          "AreaPath": "Area",
          "IterationPath": "Iteration"
        }
      },
      {
        "Name": "Target",
        "$type": "TfsTeamProjectConfig",
        "Organisation": "https://dev.azure.com/Target/",
        "Project": "Project",
        "ReflectedWorkItemIDFieldName": "Custom.ReflectedWorkItemId",
        "AllowCrossProjectLinking": false,
        "AuthenticationMode": "AccessToken",
        "AccessToken": "",
        "PersonalAccessTokenVariableName": "",
        "LanguageMaps": {
          "AreaPath": "Area",
          "IterationPath": "Iteration"
        }
      }
    ]
  }
}

[MrHinsh]

Most likley its fields that do not exist in the target environment.

If you run through VS and put a breakpoint on where the exception is raised you can see what the query text is.

[Musket519]

@MrHinsh So it looks like youre correct, the queries are referencing fields that dont exist in the target. My question is, do field maps not work for this? I attempted to create a field to field map for the field its throwing an error over and the error didnt stop. Do I have to manually go into the queries and change what fields they are referencing?

[MrHinsh]

No field maps do not work for this.

If it's in the query then it must exist.

[MrHinsh]

Although that would be a good feature...