You need to sign in to do that
Don't have an account?
niristotle okram
Inconsistency with the force migration tool
I am trying to under the fact that the migration tool sometimes fails with "Error: Not in package.xml", while it doesn't complain about the same for some metadata types. I am aware of the fact that only elements specified in the 'package.xml' should exist in the 'src' folder.
So if i have some 'objects' metadata inside src, and not mentioned in the package.xml; it throws the Error.
But if i still have metadata like 'Communities' , 'workflows', the migration Ant task doesn't seem to throw the error, even if i don't specify them in the package.xml.
i am working in a developer edition and the version is 38.0 (specified in the package.xml), may be the API version
So if i have some 'objects' metadata inside src, and not mentioned in the package.xml; it throws the Error.
But if i still have metadata like 'Communities' , 'workflows', the migration Ant task doesn't seem to throw the error, even if i don't specify them in the package.xml.
i am working in a developer edition and the version is 38.0 (specified in the package.xml), may be the API version