5

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?

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

4 Answers 4

3

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)

1
  • I'm trying to deploy Paths for Leads object. I already have Default path for Leads and your solution does not work for me
    – compski
    Commented Feb 16, 2021 at 6:55
3

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.

2

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).

1

A quicker way to resolve this is to NOT deploy Lead Process at all.

Do a manual pre-deployment step of adding the Lead Process and assignment of record type DIRECTLY into the Target Environment.

Note: I have tried segregating the change sets, making sure all FLS is setup, deploying record types with Path assistant and all the same error "Required fields missing: [PicklistMasterId]". The only way you can do this right now is manual pre-deployment step or ask Salesforce Support

1
  • 1
    Yes its a pain in the but to rebuild a path... but at least this is 100% going to work. I was working with opportunity paths. I deployed a new sales process with it. The stages didnt show up at at first. To fix all I needed to do was remove and add the stages to the sales process. Then the path and process where all set. <-- adding this here in case anyone else goes with this option Commented Nov 8, 2021 at 13:40

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .