Since the FTP API methods are only available with SuiteScript 2.0, you would start with a SuiteScript 2.0 scheduled script. You would then use the N/search module to run the search, the N/file module to create a file object, and the N/sftp module to FTP the file. Depending on your technical persuasion, you may want to…

If you want to show all items, make an item search and join to transaction fields as opposed to a transaction search.

So in that case you definitely don't want any criteria to be based on the transaction fields because that will exclude some items. You can still have results based on transaction fields though. To exclude info from transactions that are not POs, use a formula like this in the results (pseudocode, dont copy/paste): Case…

NetSuite's saved search joins almost always use left joins, so they should do exactly what you're seeking. What filters do you have on your saved search? Do you have a filter for Transaction Fields...Type = Purchase Order? If so, then try checking USER EXPRESSIONS and replacing that with two filters: Transaction…

If the user is checking/unchecking based on known critiera, you could add filters for those fields. Otherwise, you could build this exactly as you described with a suitelet. That said, I'm having trouble understanding the value here. Given that a user would only be manually checking/unchecking a small list anyway, wouldn't…

I believe this would be a case statement with slightly different formulas depending on the day of the week. There are some answers here: https://stackoverflow.com/questions/14898357/calculate-business-days-in-oracle-sqlno-functions-or-procedure

The criteria above will exclude items that are on other transaction types (i.e. vendor bills, sales orders), but not purchase orders.

If you have the advanced reporting module, you might want to consider using ODBC/JDBC instead. That said, depending on what records you are reporting on you may be able to implement a saved-search-only solution by adding formulacurrency columns such as the follows: CASE WHEN {salesrep.custentity_sales_volume} <= 1000 THEN…

Add a result column for employee, and set the summary type to group. You can have multiple result columns set to group.

The work-around would be to hide the standard field and display a custom field in its place. Then when a value is selected in the custom field, that value has to be transferred to the standard field by scripting or workflow.

Hi Steven, there's no way to add filtering to standard fields in addition to the native filtering already in place (i.e. filtering out inactive records). What you could do in your example is to provide your own search box (custom field), and pop up a window with a list of search results filtered as you desire. When the…

I was recently corrected that there is now a supported way to show/hide fields in SuiteScript 2.0 - see michoel 's comment in this thread: https://usergroup.netsuite.com/users/forum/platform-areas/customization/suitescript-2-0-custom-code/428412-simple-how-to-conditionally-display-field

I've had trouble with this as well. I reported this as a defect, but NetSuite re-classified it as enhancement #412482 - it only has 2 votes right now in SuiteIdeas, so NetSuite isn't likely to fix it in the near term. The only work-around is to save the copy and then re-load it - then the sublist will be available - would…

The auto-generated numbers feature creates an additional numbering schema that is separate from internal IDs. Internal IDs have never been guaranteed to be sequential or even in order (more recently created records are sometimes assigned lower internal IDs).

Did you try transactionRecord.getFieldText('customform');

Did you try setting the access level for the Administrator role to "edit" and checking the "run as administrator" checkbox on the workflow?

If you go to SETUP > COMPANY > AUTO-GENERATED NUMBERS, you can check the "Allow Override" checkbox for invoices.Then you can type in the sales order #, or any other number for that matter. If at any point down the road you change your mind and decide to automate this via script or workflow, you can.

If you want to limit the options in the class dropdown by user/role, you can select a class on the user's employee record and set the role to be restricted to that class and subordinates.

Is your custom field set to "store value"?

I believe the URL parameter is a reference to memorized transactions, for instance the URL of the "Enter Memorized Transactions" page is: /app/accounting/transactions/bulkmemdoc.nl But keep in mind, aside from the parameter which you may be able to manipulate in the UI, the sublist will also be unavailable upon copy or…

Easily doable - on the custom field, set the type to list/record employee. Then on the custom field's sourcing and filtering tab, set the "filter using" column to role and select the desired role in the "value is" column.

Correct! If you uncheck the "store value" checkbox when defining the field, then NetSuite will re-run the formula everytime the user goes to the record. As far as the type of field, there are a few different options: 1. A hyperlink field is fine, but the display text will be the link URL 2. An inline HTML field would be…

You can create a field with it's default value coming from a saved search instead of a formula. But I think you're going to run into challenges because fields that do not store values cannot be included in saved search results.

NetSuite doesn't use the popup form in the scenario you're describing. Popup forms for custom records are used when a list/record field is a drop-down of custom records and the user selects "New" as the option. As far as what you're requesting, it could be scripted or created with formula fields (target="_blank",…

Sorry, I tried it and you're right - the value for "Role" always seems to be empty when the filtering is happening. If I check "Is Empty," then all employees show up in the drop-down. So I guess that won't work... Maybe you could add another flag to the employees with this role that you can filter by? Or the other option…

Oh, I missed that about your description - you can create a formula like that for any type of custom field, the only thing to keep in mind is that you can only pull in data from the current record and records it links directly to.

See https://usergroup.netsuite.com/users/forum/platform-areas/customization/426994-list-field-listing-fields-from-transaction

Sure - create a transaction body field with a default value formula as follows: 'https://www.randomwebsite.com/thirdparty/servicecallpost.cgi?&transactionID=' || {internalid} || '&firstName=' || {customermain.firstname} || '&lastName=' || {customermain.lastname} and so forth * I just typed this off the top of my head, so I…

I would love to know this too. A few more work-arounds I can throw out: 1. Using two fields. One field with a default value of {cleared}. Another field with a formula based on the first field. 2. Using SuiteScript to set the field.

The sales team and sales tabs are different. The sales tab has opportunities, transactions, etc. The sales team tab has sales reps and their sales roles. Sounds like you might have the two tabs mixed up?