(i.e. I have a TX column that doesn't exist on all my forms)

ooh

NVL?

....but want to do a conditional field on all of them

ooh, maybe.

I suppose I could just expose that field to all the forms

as a backup plan

yeah idk if i really have done what you're doing here

All part of that ARM magic

Checking dates so I can feed the right one to a rev arrangement

but the Recurring start/end date fields don't exist on some of the Manually-generated credit memos

so even though it's at the tail-end of the CASE formula it throws an error because the field's not found

So something like this would tank out if the _sb_end_date field wasn't on the form:

even if the earlier condition was met.

(I suppose I could just NVL the whole thing....)

hah

I should just script it rather than using default value formulas

¯\_(ツ)_/¯

But this is how NSPS set it up, so, y'know

Guys a silly question - how long grace period is given to access data after the subscription expiry for Netsuite? As far as I can remember it is 30 days after expiry just wanna make sure. I am cutting off crappy TribeHR which is a Netsuite product.

Has anyone experienced the import error of "New" when trying to update employee information via CSV import?

@Shawn if you are using the internal id or external id as key then you shouldn't have any error , did you use update only or add + update option? your load file might have some mismatch - dept, subs, location or class. I tend to use internal ID values for all those fields for csv update/import, it saves you headache.

@Sam-I-Am I'm using Internal ID as key... and trying to update their passwords. The employees have all previously been created, but many have not logged in yet as we haven't gone live. We're trying to set a default pass for them with "force password change on next login". I'm getting 0 records imported successfully and the CSV response is an error of "New" for each record. I've tried "Update" and "Add or Update"

@Shawn While I have not done an Employee import yet, I looked into your issue, and noticed the "Employee ID" is readily available on our setup, but internal ID isn't, had to go into system notes to find it. You are in fact using Internal ID, and not the Employee ID? I would run a test on this, but I am currently importing 5k+ SKUs. Update should be the appropriate type of data handling.

@nlahara Yes. I created a saved search with internal id included, exported that, added a password field, and tried importing with the internal id as key

I see, and what information did you include in your password column? I ask, because you previously mentioned the "force password change on next login", which will only accept Y/N values.

Anyone have any thoughts on how to store information about items that may have varying costs based on the quantity ordered? In terms of Retailer to Vendor, not Consumer to Retailer.

@nlahara i don't think it can be done natively, but i remembered coming across a third party solution before