My Stuff
Review our AI Community Guidelines before posting AI-generated or AI-assisted content. Verify accuracy and include the appropriate AI disclaimer.
Action Required: Review and submit pending reconciliation matches before the NetSuite upgrade to avoid rework. After 26.2, unsubmitted matches will be unmatched. For more details, see SuiteAnswers 1047397
Explore NetSuite Next with Free Training!
Build your skills with the LCS Explorer Pass.
Visit the NetSuite Next community page
to learn more, ask questions, and share your experience.
Build your skills with the LCS Explorer Pass.
Visit the NetSuite Next community page
to learn more, ask questions, and share your experience.
Comments
-
@Mikko De La Fuente-Oracle No I do not. From some reason the fieldType and scriptId are not being deserialized. I have had to work around it and get that information a different way.
-
I have determined that the issue is not that the fieldType data is not coming back in the the SOAP response. I added logging to log the SOAP request and response and I see the correct data. The problem must be in the Connected Service code that Visual Studio generated from the WSDL I guess. I am digging deeper.
-
Thanks @Mikko De La Fuente-Oracle . I didn't see that this forum had direct message capability.
-
Account is ######. Is that all you need?
-
Sadly no. NetSuite does not allow us to submit support cases at the level of support we have. Not a great business decision in my opinion but maybe that's why I don't run a business.
-
I am using the latest WSDL I think. 2022_1 maybe I have not tried with other applications. I think I can work with what I have now. Thanks
-
Hmm, yes, if I call getCustomizationId with GetCustomizationType.customRecordCustomField I get a list of all customization fields and each field does include the scriptId. That's fine and maybe I can use it but it doesn't really fit the current logic that would only get the customFields used be a particular CustomRecord…
-
https://medium.com/@benwmills/using-the-netsuite-suitetalk-api-with-net-core-net-standard-40f1a4464da1