Hello! After an intensive use of restlets and suitscript I am trying to create entitities using standard REST Webservices. The result is that I am a bit confused due to different names for the same field. For example I would like to set the Tax Registration Number of a Vendor. In suitescript it is easy: I set the field vatregnumber. In REST I cannot find what is the right field to be set. I tried both "defaultTaxReg" and the sublist "taxRegistration" but without any chance. Have anybody ever faced problems like these? Thanks in Advance.

fair approach is to do a get on an existing vendor

Already tried on an existing record and it does not appear. Strange that such a standard field is not supported on REST.

I would stay on using of RestLet and suitescript….REST webservices has been on hold for a long time and still in BETA

Thanks Zoran. Unfortunately in this case we're dealing with an external system integrator with no experience on Netsuite so the Restlet solution is not an option. I've just talked to him and he is unwillingly going to use SOAP.

SOAP is nightmare for me … never used before .. too complicate, too old, but unfortunately, from the NetSuite the only one solution that is completed. REST WebService is not finished, still in Beta … many features are missing That’s why I always force custom RestLets. In that case we can hold all under control. Moreover, I wrote some custom RestLets (or http requests) when client use official connectors like OpenAir or HiBOB … Well, my honestly suggestion : make a deal with external system integrator > you provide custom restlets, they provide access …. This is not place for offering service, but if you want, I can help

Thanks Zoran for sharing your experience. Mine is similar: I developed a lot of integrations with Netsuite using both raw programming languages as PHP or integration platforms as Talend and Mulesoft. In all this cases, on Netsuite side I developed my own Restlets. IMHO it was the simpler and flexible approach. In this case we are talking about a very low-spending client. We presented several alternative solutions for data integration (scheduled CSVs, Restlet, APIs,...). They chose APIs because it was the cheaper on our side and they could be nearly independent. So it is not a matter of knowledge nor of time but of budget on client side. Anyway yesterday their developers successfully managed to connect by using SOAP and create a complete Vendor. So let's go on on that way. ;-)