I have some really noob questions when it comes to...
# sdf
h
I have some really noob questions when it comes to SDF, but I'm tired of hitting my head against my keyboard: We initially set up everything by hand in our account, we have a dev env and a sandbox as well. The sandbox is copied from production from time to time. However, we'd like to get everything into SDF so that we have the configuration stored in source control and have a better workflow than making changes straight in production and or having to redo everything we've tried in the sandbox. I've managed to set up and account customization project and import all the non locked objects into it. However, if I try to deploy to the dev env there is a dependency problem. I've tracked it down to a bundle that is installed in sandbox/prod, but not in dev. Adding a bundle dependency in the manifest file informs me that I can only add it to a Suite App project. Questions: 1. Is it possible to install bundles via SDF? 2. If so, can you only do so via a SuiteApp project? 3. Do you need to register to get a publisher ID before you can do this? 4. Can you publish a SuiteApp to only your account? Please feel free to tell me if I'm going about this in the wrong way, it's all new to me 🙂
👀 1
a
SDF was actually created to replace bundles. So Bundles don't go with SDF. There are constant improvements in SDF. And recently efforrs are increased to io improve SDF.
🤔 1
👍 1
s
With the current capabilities of SDF, when you pull down an object it gets the entire definition. That includes dependencies that third party bundles may have inflicted on the object. The only workaround I'm aware of is to hand edit the XML to include only the customizations you control/want. I wish SDF had a way to exclude dependencies due to existing bundles - maybe it will someday.
t
Isn't that what manifest.xml is for? I add in 3rd party bundle objects in it so that when I deploy it skips over the dependency check
h
@Travis Zuri yeah, that works, but only after you've installed the bundle. I was hoping there is a way to tell the deploy to install all the required bundles if they don't exist.
I was hoping to be able to do:
Copy code
<dependencies>
  <bundles>
    <bundle id="351">
      <objects>
<object>customrecord_car.custrecord_wheel</object>
<object>customrecord_train</object> 
      </objects>
    </bundle>
  </bundles>
</dependencies>
but that's not allowed in account customization
z
@Travis Zuri... no... with adding dependency objects in manifest you are telling to SDF : "OBJECTS ALREADY EXISTS IN TARGET ACCOUNT", but during deployment process NetSuite checks are objects really installed... It is regularly... If you have some custom fields, scripts which referencing bundle components it is not possible to create... even through UI
h
@Zoran Roncevic do you know if what I'm trying to accomplish is possible?
or am I going to have to install all third party bundles in the UI before deploying?
s
you can edit the xml to not reference things those bundles added. or in other words, reduce your xml to only include the things you're interested in
t
But if you remove the dependencies in the xml and then redeploy you remove that bundle's functionality after deployment. I don't know anyway around it other than installing all the bundles, but I would think you would want any bundles present where you deploy so that testing is correct
s
SDF never removes anything as far as I've seen. It's only additive
t
If you have a customform that includes a customfield from a bundle, my experience has been that removing it from the form xml keeps it off the form when you deploy it
h
yeah, editing the xml to remove things referenced by a bundle is not really an option, some of the fields are actively used. The question really is all about automating bundle installation 🙂 If not possible with SDF, can you do it with suitescript?
t
outside my scope of experience
s
hmm, that would be sad - I haven't tried that myself. NS needs
removing things from xml would be fine if it only changed what was in the xml and left the rest the same
z
@Hannes Benson You have to install All bundles before deploying your SDF project And it same situation with other objects from the same project. I worked previous days on transfering whole account to new... Hundreds objects 🙄... WebStorm plugin stucks (neverendding progress bar)... Then I started partially deployment. DeployXML had only one type of objects, but on the other side manifestXML contained all previously installed objects... 😢nightmare
h
@Zoran Roncevic thank you very much 🙂
z
Very useful option is Add depedency to manifest in SDF plugin... Just click and WebStorm will add all required objects
Just to comment : you are lucky if you dont use Bundles... NetSuite automatically add all depedency without option to exclude... So if you extend or use some custom fields from 3rd party bundle, NetSuite force install them inside your bundle..