I need some help troubleshooting this error which I see in the Network tab of my browser console when I try to Continue from the first checkout page when logged into SuiteCommerce as a customer:

{
  "errorStatusCode": "400",
  "errorCode": "ERR_WS_FIELD_NOT_SUPPORTED",
  "errorMessage": "You have attempted an unsupported action."
}

The errorMessage appears in a little pink error notification in one place on the checkout page, or three places if it's one-page checkout. It doesn't really tell me much, and I don't see any Server Script Logs about it when I search them. Whatever is throwing this error seems to also be preventing the user from advancing to the next checkout step.

AI generated answer (using internal Slack threads):

Based on the error message you're seeing, it seems like you're trying to perform an action that is not supported by the NetSuite Web Services (WS) API. The error code

ERR_WS_FIELD_NOT_SUPPORTED

indicates that a field you're trying to access or modify is not supported in the context of the current operation. Here are a few steps you can take to troubleshoot this issue: 1. Check the Field: Make sure the field you're trying to access or modify is supported by the NetSuite WS API. You can refer to the NetSuite Records Browser to verify this. 2. Check the Operation: Ensure that the operation you're trying to perform is supported for the field in question. Some fields may be read-only or write-only, or may not be accessible through certain operations. 3. Check the Record Type: Some fields may only be accessible on certain record types. Make sure the field is valid for the record type you're working with. 4. Check the SuiteScript Version: If you're using SuiteScript, make sure you're using a version that supports the field and operation you're trying to perform. 5. Check the User Role: The user role may not have permission to access or modify the field. You can check this in the role settings in NetSuite. 6. Try a Different Browser: As suggested in the threads, sometimes using a different browser can give you a different error message that might be more helpful in pinpointing the issue. Remember, it's important to thoroughly test any changes in a sandbox environment before deploying them to your live site to avoid any potential disruptions. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******

The problem was due to the custom fields defined in the SC Custom Fields extension not existing in Transaction Body Fields. I was able to fix it (thanks to Vicky's advice) by creating those fields.

The agent hasn't yet been programed to respond to follow-up questions in the thread. But you can continue asking in the main channel.