if I 'validate against account' - does it confirm ...
# sdf
s
if I 'validate against account' - does it confirm that any elements I've indicated as dependencies exists in the target account? it doesn't appear to which is counter to what I'd expect. My expectation would be if an SDF project validates against an account then it should successfully deploy against that account. If there are dependencies listed in
manifest.xml
that are not in the target account, SDF will error on deployment, yes?
Any insight on above? What exactly does 'validate' do when pointing at an account? @Ali Syed (NS DevTools QA)? Or can we confirm that
validate
does not confirm that object dependencies in
manifest.xml
exist on the target account?
a
Yes, it does validate the dependencies against the account you have referenced in your local project. And it should complaint if referenced files are missing in target account.
s
hmmm. and the account authid listed in
project.json
is always what
suitecloud
will use for the target account for
project:deploy
?
a
I remember the use case you provided some days ago and also listing the default authid through a command. I have suggested these improvements for future release. For now yes, the default account in project.json will be used for all actions.
s
ok, thanks, just confirming. It's scary to not know for sure where I'm changing things 🙂