SSP Application Asset Precedence Management in NetSuite
Manage SSP application asset precedence in NetSuite for effective web customization handling across multiple applications.
SSP applications in NetSuite allow users to store multiple website customizations within a single account, which can include modifications for identical web store touch points. When a URL directs to an asset that exists in several SSP applications, a precedence system dictates which application responds to the request.
Understanding SSP Application Precedence
Each SSP application is assigned a precedence sequence number, such as 1, 2, 3, 4, etc. The application with the lower number has higher precedence. Consequently, files within an SSP application that has a lower precedence number are utilized first.
By default, newer SSP applications automatically take precedence over existing applications when they are integrated into an account. However, administrators have the flexibility to adjust the precedence of any SSP application within NetSuite.
Example of Precedence Behavior
When a new SSP application is installed, it is assigned a default precedence of 1. This gives it priority over any files within applications that carry a precedence of 2, 3, 4, and so forth. Administrators can change this precedence whenever necessary to suit their needs.
How to Change SSP Application Precedence
- Navigate to Customization > Scripting > SSP Applications.
- Click the Change Precedence button.
- Adjust the numbers in the Precedence column as necessary and click Submit.
Following these steps can help maintain a proper hierarchy for your web assets, ensuring the intended customizations are deployed correctly.
Key Considerations
- Always review the current precedence configurations when adding new SSP applications to ensure that the desired assets are prioritized appropriately.
- Changes to precedence can take immediate effect, so it's wise to verify the functionality after any adjustments.
Related Topics
- Enable Required Features for SuiteScript 1.0 SSP Applications
- Create a SuiteScript 1.0 SSP Application Record
- Upload SSP Application Files
- Set Execute as Role Permissions for .ss and .ssp Files
- Select Supported Touch Points
- Link a Website or Domain to an SSP Application
- Remove Touch Points
- Sample SSP Application Code (SuiteScript 1.0)
- Debug a SuiteScript 1.0 SSP Application
- SuiteScript 1.0 SSP Applications
- Create and Use SSP Applications
Source: This article is based on Oracle's official NetSuite documentation.
Key Takeaways
- SSP applications enable multiple customizations within a single account.
- Lower precedence numbers indicate higher priority for asset usage.
- New applications default to higher precedence but can be adjusted.
- Changing precedence is straightforward but requires attention to detail.
Frequently Asked Questions (4)
How does NetSuite determine which SSP application takes precedence?
Can administrators change the default precedence of newly added SSP applications?
What should be done after adjusting the precedence of an SSP application?
Where can the SSP application precedence be changed in NetSuite?
Was this article helpful?
More in SuiteScript
- Scheduling Map/Reduce Script Submissions in NetSuite
Learn how to schedule map/reduce scripts for one-time or recurring submissions in NetSuite, enhancing automation and efficiency.
- API Governance Units Calculation in NetSuite 2026.1
NetSuite 2026.1 introduces examples illustrating API governance unit calculations for both user event and scheduled scripts.
- Binary File Support in N/https Module for SuiteScript
SuiteScript enhances capabilities with binary file support in the N/https module, allowing improved data handling in external communications.
- Attach and Detach Operations in NetSuite 2026.1
Attach and detach operations for record relationships in NetSuite enhance data management and connectivity.
