Olivier Gagnon NC Red Ribbon

We had to do this for a customer not long ago. The solution we went with was to create Reports in Netsuite and set them as Web Query. We then had an Excel spreadsheet consume those services, and we coded up a VBA macro to format the sheet to look exactly like a Netsuite invoice our customer could then print and send out.…

Amy, You could use scripting to calculate, on the Invoice, the profitability of said Invoice, either globally or per-line (or both!). It would thenj be simple to source that information in a report or search, as the tricky backwards link following and calculations would have been "pre-handled" by the script, so the…

Our Default Sales Order Status is 'Pending Fulfillment' but we would like the Sales Order Status to go to Pending Approval if the customer is below his credit limits. [...] Is that possible either directly or through any scripts? Yes, it is.

Indeed, only the Supervisor can perform Supervisor approval (via the screen, anyway). I think you can edit the Transactions one by one and manually tick in the Supervisor Approval checkbox though.

Change the Payroll item to select the new salary one he will be using, perhaps also modifying the pay frequency. Then, untick "Use Time Data".

"do you mean environment (ie sandbox vs production)? or account? Because I can edit roles in other accounts..." Because you're logging into those accounts... NS unifies your accounts under your login credentials so you can jump between them easily, but you are still fundamentally logging into another account

No. Roles can only be edited in the account they exist in. However, note that when you refresh your Sandbox, the Sandbox will be a copy of Production, including any roles that existed in Prod at time of refresh.

You would need to create a Custom Employee Form that does not show the Access subtab, and then restrict your new role to be only able to use that specific form.

No, you can't

Note that this won't stop the users from having access to the fields via saved searches. So if you want to hide because it's confidential, that won't work.

This is a pretty standard request actually. Has anyone checked in the bundle repository? I think someone exposed a non-financial full access role. Could be wrong though.

That would indeed be possible, however, it would not restrict a person from outputting the record as part of a Saved Search. It would only sopt them from being able to edit the record and look at in in view mode. But everything could be outputted from a saved search, unless you also restricted searching permissions.

Hmm, try Lists->Publish Forms

NS does not have anything out of the box to handle this. You could duplicate all your service items to create an Hourly and a Daily version of them, and then rely on users picking the right one. Otherwise, you'll want to use scripting to control rates on service items.

From an email I sent internally when we analysed Timesheets for ourselves: I have been doing more testing and research and have found a significant flaw. Once time is approved, it cannot be modified or unapproved in ANY way by ANYONE, including Admin. It’s locked for good. You can delete an approved entry, but you have to…

Paul, is this a defect or an enhancement request? Did NS get back to you?

I tried messing around quickly in a demo. Doesn't look possible to replicate. I would add a custom checkbox "Billed outside system" and tick that in and call it a day. Maybe you also uncheck "Billable", if you want to avoid the system trying to bill time entries if ever you decide to go back to billing in NS.

I prefer using the non-Weekly time tracking. You see the time you've been entering so far, and there is a shortcut when you enter time in that if you click on a Customer/Project, it selects it for your new entry, and same if you click on the Service Item. Annoyingly enough, it doesn't work with the Task though, but hey,…

2015.1 resolved most of the problems with Timesheets, and they are quite useable now. You can now unapprove time and then edit it or delete it. Time Entry CAN be customized with scripting so if that's your only reason you may want to revist. In general, Timesheets are more complex and will serve companies with more…

Unfortunately I don't have any test accounts with Payroll enabled. I know the Payroll module is, when properly configured, able to track PTO (I don't recall seeing the "time in lieu" terminology though, so maybe focus on searching for "PTO"). Maybe your best bet is simply to reach out to NS Support to open a Case.

Are you using time in combination with the Payroll module?

Yeah this was a tipping point for us NOT to adopt the new Timesheets. I tried various workarounds but I have the same conclusion as you - once approved, that's it that's all. Not very well thought out...

Time itself does not have any GL Impacts. Time receives a Sales impact when invoiced, and a cost when fed into the Payroll module and turned to a paycheck. If you do not have the Payroll module, you will need to continue using Journals to give Time a cost impact. A customization could be built to automatically flip Time…

You can either ensure people enter time in 15 minute increments (most people do this) or have a custom field on the Invoice that truncates numbers. The first method is much easier. You can enforce with scripting if you want.

It's not a matter of modifying any fields. This can be fined tuned to whatever behaviour you prefer, but the simplest might be to have a On Save client side script that reads the date, figures out if it's "too late", and if so alerts the user and refuses the save.

Time Records can be configured to lock down once they've been billed to the customer. That isn't quite date-based, but it may fit your needs. Otherwise, scripting may be used to block records based on dating.

In this scenario, CSV Upload cannot simply append to existing text. You will need to Export all your values to Excel, then use some simple formula to append the new values to the existing string, then reimport the whole thing into NS.

No, the text type should not cause problem. I would investigate if there isn't custom logic (script or workflow) impeding your update.

Well CSV cannot update disabled fields, but it sounds like you correctly dealt with that by switching to the Standard form. So, not sure what the issue could be. Silly question, but do your custom fields correctly have their "Store Value" box ticked in?

Did you actually map to the fields? Are the fields "store value false"?