Another question, does anyone know if "cc approved...
# general
n
Another question, does anyone know if "cc approved" field actually has any permissions assigned to it? Our 3rd Party Payment portal is creating our Payment in NetSuite and we are receiving this error in the SOAP Web Services Log, "`platformCore:message>You do not have permissions to set a value for element ccapproved due to one of the following reasons: 1) The field is read-only; 2) An associated feature is disabled; 3) The field is available either when a record is created or updated, but not in both cases.</platformCore:message>`" The error log shows it fails to create the payment record and then literally 2 seconds later it succeeds. Curious if it is worth it to get this error solved, or just let the 2 second pass for it to actually get created.
b
take a look at the web service usage logs to make sure that the 2 requests are actually the same
n
The only difference I can see is on the failed one it has the line "<ns8:ccApproved xsi:type="xsd:boolean">true</ns8:ccApproved>"
Then on the successful one, that line is removed.
b
that would suggest the successful request isnt actually setting the ccapproved checkbox, so its not actually solving the issue
n
Correct. But that field isn't even viewable on the Payment record.
b
that would cause the problem in the first place
you cant set a field that doesnt exist
n
It exist on the form be looking at the form record and editing it.
b
doesnt really matter, if you cant see the field on the form while creating the record
n
https://suiteanswers.custhelp.com/app/answers/detail/a_id/105027/loc/en_US this is the one article I was able to find on it.
b
there a bunch of different reasons you cant set the ccapproved checkbox
most of them related to whatever payment method (or payment instrument) being used not actually being a credit card that can be approved
in general, you need to know how to create your payment in the ui
if you cant set ccapproved in the ui, you wont be able to set it via the integration
n
So do you think the payment integrator knows that and is sending it twice if the CC approve fails. then they know they have to send one without it?
b
i think they are being lazy and arent making the effort to store which methods are actually credit cards
my guess is that they decided its easier to make another request every time they cant set ccapproved over making logic to determine if they should set the field in the first place