Nov. 9th is the target date we hear but plan for sometime in November. Frank

Scott; Thanks for the correction – however is there a later version than Intellisync 5.5.0 (build99) available with 2007.1? Frank

It is indeed real. Saw the new version at Partner Conference yesterday with my own two eyes. Sweet. Major improvement. Looks likes it solves most problems surrounding Intellisync and legacy Outlook Integration. Only one tool necessary. Trashes the sync category for those of you familiar and uses NetSuite-like search…

No help, just a ditto on your predicament. Serialized inventory tends to be higher value inventory for my client base so from a dollar perspective the lack of capability to get at serialized data (reporting and otherwise) gets noticed quickly. I’m no guru but methinks exposing the serial sublist as a scriptable record…

Evan; Thanks for the reply – however when I return false (below) I can tab off the field and eventually save the incorrect info. What am I doing wrong? function itemFieldChanged(type, name) { var item_dash; if ((name == 'itemid')) { if( nlapiGetFieldValue('itemid').indexOf('-') != -1 ) { alert('Dashes Not Allow In Item…

Evan/Yang; Exactly! This is on the Item entity form – works perfectly with Validate Field. Thanks for the great support! Frank

Sean; Outstanding and thanks so much. We’ll give it a whirl! Frank

Saw the new version at Partner Conference yesterday with my own two eyes. Sweet. Major improvement. Looks likes it solves most problems surrounding Intellisync and legacy Outlook Integration. Only one tool necessary. Trashes the sync category for those of you familiar and uses NetSuite-like search approach on the Outlook…

Any help or ideas on this? TIA; Frank

Nope, just the message INVALID_KEY_OR_REF. Here is my error code: catch( e ) { if ( e instanceof nlobjError ) alert(e.getCode()) else alert(e.toString()) } Can if modify to see the field in error? Frank

Yup, tried True and False with same result. Thanks for the suggestion. Frank

Ah…..movement. I now get “Invalid price reference key 1”. Not sure what it means, I’m researching. Any clues you might suggest? This is a saved sales order I’m updating. Thanks; Frank

I really need an answer on this or a possible workaround if truly a bug. Any help?

Matt; Sorry – I am indeed in a server side script; Frank

Matt; This is a User Event on beforeLoad, so I choose option#1 (no internalid). However I don’t want to commit the record to the DB, just present. How then do I display my record object? Thanks so much; Frank

Yang; I don't see float as an option on the custom field "type" dropdown. Am I missing something? Thanks; Frank

Yang/Evan; Any further thoughts or suggestions on this topic? Thanks; Frank

Yang; Still no joy in "hooterville" yet. Back to original problem - if I use 3.3, 3.5, 5.12 or another decimal it shows 3.0, 3.0 or 5.0 on the timesheet respectively, ignoring the decimal. Ideas? Thanks; Frank

Tried but no help yet. I did however notice different behavior suggested in your reply on the Time Tracking form. If you put in 3.18 it changes it to the 3:11 (with a colon). Must be a different field type?

Yes! Almost there! It took the literal ‘5:12’, so now I’ll create a routine to manipulate the time. Thanks for hangin’ in there with me! Frank

Yang; Not sure what to do then. My script is server side (User Event - does that matter?). If I set my custom field to integer I cannot enter a decimal. How do I define the custom hours field then and use it in a script? Thanks; Frank

Yang; Once again thank you very much. That will work just fine. Frank