Hi everyone, I'm attempting to implement the "Resolve Content-Type Mismatch for SCA 2019.2 to 2023.2" patch, but am struggling to get the override functionality to work during the deployment compilation. The version I'm working with is 2021.2. The ns.package.json file is the same as provided in the documentation:

{
  "gulp": {
    "ssp-files": [
      "SuiteScript/*.ssp"
    ]
  },
  "overrides": {
    "Commons/CustomFields/SuiteScript/customFieldsMetadata.ssp": "SuiteScript/customFieldsMetadata.ssp"
  }
}

and the distro.json file has been updated to include the new custom extension module. However, when I run the build to compile, the customFieldsMetadata.ssp file is not in the deploy distribution folder. When I remove the module from distro, the native version is back in the deploy distribution folder. Essentially, I am not able to get the newly over-ridden version to be include in the deployment. If I adjust the ns.package.json file:

{
  "gulp": {
    "ssp-files": {
      "SuiteScript/customFieldsMetadata.ssp": "customFieldsMetadata.ssp"
    }
  }
}

and move the custom module below the native custom fields module in the distro file, I am able to pull in the new version to the distribution folder. I would rather use the override functionality as the documentation instructs, but it's almost if it takes issue with a .ssp type file. I have no issue with overriding service files. Sorry for the long winded explanation. I'm hoping someone else may have run across this issue before or can point out if I'm missing something. Thank you!

@Steve Goldberg could you please help us to get the docs updated? @Cory is totally right.

It already has. If you're checkin docs.oracle then those are a few weeks out of date, but they have updated in HC and SA