Olivier Gagnon NC Red Ribbon

Awesome. If it kind of falls in the same line, it would be very helpful if on linked transactions (SO and Drop Ship PO specifically), you could see the "parent item" line number. We often need to match up items in linked transactions and it would be good if we just had a reference line number. Not sure if that's quite the…

Is exactly what you just typed going to be part of the 2011.2 release notes or should I note this somewhere?

Ah, line numbering... You have to consider what you want your numbering for. Do you need line numbers to be absolutely unique per order? Do users use Add Multiple to add items? Do you enter orders through CSV import of web services? Does numbering need to always be sequential? Can numbers change once assigned to a line?…

No transaction rows? Weak sauce. Well, that means you gotta store the information at the Body level, which means custom body fields. However, you don't know how many lines you can have, and you need 1 field per line - unless you decide to sum all your COGS into a single value. Then you'll need scripting to transfer the…

Mm, ok. The field thing was based on the following thinking - Tabs don't show if there is nothing on them Read-only components don't show on create (for example, store value false fields) Perhaps the entire tab wasn't showing, thus the sublist wasn't since it's dynamically added, so bu forcing the tab to show it might show…

What you are trying to do is not possible. First of all, an item is tied to many POs, so you would need a field to select which PO you want to source from. That's not so bad, except then a PO has many line items. So again, you would need a way to specify which line to look at, and that is not possible in Netsuite (there is…

Ok I got really curious so I tried this myself. The result I got is that placing the custom field on the Tab DID make the tab show, but the tab did not have the sublist loaded. So... yeah. Maybe your account has something special?

Try sticking a custom field on the Tab. Any custom field. Just make sure it is Store Value True.

Hmm, good one. Ok, here's an idea. 1. Create a Transaction Saved Search showing Account and Amount, filtered to only show COGS accounts. Add an "Available Filter" for the internal id field. 2. (Optional) Create a subtab (Setup->Customization->Subtab) and name it "COGS" or something 3. Create a Sublist…

Not possible. There is an enhancement request for it.

Hmm. I'd have to look in more detail, I don't know what the problem might be. You could try calling Support for advice (but that'll take a while).

Well... When you create a Credit Memo, you can chose to apply it to anything existing. It will not, however, automatically apply itself to the next created Invoice. You would need to either edit the CM and apply it to the invoice, or create a new Payment to link the CM to the Invoice. When you create the CM, you can chose…

Right. What you CAN do is show Amount Remaining and/or Amount Paid on the printout using custom elements. Of course, this means you must only email the Invoice AFTER having applied the Credit Memo.

Try erasing the label, that may work.

Yes, that is the BIG limitation of mail merges - no line item information. The scripted scratch built PDF is the best way to get around that problem. You can access any field and the layout can be anything you want. There's no real other way to achieve this, except perhaps exporting data (such as with a Web Query Report)…

I've seen some customer customize the SO print out so that it can pass as a BoL, so sometimes that works. You can also perhaps make a Mail Merge with a Template, and that can hopefully come out looking how you need it. For heavy-duty custom document generation, you can use scripting to scratch-build PDFs. That would really…

Yup, you got it

Under Setup->Website->Setup Website

You could probably force something with scripting, but you're better off having 2 forms.

You would need to build something like a Suitelet to be able to correctly render a online-enabled form that shows parent-child relationships (maybe in a format like a sublist). You won't be able to do it using out-of-the-box online forms. But a Suitelet could do it, yeah.

Formula fields cannot run group operations. You'll need to use scripting to compile this value, or run a saved search to see the values.

Yeah I'd love to have that. I haven't found a way :(

Your field names must be wrong because custom fields always begin with "custcol_". So double check your field names, but having a formula field with store value false and the formula of {'custcol_end_date'}-{'custcol_start_date'} should work. Note that if you do it this way, the value will only be displayed when you save…

The number should be correct - it returns the value in days, with fractions being hours (e.g. 5.5 would be 5 and a half days, which means 5 days and 12 hours)

This is typically done with Suitescript

You can try a couple of debugging points yourself first. Add the following fields, and check their output to try to pinpoint the problem Formula (numeric) -> {customer.custentityuk_premuim_shipping_expiry} - {datecreated} Formula (numeric) -> {customer.custentityuk_premuim_shipping_expiry} Formula (numeric) ->…

You can use the Record Browser to determine the internal id name of a given field - https://system.netsuite.com/help/helpcenter/en_US/RecordsBrowser/2010_1/index.html The Date Created field is particularly annoying because it is not consistantly named across all records and ways to access it.

Hm. Okay, then in theory this should work - Formula (text) -> CASE WHEN (({customer.custentityuk_premuim_shipping_expiry}-{datecreated})>0) THEN 'Y' ELSE 'N' END

I haven't checked myself, but many, many fields are not available for sourcing, so this would not be unusual.

You cannot source per-location Quantities (or per-location anything, for that matter). You'll have to use scripting to fetch the values.