In SDF, I have downloaded all objects but it throws me the dependency error. Seems like it refers the object like transaction body field or transaction column field before it is deployed. It throws me this error.

Details: The manifest contains a dependency on custbody_custom_id object, but it is not in the account.

But in SDF objects directory I can see that body field xml file. How could I fix this?

Is the field inactive by chance?

yes that object does not exist in the target account

Push the object only to the target account and revalidate.

So no way to do that in one step?

There seems to be a dependency on the custbody_custom_id object itself. What kind of field is it?

It's a transaction body field which is used in SuiteScript files just List/Record type

Well, Just remove the dependecy from the manifest and try that or use Copy to Account to move the field over.

Actually I already did it, but I wanted to know if there is any method to do that in one step. Like importing Objects first and then scripts, WFs, automatically

SDF is an adventure sometimes. Bets to try workarounds. Not always possible in one step.

Thank you

@Boris Yasen I’ve found sometimes the order objects are listed in the deploy.xml has an affect on success or failure. Sometimes moving the “missing dependency” to the top of the list fixes the issue.