I did precisely this...I added user event script on various record types AND a scheduled script (which uses saved search API) to pick out checks both as they are updated and any records that might have been missed/previously skipped for any reason. I ended up having to do nlapiRequestURL to send the information to a PHP…

This is obviously an old thread, but in case anyone comes across it, you can now create Folders in the File Cabinet using the API. You can also use the API to save Files into specific Folders and specify if those Files should be Public or not (setIsOnline() function).

Evan's code worked great for me in the Before Load User Event for a Support Case (http://usergroup.netsuite.com/users/showthread.php?t=13053&page=2): if (type != 'create') { var filters = new Array(); filters[0] = new nlobjSearchFilter('internalid', null, 'anyOf', nlapiGetRecordId()); filters[1] = new…

I figured that I should report back now that I seem to have the SuiteCloud IDE working. However, I'm not really sure what exactly was necessary to fix the problem. It's also still unclear to me if others are/were seeing problems or if we're just unlucky. In any event, here's what did. Downloaded clean copy of Eclipse…

We are also seeing this. It also seems to not be linked to how many files are in the File Cabinet, as it happens on Developer, Sandbox, and Production instances with very different File cabinets. SDF CLI listfiles seems to work.

Is this post made with the knowledge of NetSuite's recommendation to have a dedicated SDF user account? Is the issue that you don't have / don't want to pay for an additional account? That seems completely reasonable, but I just want to make sure I'm understanding your post.

The NetSuite Java code (SuiteAppUtil.class) sets values in the "C:\Users\<user>\.sdf" directory (on Windows). Have you verified that there is a valid "sdf.properties" file getting created there?

I am receiving this exact same error on production and sandbox for 17.2, both via SuiteCloud IDE and via CLI, when trying to deploy a single "role" XML file (that I did successfully retrieve via CLI). The exact same Project and file deploys fine to a clean developer instance. Is the implication the this SuiteCloud plugin…

DWDW Apologies if I am misunderstanding, but I believe the (IMHO confusing) rule established in this thread is that if the "Help" output for a command does not show a "-p or -project" parameter then that command will always require explicit specification of all individual parameters and that they cannot come from an .SDF…

For what it's worth, I've been writing some custom Node.js to automate around the CLI, and if you're using Visual Studio Code, the existing NetSuiteSDF plugin seems useful and might provide guide rails (Though I have not actually tested it as much as read the source code). It also already includes some logic to autoinput…

What specific command did you use specify the "project"? https://netsuite.custhelp.com/app/answers/detail/a_id/63969

kcng Interesting, I never actually used those specific commands before but your answer seems to solve this thread... but as an aside, wouldn't it make sense to still default to using the default project's account for those commands? Or perhaps there should be a concept of a "profile" apart from a specific project?

Hi rprice , In that case, is it possible that you have an invalid ".sdf" file or, perhaps, you are issuing the commands in different prompts? On Windows 10 at least, if you open Command Prompt 1, use that "project" command, then open Command Prompt 2, that will not carry over, I think. I think the most direct way to solve…

I am not familiar with the NetSuite domains used to send out e-mails either, but I have discovered that even if a nlapiSendEmail() message is attached to a Case such that a reply to that message will also be attached to the Case, it seems to use the @messages.netsuite.com domain and NOT the normal @cases.netsuite.com…