2

When deploying a case path assistant from a sandbox to another I'm getting an error when deploying the package:

Required fields missing: [PicklistMasterId]

We have deployed all fields being used in the case object to this environment as well. What can be causing this error message?


After playing with the Migration Tool, directly with the metadata, I noticed that I can retrieve the path and related metadata, such as:

  • BusinessProcess
  • CustomField
  • PathAssistant
  • Queue
  • RecordType
  • Role
  • Settings

And when commenting all the fields in the path metadata the validation succeeds as expected. However, the path would be deployed without its fields. For example:

<pathAssistantSteps>
    <!-- <fieldNames>Observations__c</fieldNames> -->
    <picklistValueName>Call customer</picklistValueName>
</pathAssistantSteps>

The Observations__c custom field is a text area field. When commented out, the validation succeeds. Otherwise, I get an error describing that it is not possible to deploy a path step because a picklist value is unsupported. This error doesn't make sense for this specific field.

Am I correct to assume this is an internal error with Salesforce?

  • are you using Global picklist field? – Santanu Boral Jul 24 '18 at 18:21
  • On the case object there is at least one object which uses a global picklist, yes. – Renato Oliveira Jul 24 '18 at 19:20
2

Required fields missing: [PicklistMasterId]: I had the same error and I fixed it by adding a default path for the same object (in your situation 'Case') with record type --Master-- After that was created, I could deploy met custom path.
Cannot insert Path Assistant Step Item: Picklist value is not supported: Remove all <info>blablabla</info> tags from the .pathAssistant file. It's a bug (https://success.salesforce.com/issues_view?id=a1p3A0000008gWXQAY)

| improve this answer | |
2

I managed to resolve this error. In my case I was including a PathAssistant in a change set for an unmanaged custom object with no record types. The path was already in Production so it had been successfully moved via change set before.

The problem was the picklist field had different picklist values in Production and the Sandbox. (I added some new options in my Sandbox). The picklist field was not included in the change set. This was the cause of the "Required fields are missing: [PicklistMasterId]" error.

I manually adjusted the picklist values in Production to match the Sandbox and the change set was then able to deploy.

| improve this answer | |
1

What solved this answer, after some days working with SFDC's tier 2 support, was to redeploy the picklist field that controls the path steps (so this field is technically the "master" here).

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.