Testing NetSuite Extensions and Saving Form Data
Test your NetSuite extensions and verify form data is saved correctly to enhance data management efficiency.
Testing your extension is crucial to ensure data is captured correctly within NetSuite's platform. This process can be executed at any time by launching a local server. If all required fields are completed and validation for custom fields is successful, users should see the data entered in their NetSuite account.
Steps to Test Your Extension
-
Navigate to Leads:
- Go to Lists > Relationships > Leads.
-
View Lead Details:
- Click View next to the lead name you filled out on the registration form.
-
Access Custom Fields:
- Select the Custom tab to see the custom fields along with the data you entered.
- Note: If the custom field isn’t visible, you may have to customize the form settings. For more information, refer to the documentation on Custom Forms.
- Select the Custom tab to see the custom fields along with the data you entered.
-
Verification:
- Check to ensure the data entered in the form is correctly displayed within the custom field.
Local Server Setup for Testing
To create an efficient testing environment, set up a local server using Node.js, which requires the Express web framework. Follow these steps:
-
Run the command:
bashgulp extension:localThis initializes a local server, compiling the source files located in the LocalDistribution/tmp directory.
-
Changes Detection: Gulp.js will listen for file changes in your project directories, automatically recompiling any altered files and updating the distribution.
-
When modifications involve manifest files, remember to restart your local server to apply the changes.
Important Considerations
- Testing should occur on a local server before deploying to a live NetSuite environment. If your extension includes SuiteScript or configuration (JSON) files, ensure these are deployed in your NetSuite account to access their functionalities locally.
- This approach ensures that services defined through SuiteScript are available during development, as such services do not exist until deployment.
Conclusion
Following these steps ensures effective testing of your NetSuite extensions, focusing on accurate data entry and verification, ultimately enhancing your data management capabilities within the platform.
Frequently Asked Questions (4)
Do I need any specific permissions or roles to test NetSuite extensions?
How can I make custom fields visible if they are not showing during testing?
What are the prerequisites for setting up a local server to test NetSuite extensions?
What should I do if manifest files are changed during extension testing?
Was this article helpful?
More in SuiteScript
- Common SuiteScript Errors and Solutions for NetSuite
Common NetSuite script errors include INVALID_SCRIPT_DEPLOYMENT_ID and SSS_AUTHORIZATION_HEADER_NOT_ALLOWED. Learn effective solutions.
- Set Sublist Field Values in SuiteScript 2.x for Record Management
Set sublist field values in SuiteScript 2.x for effective record management using standard and dynamic modes.
- Setting Field Values in SuiteScript for Effective Record
Learn to set field values in SuiteScript effectively, troubleshooting common errors and understanding data types.
- SuiteScript 2.1 Enhancements and API Updates in NetSuite
SuiteScript 2.1 enables execution of 2.0 scripts and supports PATCH method for enhanced API capabilities.
Advertising
Reach SuiteScript Professionals
Put your product in front of NetSuite experts who work with SuiteScript every day.
Sponsor This Category