Newbie Webstorm question. Is it possible to “deplo...
# sdf
n
Newbie Webstorm question. Is it possible to “deploy to account” just one object from a project? Similar to the way just one file can up uploaded to account.
m
"Deploy" will deploy whatever is in your
deploy.xml
file. So you would need to manage the contents of that file to control what gets deployed when you use "Deploy to Account".
a
there's no simple click on object .xml definition and deploy just this to the account specified in the project.json ... which there can't be really cos objects have interdependencies and those need to be validated on deploy you can do what @Mike Robbins suggests above but you're likely gonna have to add a bunch of dependency stuff to the manifest.xml to get that to work depending what the situation is.
i guess if everything ELSE already exists in the account maybe it would be ok? 🤔
m
Every new piece of functionality we push to production has it's own dedicated
deploy.xml
specifically for this purpose. For a new feature, we create a new git branch and as we create/modify customizations, they get added to the
deploy.xml
for that branch. After QA/UAT, deploying is a "simple" as checking out that branch and then
suitecloud project:deploy
to production. It's often not that simple because ... NetSuite, but it's very close.
a
its simple enough to test I guess... just create a subfolder under objects called
justthis
and copy your .xml file into it and then update your deploy.xml to look like this
@Mike Robbins you could just structure your Objects folder to be ~/Objects/releaseName/* and that's what the deploy.xml in that release references... or is that what you do already? that way all the other objects are still in the objects folder for easy access if needed
m
We store our objects in folders by type. It's pretty frequent that different releases will deploy updated versions of objects that were part of previous releases. For example if we deploy a custom record and a subsequent release adds fields to that record, we deploy the whole record. I'd prefer to only have one version of any object in the repo, but that could be a personal preference.
Our
deploy.xml
files can be pretty large sometimes because we call out each object explicity.
n
thanks, we do have the objects organised into subfolders already, so updating
Copy code
<path>~/Objects/*</path>
makes sense for me to test.