Customize Configuration Manifest in SuiteCommerce Advanced

Customize the configuration manifest in SuiteCommerce Advanced to enhance properties and integrate custom modules for better functionality.

·2 min read·View Oracle Docs

The configuration manifest in SuiteCommerce Advanced (SCA) defines how customizable properties are presented and processed within the application. Understanding how to customize this manifest is crucial for developers looking to enhance functionality and interface elements in SCA.

Importance of Customizing the Configuration Manifest

This approach allows developers to add new properties or modify existing ones, tailoring the SuiteCommerce configuration record's user interface for specific business needs. Customizations can range from changing default values to implementing entirely new features through custom modules.

Best Practices for Customization

When customizing the manifest, you should adhere to best practices to ensure the longevity and compatibility of your changes:

  • Never alter or delete the configurationManifest.json file directly. Instead, focus on customizing individual JSON files associated with the manifest.
  • Use JSON Schema V4: When creating new properties, structure them properly to ensure they integrate smoothly into the configuration record.
  • Monitor Upgrades: Following best practices aids in upgrading to newer SCA versions without issues, as your customizations will coexist with newer updates.

Create a New Property

To introduce new properties into the manifest, follow these steps:

  1. Create a custom module, defining necessary files and directories.
  2. Utilize JSON Schema V4 to declare the new attributes.
  3. Deploy your module to NetSuite.

Example Structure for New Properties

Here’s a simplified structure of how your custom module could be organized:

plaintext
MyCustomModule
├── config
│ └── custom_property.json
└── module.js

Customize Existing Properties

If you wish to modify existing properties, the Configuration Modification method should be employed. This involves adjusting the source JSON configuration files associated with properties existing in the configuration manifest. You can add, replace, or remove metadata as needed while also spreading changes across several custom modules.

Existing Property Modification Steps:

  • Identify the target JSON configuration file.
  • Apply changes using the Configuration Modification method.
  • Validate your changes by testing the configuration in a development environment.

Conclusion

Understanding how to manipulate the configuration manifest is essential for any SCA developer. By following structured best practices and careful modification of JSON files, developers can ensure that their customizations are sustainable and compatible with the evolving SuiteCommerce landscape.


Source: This article is based on Oracle's official NetSuite documentation.

Key Takeaways

  • Never edit the configurationManifest.json file directly; use individual JSON files.
  • New properties require creating a custom module with JSON Schema V4.
  • The Configuration Modification method allows tailored changes to existing properties.
  • Following the best practices will help ensure compatibility with future SCA updates.

Frequently Asked Questions (4)

How do I add new properties to a configuration manifest in SuiteCommerce Advanced?
To add new properties, create a custom module, define the necessary files and directories, and use JSON Schema V4 to declare the new attributes. Afterward, deploy the module to NetSuite.
What are the best practices for customizing the SuiteCommerce Advanced configuration manifest?
Best practices include avoiding direct alterations to the `configurationManifest.json` file, utilizing JSON Schema V4 for new properties, and monitoring upgrades to ensure customizations fit with new SCA versions.
How can I modify existing properties in the SuiteCommerce Advanced configuration manifest?
To modify existing properties, use the Configuration Modification method. This involves adjusting source JSON files associated with the existing properties, allowing for adding, replacing, or removing metadata as needed.
Is it necessary to follow JSON Schema V4 when adding new properties to the configuration manifest?
Yes, using JSON Schema V4 is necessary for structuring new properties to ensure they integrate smoothly into the configuration record without compatibility issues.
Source: Customize the Configuration Manifest 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 General

View all General articles →