The webstore pages can be branded - yes... but they are not 100% same for same functionality as the system.netsuite.com Customer Center login. For example - @ system.netsuite.com (where you can't brand the login page)*, you can easily add searches, tabs and other things via the role and configuration... MANY of those…

Either nobody likes me or my questions... or - every question I post has no answer... either way... :eek:

Depending on how involved you want to be and how much infrastructure flexibility you have in-between the systems, off the top of my head, you could: 1 - Scheduled Saved Search with a CSV / Excel file attached to the email and have that mailbox have some sort of process that pulls / parses and uploads into the other system…

Here's the resolution... 1) Import SO's THEN export Internal ID / External ID of all SO's 2) Import all Invoices as standalone invoices THEN export Internal ID / External ID of all Invoices 3) Use Excel VLOOKUP (or perl script) to align SO Internal ID with Invoice Internal ID's based on External ID's of both and their…

Thanks for the response Oliver. I had kinda considered that approach but I'd have to write the script and then see what happens when I import the linked payments :)

Just to keep a running account of this - I don't think I can articulate how god awful this process is... It's very clear NetSuite does not want to make this easy. Here's an example: SO #123 has 2 items on it: (LINE 1) 1 Big Hat and (LINE 2) 1 Big Shoe (LINE 3) 1 Big Shirt I import 2 custom records for 2 different invoices…

@Oliver - so I got back to this... and the approach isn't half bad... BUT... The SO/Invoices I'm importing are from an accounting system where a SO might have a single line that looks like this "Qty = 1, Item = 3 month subscription, Amount = 3000" Then that Item would have 3 Invoices to be imported against it - each for…

Yeah - it was an inventory setting (and it's a NII)... custom fields had shifted the "min qty" box off the screen and I missed it! Got it working now... playing around with the best way to actually "implement" now... I have more work to do... thanks so far!

Keep in mind if you import "standalone" invoices (invoices without a created from), and those items contain Inventory Items (or Kits or assemblies, etc), the Invoice will cause the inventory to deduct. So if you already had a SO->fulfillment, you'll be double-deducting inventory. Also, your SO will remain Open. Yes -…

Sorry if I'm asking a silly question, but have you tried customizing the transaction form to see if the field is unchecked? You betcha - first place I went... even tried Standard Form. :) It's checked "visible" on both - but it's not in the UI. Also - if you script at the field nlapiSetFieldValue('lastinday', 'T' | 'F') -…

@Pablo - it's submitting a custom record - from within a Suitelet. Here's the thing - after reviewing the code farther - there are 2 types of records that the Suitelet can create based on the data it collects in it's forms... One is an "inbound" and the other is an "outbound". The records are basically the same - same…

Just opened a case and asked to be attached to the defect. Thanks.

Multiple ecom sites are slow for us as well - so slow customers are clicking "Continue" multiple times and causing checkout error emails.

Hello, The issue is now resolved. A fault in our Web tier resulted in decreased performance for hosted web sites/stores for all customers on version 2010.1. No other portions of NetSuite's service were impacted. Our monitoring detected the failure and it was resolved as soon as possible. We are currently performing a root…

Have you tried - on the record.create(), setting the init parameter for the customer field to the employee value? It's one of those weird UI filtered fields - I think that worked for me once before - not on a timebill tho :)

Ever create a SS 2.0 script (or migrate one from SS 1.0) only to find an unsupported or non-working API call Every - single - time.

Sounds like it it is related - but I didn't open a case.

This is a nice resource

None that I was ever able to access - instead I ended up scripting the field update. I think when I was trying that someone from support weighed in and told me that by design the external ID is not meant to be "accessed" in that manner... which actually makes a lot of sense given it's a FK. Script or update import are your…

Currently - as cool as workflows can be - they can't see lines in sublists... so - line items on a transaction can not be interrogated by workflow. There's just no way to do what you want to do without a script. The script itself isn't that difficult to write.

@Expandasign - are you trying to send it from the same workflow (sounds like you are - 2X from state 1). Try calling another workflow that's basically the same and bounce people back and forth between the 2... that may work for you. Enter workflow A -> State 1A -> State 2A -> State 3A -> State 4A (go to workflow B)…

Off Topic - BTW would SO much prefer the form field colour to change when mandatory rather than the '*' - give us the option at least. You can really make your form look however you want if you go with HTML and then embed the tags behind the scenes inside HTML comments tags... just use the contents of a given tag as the…

When NS creates that record the owner of the record will be -System- When you, me, or any UI user enters a Lead (customer Record) via the UI - it gets the "Owner" set as them... So you have 3 options - one may be better than the other depending on your business processes... ONE - add "owner != -System-" in the criteria...…

@evan - how did you manage that - anything that's client side prevents a join... From an Opportunity, which has a Sales rep, I want to set the Department on the Opportunity to that of the Department of the Sales Rep... Any client side option tells me in the workflow engine I can't do the join... Parameters: Field =…

@evan & @MChamma - I think I'm trying to do the same sort of thing. I need to pull the "Department" off of a Sales Rep on and Opportunity and set it ON the Opportunity. The problem is - you can't do any sort of "join" client side in a workflow... So when you choose the "Before Submit" action - there's no handle in the…

Thanks for the idea but I had already tried this and it won't work... (and tried it again) I guess I wasn't 100% clear - the Opportunity form uses Sales Teams... so the sales rep on the Opportunity is based off of the team set on the customer... so when the customer is selected on the form, the sublist not a single…

(borrowing sbuttgereit's soapbox) - Another thing it would be nice to see in regards to workflows is a updated SuiteScript Records Browser that shows which fields you can - and can NOT act upon with workflow - as opposed to trial and error... and the wondering if "the next release will break it". It really is just silly…

@MChamma - not yet but I will. Of course beta = live next week so maybe I'll just wait and see. Although I'm not convinced it will work there either. I already tried something like that in this release - I use after submit to call another workflow to do the work described above and it didn't. Workflow history on the record…