True. But I have a bundle that is a legacy SuiteA...
# sdf
d
True. But I have a bundle that is a legacy SuiteApp, and I cannot transition it to the new SDF-style SuiteApp (I wish I could). So, I want to manage the legacy SuiteApp bundle as an Account Customization (which I guess it really is). Seems logical no?
a
I don't know what you mean by "manage the legacy SuiteApp bundle as an Account Customization"
Can you elaborate?
d
Hey @Albert Margarit (NS Eng Lead), ok. So, this is concerning a SuiteApp built a few years again (Tactical Connect).
We built it as a Bundle, and followed all the best practices (hiding files, locking objects, etc)
So, the bundle is Developed in a Developer account, tested and bundled. Then copied to our Deployment account, and released to NetSuite customers
I want to leverage SDF and was hoping I could do that at the Developer level
So, I attempted to import all the files/objects via SDF (Account Customization project), but the 'hidden' files were ignored. Obviously not good
Also, I cannot convert this bundle to a SDF SuiteApp style, because everything would break (For starters, files go into a SuiteApp folder, etc)
Thanks @Albert Margarit (NS Eng Lead) for checking in on this
a
I see
I´m not sure I´m able to answer this one. @Mariano Saenz (NS Eng Lead) any thoughts on this?
d
@Mariano Saenz (NS Eng Lead) in a nutshell, if I had control of HIDE IN BUNDLE and INCLUDE IN SUITEBUNDLER file attributes using the Account Customization type of SDF project, I'd be good.
m
Hey Darren, you are correct, you should be using an Account Customization project. The project should be used with the account where you do your development. Therefore that account should have the files NOT hidden, since you need to modify them. SDF should allow you to modify the files if you are able to modify them in the UI. SDF also allows you to modify the file properties like Hide in Bundle by using the attributes files.