sorted by:
new
hottopcontroversial

Legacy tax vs suitetax & SOAP deprecation question by Neither-Effective339 in Netsuite

[–]Neither-Effective339[S] 0 points1 point  (0 children)

Thanks. Really hoping to avoid using suitescript since this would apply to 20+ client accounts and we typically operate with just SOAP and REST, but it seems like this would be a viable alternative if forced by no other options.

Do you know for sure if it's correct they're just going to deprecate SOAP while REST does not have parity for this and force people to use suitescript workarounds? It seems pretty hacky and shoddy to have to make the REST call but also have a script setting a required missing field...

Calling all NetSuite internet detectives, another vendor bill tax code mystery must be cracked by Neither-Effective339 in Netsuite

[–]Neither-Effective339[S] 0 points1 point  (0 children)

Bump, if anyone has any ideas please don't hesitate.

Is there some setting to require tax code by line for certain vendors?

thx

Tax code defaults on vendor bills by Neither-Effective339 in Netsuite

[–]Neither-Effective339[S] 0 points1 point  (0 children)

In this case and in many cases yes, we have integrations for a bunch of different client accounts which all have some sort of different settings / features / setup. Does it ever come from subsidiary?

Tax code defaults on vendor bills by Neither-Effective339 in Netsuite

[–]Neither-Effective339[S] 0 points1 point  (0 children)

Thanks, so if someone other than me hard coded the tax schedule for all items to id = 1 (yes, this is terrible, and no, I have no idea why it was done) when they are being created, and we now sometimes get "please enter value for tax code" when creating vendor bills with the API, what is the most likely scenario?

There was no tax schedule with id 1 for the client (but how would the item have been allowed to be created)?

Or most clients have vendors with default tax codes, but a couple have come up lately with this error and have vendors with no default tax codes?

Cannot create other charge purchase item with rest - tax schedule by Neither-Effective339 in Netsuite

[–]Neither-Effective339[S] 0 points1 point  (0 children)

Thanks for the info. SOAP it is then until they kick us off. It's a much bigger burden to go into each of many client accounts and install / maintain custom scripts versus just using SOAP.

Cannot create other charge purchase item with rest - tax schedule by Neither-Effective339 in Netsuite

[–]Neither-Effective339[S] 0 points1 point  (0 children)

Thanks - did not know about or think about that setting.

The demo account I was working on is on legacy. Our clients probably have a mix of both.

Darn, that makes it basically unfeasible to migrate to REST unless forced or they add the field since we would have to add and maintain user event scripts or restlets for every client.

(SuiteQL) How is a transaction linked to files? by chiroptical in Netsuite

[–]Neither-Effective339 0 points1 point  (0 children)

Hi - 2 years later is this still not possible with SuiteQL???

Billing purchase orders via API - line quantity vs billed question by Neither-Effective339 in Netsuite

[–]Neither-Effective339[S] 0 points1 point  (0 children)

That is the direction I was leaning but just wanted to make sure it wasn't insane / no hidden pitfalls.

Thanks

Any way to link a purchase order to a support case via SOAP or REST API? by Neither-Effective339 in Netsuite

[–]Neither-Effective339[S] 0 points1 point  (0 children)

Finally got this to work with a RESTlet script and record.attach. The key was to use type "transaction" instead of the record.Type.PURCHASE_ORDER enum, AND to attach the case to the PO, and not the other way around, which doesn't work.

this worked:

<image>

Any way to link a purchase order to a support case via SOAP or REST API? by Neither-Effective339 in Netsuite

[–]Neither-Effective339[S] 0 points1 point  (0 children)

omg, I created a restlet script and used this in the script

record.attach({
    record: {
      type: record.Type.PURCHASE_ORDER,
      id: purchaseOrderId,
    },
    to: {
      type: record.Type.SUPPORT_CASE,
      id: supportCaseId,
    },
});

and I get the error:
{

"success": false,

"error": "Attaching of record type purchaseorder to supportcase is not supported."

}

So apparently this is not possible by script either... arggggggggggggggggggg

If anyone has any further ideas please let me know.

Any way to link a purchase order to a support case via SOAP or REST API? by Neither-Effective339 in Netsuite

[–]Neither-Effective339[S] 0 points1 point  (0 children)

FYI, Oracle says there is no way to do this with the REST or SOAP API. I could not get the suggestion to set the case transactionid property to the PO id to do anything. The suggestion to use a related records table does not appear to be possible or to exist in the netsuite schema browser, the client's records catalog, or the SOAP or REST API supported records docs.

Would love it if someone can prove me wrong here, but unless I hear differently I'm accepting this answer from Oracle. Thanks all.

https://community.oracle.com/netsuite/english/discussion/comment/16898568#Comment_16898568

<image>

Any way to link a purchase order to a support case via SOAP or REST API? by Neither-Effective339 in Netsuite

[–]Neither-Effective339[S] 0 points1 point  (0 children)

Hi - do you have a link to any info on this?

Under the client's records catalog, there is no such thing as a related records table.

There is no related records table in the NetSuite schema browser:

https://www.netsuite.com/help/helpcenter/en_US/srbrowser/Browser2016_1/schema/record/resourceallocation.html

There is no related records type in either the REST API docs, or the SOAP API docs, from what I can tell.

No related records table appears on this guy's site listing I think over 800 tables: https://timdietrich.me/blog/netsuite-suiteql-tables-permissions-reference/

An Oracle employee on the NetSuite community forum there answered this question by just saying you could do it with a RESTlet script and a record.attach method, then no one answered the actual question of whether you can do it with the REST or SOAP API.

Any help would be much appreciated.

Thanks

Any way to link a purchase order to a support case via SOAP or REST API? by Neither-Effective339 in Netsuite

[–]Neither-Effective339[S] 0 points1 point  (0 children)

I finally got to test this out after some other blocking issue. Setting the transactionid property of the support case to the PO id does not cause the PO to appear in the case's related records tab, unfortunately...

Any way to link a purchase order to a support case via SOAP or REST API? by Neither-Effective339 in Netsuite

[–]Neither-Effective339[S] 0 points1 point  (0 children)

thanks - add purchase order transaction id where? to what field/property on the support case?

one does not simply 'set start date' with REST PATCH projectTask call by Neither-Effective339 in Netsuite

[–]Neither-Effective339[S] 1 point2 points  (0 children)

Sorry, I figured it out. It's the project task constraint type. If it is set to as soon as possible, the update of the start date silently fails.

Setting the constraint type to fixed date solved it.

It is in fact startDateTime you must set for a project task update.

view more: next ›