Have you ever come across such a blocker while trying to access the Configuration page in SuiteCommerce? If yes, you’re not alone. This error-“Invalid webapp id : ‘configurationManifest.json'” – typically occurs when NetSuite fails to resolve the correct domain mapping for your SuiteCommerce site. But Don’t worry, the solution may be simpler than expected.
One common cause is when the SuiteScript is unable to correctly link the Configuration page to its corresponding domain setup. This can happen if the SSP Application, a core component used to manage SuiteCommerce functionality, hasn’t been properly connected.
What is SSP Application?
The SSP Application (SuiteScript Server Pages) is a key framework in NetSuite’s SuiteCommerce architecture. It enables server-side scripting for dynamic page rendering, configuration management and integration with various SuiteApps. Each SuiteCommerce site typically uses an SSP Application to serve content and handle custom behaviors.
There are different versions of SSP Applications depending on the site’s deployment and customizations – often labeled as v1 or v2 .
How to Solve It ?
It’s easy to resolve the issue by using the following two actions based on the version of SSP Application :
For SSP Application v1 : Use the ‘Link to Domain’ option to establish the correct association between the application and the target domain.
For SSP Application v2 : Utilize the ‘Deploy to Domain’ feature to publish and bind the necessary configuration files to the domain environment.
Once these adjustments were made, the Configuration page became accessible without triggering the “Invalid webapp id : ‘configurationManifest.json'” error.
NB : After domain linking or deployment, it’s advisable to clear the site’s cache to ensure new configurations are properly applied. This helps eliminate outdated references and ensures a clean load of updated assets.