https://netsuiteprofessionals.com logo
Join Slack
Powered by
Im using an Account customization project for the ...
# sdf
n
Im using an Account customization project for the first time with Webstorm. I have successfully downloaded all my objects (Custom form, body fields, column fields, script). Then I click on 'Add dependencies to manifest'. But I dont see the custom form object that I had downloaded. Any idea what I may be doing wrong?
m
I'm not sure I understand. On the left of the screenshot I see a custom form in the project, so it did download. If you are referring to seeing the form listed as a dependency in th manifest, then that's the correct behavior. It should not be listed because it is in your project.
n
ok perfect. Thats what I was trying to confirm. So now when I try to push this to Sandbox 2 where none of these objects exist, i get a whole bunc of error messages like this:An error occurred during account settings validation. Details: The manifest contains a dependency on custbody_11187_pref_entity_bank object, but it is not in the account. Details: The manifest contains a dependency on custbody_bko_flag object, but it is not in the account.
So my question is do i have to import the custom fields first, then separately import the new custom form using these new custom fields?
e
It doesn't really matter what order you do it in as long as you do both before you deploy (assuming both the form and all the fields should be part of the project)
You can't deploy when you have a dependency that doesn't exist in the account
All dependencies must exist in the target account before you can deploy. Either add the form and the fields to your project directly and remove them from the dependency list, or make sure everything listed as a dependency exists in the account first
n
yes that makes sense. So maybe my steps are wrong. So first i import all my objects in webstorm, Next i click on the ''Add dependencies to manifest" and this automatically adds dependencies to the manifest.xml file. Lastly i am deploying. Maybe I am missing something here. Are you saying that i should first import all the custom fields , add them to manifest, then deploy so those objects are in and then do a second round where I import the custom form?
e
Not exactly
If you are truly importing all the relevant objects, then there shouldn't be a problem deploying
any Object that is directly in your project should not be listed in your dependencies also
I've noticed WebStorm will do that sometimes, like it will add script files that are in my project as dependencies, but that breaks deployment
Your order of operations is correct. I am questioning: 1) are you actually getting all the necessary Objects? 2) Is WebStorm adding too many dependencies? e.g. if 
custbody_bko_flag
is part of your project (its XML file is in your Objects/), then it should not be listed as a dependency in your manifest
n
ok i think i figured it out. I had this field custbody_bko_flag which i imported into webstorm, Then before deploying i realised that I needed to rename the Id in the UI. Then i tried to deploy from webstorm without fixing this in the manifest. let me try to fix it now...
ok I tried to simplify this and I am still running into issues. So here is my new scenario: - I import one single script file from Sandbox SB1 in my Account customization project in Webstorm. -I validate against Sandbox SB1 and it shows success. Now i validate against Sandbox SB2 and it fails: Details: The manifest contains a dependency on /SuiteScripts/Sales Order/USE_sales_order_v1.0.js file, but it is not in the account. I think this is excepted correct behavior, the file is not yet deployed to Sandbox SB2. -Now I try to deploy that single script object to SB2 and I get the same error: * ERROR * Validation of account settings failed. An error occurred during account settings validation. Details: The manifest contains a dependency on /SuiteScripts/Sales Order/USE_sales_order_v1.0.js file, but it is not in the account. 2019-04-12 120030 (PST) Installation FAILED (0 minutes 1 second) Any thoughts?
b
Manifest file lists things that need to exist in the account to make the deploy successful
e
Again, it's because you have listed an object that's in your project (the script file) as a Dependency
remove the File from your Dependencies
no Object should ever be in both your dependencies and your project
Dependencies are things that are not part of your project but must exist in the account for your project to work
Things in your 
Objects/
folder are what will be created/updated by deploying your project.
Nothing should ever be in both places
n
ok now that makes better sense, i have got it to work. Thanks for your help.
👍🏼 1
✔️ 1
Open in Slack
PreviousNext
Powered by