Why isnt my credential GUID switching over in my https post call

AI generated answer (using internal Slack threads):

Based on the conversations, the issue of the credential GUID not switching over in the HTTPS post call could be due to several reasons: 1. Incorrect use of GUID: GUIDs are case sensitive and should be used as is without any modifications like converting to uppercase. They should be used as placeholders that are replaced by N/https when you make a request. 2. Incorrect use of SecureString: A common mistake is to accidentally convert the SecureString into a normal string when trying to mix the two. A SecureString converted to a string is useless and won't be replaced with a credential. 3. Incorrect placement of GUID: The GUID should be placed in the correct location where it needs to be replaced. For example, if the GUID is being used in the body of the POST request, it should be placed in the body and not in the URL or headers. 4. Incorrect configuration of Credential Field: The

restrictToScriptIds

and

restrictToDomains

parameters of the credential field must be correctly set. The

restrictToScriptIds

should be set to the scriptId of the script using HTTPS and

restrictToDomains

must be correctly set to the domain that you are sending requests to. 5. Incorrect format of GUID: The GUID needs to be surrounded by "{}". If your GUID is 4cc0f6c255ad4299ad538b3b4c75580a, you would use {4cc0f6c255ad4299ad538b3b4c75580a} in the requestBody. 6. Incorrect use of https.post: The GUID should be included in the

credentials

parameter of the

<http://https.post|https.post>

call as described in the NetSuite documentation. If all these points are correctly implemented and the issue still persists, it would be a good idea to test the request with an echo service like httpbin.org or postman echo to see what the request looks like and to identify any issues. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******