Testing NetSuite Extensions and Saving Form Data

Test your NetSuite extensions and verify form data is saved correctly to enhance data management efficiency.

·2 min read·View Oracle Docs

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

  1. Navigate to Leads:

    • Go to Lists > Relationships > Leads.
  2. View Lead Details:

    • Click View next to the lead name you filled out on the registration form.
  3. 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.
  4. 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:

    bash
    gulp extension:local

    This 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?
The article does not specify permissions or roles needed for testing extensions. Review your role settings or consult NetSuite's documentation for necessary permissions.
How can I make custom fields visible if they are not showing during testing?
If custom fields aren't visible, you may need to customize the form settings. Check the documentation on Custom Forms for instructions on customizing form visibility.
What are the prerequisites for setting up a local server to test NetSuite extensions?
You need Node.js and the Express web framework to set up a local server. Additionally, Gulp.js is required to listen for file changes and recompile source files.
What should I do if manifest files are changed during extension testing?
If you modify manifest files, you must restart your local server to apply the changes. This ensures that updated configurations are included in your testing environment.
Source: Test the Extension and Check Form Data Is Saved Oracle NetSuite Help Center. This article was generated from official Oracle documentation and enriched with additional context and best practices.

Was this article helpful?

More in SuiteScript

View all SuiteScript articles →