My Stuff
Hello Community! Josh Maxwell, a User Experience Researcher for NetSuite Foundation has fun a question for you. Imagine for a moment that NetSuite had an assistant like Alexa or Siri. What would you ask of your NetSuite assistant? Use this survey link to share your top questions to the assistant.
Here are some examples to get your creative juices flowing.
"Did I pay vendor John Doe last month?"
"Take me to my largest sales order for this month."
"What invoices haven't been paid yet?"
Here are some examples to get your creative juices flowing.
"Did I pay vendor John Doe last month?"
"Take me to my largest sales order for this month."
"What invoices haven't been paid yet?"
Join or Log in to view discussions
Comments
-
Try 'PLAINTEXT' or 'XMLDOC' without the base64 encoding
-
Have you tried creating the file as 'PLAINTEXT'? example: var xlsFile = nlapiCreateFile('TEST.xls', 'PLAINTEXT', xmlString);
-
The difference between CURL and the NetSuite API (nlapiRequestURL), is that the NetSuite API returns a response that has been encoded with "deflate", identified by the "Content-Encoding" header in the response. The [url] request seems to work in browsers and with other tools (e.g. CURL), so my thought here is that there's…
-
Was told by NetSuite Support that they could reproduce the problem (get compressed content when requesting the URL) and that I should try a URL that doesn't contain an image (the URL does not contain an image, it's JSON data returned from a weather service). My response was that there is no image file. No response from…
-
I originally thought it had something to do with the URL (the fact that it includes ".json", which "http://itunes.apple.com/search?term=metallica" does not), but both of the following URLs contain ".json" and one works while the other does not. This URL returns readable JSON - http://api.feedzilla.com/v1/cultures.json This…
-
Yes, response.getBody() returns what appears to be encoded/compressed data.
-
Here's the code I'm using to test this issue: function pageInit() { var url, headers, response; url = "https://api.wunderground.com/api/d15f79daf3e2427c/conditions/q/12345.json"; headers = new Array(); headers["Accept-Encoding"] = "identity;q=1.0, *;q=0"; response = nlapiRequestURL(url, null, headers);…
-
I'm working on a Proof of Concept, so I was able to move the code from a Suitelet to a client script and use jQuery to retrieve the JSON data.
-
So this is kind of where I started; adding a header of "Accept-Encoding" with a value of "identity;q=1.0, *;q=0" or even "*" doesn't seem to change the response. It always comes back encoded with "deflate" and appears as garbage.
-
It looks like NetSuite may have addressed this issue as my support case has gone from "Open - Under Investigation" to "Testing/Pending Release".
-
I'm consuming a web service that returns JSON. The nlobjResponse shows that the web service returned the data using 'deflate' ("Content-Encoding" in headers) and the "body" appears to be compressed (looks like encoded/compressed data, not JSON). Unless there's a way to tell the web service to NOT encode the data, I don't…
-
Thanks for the response, I'll try to upload the files again. According to NetSuite help, the library scripts are loaded in the order they appear in the Library Script tab (I know this to NOT be true). Is NetSuite aware of this issue? Are they planning on fixing this?