0

I'm trying to deploy custom Path using ANT. I have deployed the pathAssistant and the flexipagemetadata but the Path is still not visible in setup nor on page layout. I can see that pathAssistant metadata are actually not moved to next sandbox for some reason.

Any suggestions?

  • If you do a retrieve from the target org, can you retrieve the things you've pushed? If you do a comparison using gearset.com (free trial...) then it should highlight anything you've missed – Kevin Boyle May 19 '17 at 8:17
  • Thanks for the suggestion. You're right, the pathAssistant metadata are note build to the next sandbox. The question now is why. – mascot May 19 '17 at 8:51
  • I'd suggest trying a comparison with Gearset (full disclosure I'm CEO...) but that will probably help you build a deployable package (You can then download it and examine it with ANT to learn what was going wrong...) – Kevin Boyle May 19 '17 at 15:10
2

I was having the same problem, I attempted to deploy the path with the flexipage, but same deal... Can I ask if you're using a record type for your path and whether you've included the picklist you're using with the Path?

Once I included pathAssistant type in the package.xml it worked good!

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.