Version: All
Audience: Administrator

Use Case

This guide will help you:
  • Find the root cause of errors in PromoStandards responses.
  • View the NetSuite error associated with a PromoStandards response error.

Overview

PromoStandards responses include error messages that follow specific response rules. However, these messages don't always communicate the underlying cause of the error. Problems can arise from various sources, including:
  • Configuration changes in eXtendPS-SE
  • Data issues
  • NetSuite-related problems
  • Other technical factors
To get a clearer picture of these errors, we'll use the eXtendPS-SE script logs. These logs provide detailed error information for PromoStandards error responses.

How to View Script Logs

  1. Navigate to Customization → Scripting → Scripts → eXtendPS-SE Restlet.Image Placeholder
  2. (Optional) Clear existing logs by clicking the Remove All button.
  3. Run the PromoStandards request that is generating the error. This will create new script log entries.
  4. Set the Type filter to Error, then review the log entries related to your PromoStandards request.
Note: If you need more context around an “Error” log entry, temporarily change the script deployment’s log level to Debug or Audit. This will show additional log details leading up to the “Error” entry.

Tip for Busy Environments

In busy environments with many PromoStandards requests hitting your endpoints, identifying your specific requests can be challenging. To make it easier to isolate your own testing:
  1. Locate or set up an additional script deployment for the eXtendPS-SE Restlet script.
  2. Use an existing deployment if available (as long as its ID is not customdeploy_extend_promo_api_rest). Otherwise, create a new one.
  3. Add your script deployment's deployment ID to the PromoStandards service endpoint like this: ?deployId=deploymentId
    1. Example: https://yoursubdomain.suitextend.net/v1/promo-supplier/promoproductdata/v200/productdataservice?deployId=2

      deployId is case sensitive.
  4. Run your PromoStandards request using this modified endpoint.
  5. Check the script logs for your specific deployment to find your error information.