3:17 pm Eastern Time US - Down and out, no access up 4:07...

Found the problem. A custom checkbox which has (until today) been returning 'Yes' when using 'nlapiGetFieldValue()' is now miraculously returning 'T'. Time well spent? You be the judge... -Steve

I noticed this before as well. There are some that will return "Yes" instead of "T" when doing nlapiLookupField. It's pretty random to be honest. So I have had to build a wrapper around the getFieldValue to check for checkbox possibilities of 'Yes', 'No', and 'T', 'F'. And, just to be safe, I threw in 'Y' and 'N'. Did I…

I believe this issue is 131239 which is fixed and due to be released in our 2007.2 release in Feb/March. Thanks, -e March 2008? Come on now... Was working in 11.06. 9 months to correct?

I see this same badly formatted popup when trying to delete a customer, except in our case the customer record isn't inactive, it's just a bogus customer we created while testing. I deleted all the sales orders etc. from this customer, but still I cannot delete the customer. Help? -Darren Did you give access to the…

Actually the login audit trail should not be a problem any more. Let me know if it is. Thanks, -e When was that updated because I need to go back and remove a lot of records? I do not recall reading any release notes on this and thought I had tried not long after 2007.0 without success... ...but good to know it's not an…

I had the fix moved into our next week's release currently scheduled for the evening of the 4th. Thanks, -e Exceptional... Thanks. -Steve

The change in 2007.0 was to make it easy to delete entities (leads, customers, vendors, etc). We didn;t make any changes for User Roles, can you just inactivate them? Thanks, -e Yes, that's what we do now, but over time there is so much junk we have inactivated, it is just plain messy. As either we learn how to do things…

When a record has child entities, it means transactions or other records have been made involving the record you are trying to delete. For example, you cannot delete an item if it has been used on a transaction. You cannot delete a customer that is associated to contacts or other subcustomers. You cannot delete these…

OK, this thread seems to have gone cold, but I'm getting the same thing trying to add a subtab to a custom record. This is a straight forward simple everyday thing. Create a custom record, add some fields and so on. When I try and add a subtab, bam: Items you have requested in the record have been deleted since you…

Update. I am experiencing this in one client's account only. I can add permissions, change/add fields, forms, etc but cannot add a sub-tab without the following error on save: Items you have requested in the record have been deleted since you retrieved the form Obviously this was an issue before and I haven't deleted…

I've come to the conclusion that this is an ERROR in NetSuite. I cannot add subtabs to any custom record. All attempts, regardless of name (role = administrator), causes the exact same error: Items you have requested in the record have been deleted since you retrieved the form Is anyone else experiencing this or is this an…

slarsen, I think you've run into a beta anomaly. -John Oh that would be great if that is so. Thanks.

We were migrated to 2007 on Friday 7/20. Since we get CSV lead files from most all of our magazine advertisements, we were looking forward to the new import wizard. However, we have been unable to get a successful import even though the wizard accepts the file. We watched the import job status only to get the message:…

All, the import ability in version 2007 is not as easy as it looks. You still need to use templates/fields from templates. The best way to accomplish this is to work with support and select the csv import option. I found it pretty intuitive. You still need to use templates but only from the standpoint of mapping (and to be…

Steve, Did your upload work in Beta? Don't know. Working with another client today. Will look on Thu and let you know. However, I have not received any 'Import Success' email so that probably indicates it never happened. -Steve

I thought that might be the case. I was able to get some smaller uploads to import successfully, however now I am getting unexpected errors and it says I am not mapping the fields right (mapped identical to the tests that were sucessful). grrrrrr OK, maybe not the right thread, but I just started testing 2007.0 beta today…

Show us your ***emblies. Whoops, can't say that in here now... :( But I really like manufacturing items... Or p***word, or m*** update, and so on... We'll need new code words.

In 2007.0 the system will give you details of exactly why you can not delete entities (customer/leads/vendors etc). We have also eliminated several roadblocks that prevented deletion. In particular newly created leads from the web should be deletable. You may want to try on beta when you get access and report back. Thanks,…

The original post in this thread was at 10:26 PM Pacific. This corresponds to the planned maintenance which was in progress at that time. I confirmed with our monitoring and logs that there was no disruption at 7:30 PM Pacific. Doug Brown Yes, you are right - my bad (thought about that after I posted - sorry). Seems…

The scheduled maintenance on May 25, 2007 ended at 10:34 PM Pacific Time. Notification of this planned event was posted on the login page starting Wednesday May 23. Doug Brown NetSuite Engineering Operations That would be 10:30 PM Eastern time (7:30 PM Pacific). What time did maintenance down being?

Evan, I believe HTML supports a "ReadOnly" attribute. In this case the data is displayed to the user, can not be changed, and is posted. ... I believe most NetSuite users expect the READONLY behavior. How about changing or add this as an attribute? I concur. -Steve

Erik, I think you need to check the "Show" checkbox for hidden fields so that it will be included in the HTML code but will not be displayed. HTH. I don't think that is true is it? I write to hidden fields and write to inline text fields routinely. Inline text, depending on the implementation may not "display" your changed…

The problem (fields disabled on the fly do not post) only applies to fields that are not marked as disabled in their definition or on the form, but are instead disabled using the SuiteScript nlapiDisableField call. A workaround is to mark them as disabled, (possibly) enable them on page init, and then disable them…

Actually we have a way to make disabled work correctly without using READONLY, which actually behaves slightly differently froma UI perspective. We are looking at this now. Thanks, -e That's great Evan. One other request. Please let us know if you do make this work as I have code implementing the workaround in several…

Your general license agreement (the one an officer of the company would have had to sign initially), should contain the following clause. If it doesn't then I would execute a change with NetSuite immediately (although policy would likely be the same for everyone with or without the clause). 5.12. Confidential Information.…

It is basic HTML/Browser behavior that disabled fields do not post their values. You can log an enhancement and we can potentially implement a workaround for this. Or, you can try re-enabling the fields in saveRecord. Thanks, -e Yes, I did re-enable on save. Just did not put two and two together in terms of posting…

I seem to remember the subscription agreement including non-disclosure terms. NetSuite employees are bound by that non-disclosure. However, given that, if you're using a hosted product and expect your IP to be protected as it would if it were in your own environment, then you're being naive. Your IP is protected only to…

Can't even get to netsuite.com Notice The database you are trying to access is experiencing difficulties and has been taken offline. Please try again in a few minutes.

Our license agreement has a section 5, but no subsections (i.e., 5.1 to 5.12). As I said, it is a very old license. - Miguel Would recommend you contact your NetSuite sales rep and get it updated. I don't think that is an unreasonable request.