• jdillon
  • NEWBIE
  • 0 Points
  • Member since 2012

  • Chatter
    Feed
  • 0
    Best Answers
  • 0
    Likes Received
  • 0
    Likes Given
  • 0
    Questions
  • 1
    Replies

 

Was wondering if anyone has come across a similar issue before...

 

Getting the following errors when trying to do a full deployment using the migration tool.

 

Error: workflows/PersonAccount.workflow(PersonAccount):Cannot create workflow directly; must create the CustomObject first

---> This is odd because it's a full deployment which means the object is there, but for some reason the error exists. In addition, there's no visible Person Account-specific workflow component in the org itself for a metadata component to be generated.

 

Error: workflows/Question.workflow(Question):Cannot create workflow directly; must create the CustomObject first

Error: workflows/Reply.workflow(Reply):Cannot create workflow directly; must create the CustomObject first

---> Best guess for these two is that they are related to the installation of the Timba app which some folks are trying out. Having said that, I've already uninstalled the app in the source org, but the *.workflow metadata components are still there. I even tried physically removing the metadata in both the IDE and yet when I do a refresh from the server, they both come back.

 

Appreciate any insights you can offer on these errors.

Hopefully someone has encountered them before and can let me know how they were able to get rid of them.

Last resort is of course doing a clean-up of the metadata after a 'retrieve' task and prior to the 'deploy',

but I'd rather find the root cause and fix it properly.

 

Thanks in advance!