Is anyone having issues w/ their SDF project validating just fine in some accounts but not in others? I have a field on a item that is a checkbox that stores the value and then a transaction column that sources this value. Works fine in almost all of my accounts but 1 and its telling me that the item field does not exist when validating but the field is getting deployed before the field that sources it. Cannot for the life of me figure out why it would work in some accounts but not all.

Yes, not that specific problem, but generally

suitecloud project:validate --server

executes successfully but

suitecloud project:deploy

fails for a number of different reasons. Most prevalent is order of operation. If sdf evaluates a saved search before a custom item field is added, then I’ve seen failure. Generally we break our packages into folders for each type of element (think

<xmltag,,

) and then control order of operation with multiple lines in

depoy.xml

Another pretty common problem we have is role permissions (permissions on the role being used by the sdf access token/secret) - our developers seem to have admin to everything in our dev netsuite account.