The simplest way to set up a NetSuite account is to use the Suite cloud Development Framework (SDF). We can first import all of the required objects from the source account into WebStorm (the implementation platform), and then deploy them to the various target accounts. First and foremost, we must make a list of the components that must be moved to the desired account. We have to manually enter all of the preferences and account setup. After that, we start with SDF, which is used to deploy all of the Lists, Records, Fields, Templates, Segments, and so on. We’ve covered all of the steps involved in setting up an account. We are unable to deploy all of the components to the desired account due to dependencies with other objects. As a result, we must organize them into phases. There are no dependence items in the first phase and so on.
- To set up an account using SDF, we use the WebStorm platform. To start with an SDF project, create a project in the WebStorm by providing the proper naming
- Connect the source account from which the object will be imported after creating the project.
- Connect Via browser-based authentication.
- Set the default account as the source account once the account has been connected.
- These are the most fundamental things to take. The objects from the source account are then imported.
- The next step is to import objects from the account. For that right-click on the ‘Object’ then select ‘NetSuite’ -> ‘Import object from account’.
- Choose the account from which you want to import data. Then click NEXT.
- Choose the category you want to import, such as Lists, Fields, Records, and so on. Then click SEARCH
- Then select the objects by marking them. Click FINISH.
- For easier deployment, keep a directory for each set of objects.
- The WebStorm has two .xml files: Manifest and Deploy.
- Add ‘dependency references to the manifest’ to find out which objects are dependent on the imported items. To do so, right-click the manifest.xml file and choose ‘add dependency reference to the manifest ‘. All dependent objects and features are added to the manifest file as a result of this. These dependent objects or features must be present in the targeted account (if the dependent objects or features are not available in the targeted account, an error will occur. You must either delete the dependency from the manifest or create/enable it before deploying the project to the account.)
- Next the deploy.xml file. Which indicate that the deployment path. If you deploy all the object, then we set path as
<objects>
<path>~/Objects/*</path>
</objects>
- Set the proper hierarchy in the path if you just want to deploy a specific file. (Avoid using * in this scenario.)
<objects>
<path>~/Objects/CRM fields/custevent_check_correct_contacts_roles.xml</path>
</objects>
- Set the default account as the targeted account to validate the project against the new account after setting the Deployment path and manifest.
- To validate the project against the account, right-click on the source then click ‘NetSuite’, and select ‘validate project against account’
- If there are no errors, we can deploy the project to the new instance. For that, click ‘NetSuite’ then ‘Deploy to account’
- These are the fundamental understanding of WebStorm deployment.