My Stuff
Comments
-
Hi Andrew, Nope, not possible, Random NS limitation.
-
Packing Slips cannot be associated to Customers. Packing Slips can be associated to specific Sales Order custom forms. In your scenario, you would need to create 1 Sales Order custom form per customer that has a specific Packing Slip. Then, when a SO is created, the user would need to select the Sales Order form that…
-
NS maintains a "Line Sequence ID" field, but I'm not sure that's available for sourcing. You may need to use scripting. In particular, you will need to consider how you want your sequencing to behave when people insert lines in between 2 existing lines, or if a line is removed.
-
Indirectly answering, 2015.2 will allow you to Inactive fields. So, if you are having problems deleting them, at least you'll be able to inactivate them so they don't show up in the listing.
-
I've not heard the behaviour of Amount is going to change. It seems doubtful it would since that would wreck many accounts.But, you're correct that quantity UOM not being Quantiy UOM is not something NS handles. I don't really see any way other that custom fields and scripting, and then of course custom reports to support…
-
You might be able to add a custom field that uses a Search to compute the total. Keep in mind such a field will not be available in any search or report, but if you just want to see that total on the record itself, it is a simple and inexpensive solution. If you need to see that field in searches and reports, you will need…
-
FloDocs!! Check them out!
-
Note: you can edit a transaction with Inactive items without any trouble
-
You need to set up Sourcing on the other fields and make the fields Store Value = False. Refer to the Help (SuiteCloud (Customization, Scripting, and Web Services) ->SuiteBuilder (Customization)-> Custom Fields-> Creating a Custom Field-> Setting Sourcing Criteria) for more details.
-
I strongly, strongly, strongly do not recommend doing this. You will break your NetSuite. Do NOT play with the DOM.
-
Hmm, a script would do that. Can't think of any other ways.
-
You need to do 2 things 1. On the Period the bill is sitting it, go tick in "Allow Non GL Changes" (my wording is probably not quite right) 2. On the Role of the person responsible for making these changes, grant them the "Allow non GL Changes" on the "Setup" subtab of the Role Note that this will allow the user to modify…
-
If you don't need that field to show on a saved search, you can actually use a formula field to calculate that and display on the SO, so you could achieve this without scripting. If you do need to use that field in a saved search, then you'll need scripting.
-
Simplest way would be to add a link to a saved search and export that way. Using footer filters, you will notice you can paramterize your link to filter the search results to only this SO.
-
Just to point it out, clever sales reps would be able to get around the fact the Sales Rep field is hidden. Hiding a field is pretty far from making it bullet-proof impossible to change. If this is super important for you, might want to consider using a more secure system. In any case, your post is a little unclear so I am…
-
Hmm, now that is a good question. Try using the format of: https://forms.netsuite.com/.../&firstname={firstname}&lastname={lastname}&ema il={email} I'd think that is that doesn't work, then I think you'll need scripting to achieve this.
-
Maybe if you pinged a Suitelet and gave it the phone as param. The suitelet could then execute a global search to find the records and then use window.open to open the right custom record. Thing is, without seeing it, I'm not sure the session info would properly carry over for the suitelet to be authorized to open the…
-
This is a long standing pain point without an easy fix. NetSuite is great at handling whole records permission-or-not, but terrible at partial access. What you could here is give him access to a Custom Form that does not show the Vendor and price (actually, you can't even do that - Vendor at least is mandatory and cannot…
-
Are these US states? Out of a hunch, can you try nlapiSetFieldValue('custpage_inv_state', 'CA')
-
Setup->Company->Printing, Fax and Email Preferences->PDF Section on first tab->Extend Columns to Bottom of Page
-
You'll need to use scripting or a workflow to change the form when the Location is set, and possibly vice-versa.
-
It'd be possible though it falls outside supported coding practices. Basically, NS offers triggers for when you tab out of a field, but no trigger for each individual change... You want to field to show a count-down of characters as they are being typed, right? You'll have to step outside of supported coding practices and…
-
1. Under Setup->Customization->Transaction Column Field, create a new field as follows: Label: Expense Vendor Type: List/Record List/Record: Vendor Applies To: tick in Expense Report 2. Create a Saved Search as follows Type: Transaction Name: Vendor Expenses Criteria: Mainline = false Type = Expense Reports Columns:…
-
Even better :)
-
Oh no, it'll work. Like I said, you can do it. It's just not a supported coding method.
-
Any price level that has a value is shown You would need to use scripting to reject the selection of the level.
-
Not really, no. You can hide it on a custom forms and restrict users to only use that form, but they will always be able to pull it from a search. You'd have to remove the ability to create searches for the field to be truly inaccessible, and even there, there would be holes. Another alternative would be to remove access…
-
The problem is not with the field itself, but with everyone's roles. You need to edit all your Roles and take away the Setup->Custom Lists permission.
-
If you have MLI on, what you're trying to do will be impossible, as NS wouldn't know which Location to take the Quantity Available from.
-
Using a Markup item seems like your best bet then. You can add a Subtotal items, then add the Markup. the Markup applies to the item immediately above it, so that being the subtotal, you,ll get 2.3% on the entire order. Or, as I mentionned, just add it as a body-level "discount"