NetSuite’s Outlook 2.0 Beta 100 Record Update Limit

After having lengthy conversations with NetSuite’s Support discussing observations about the latest .157 Outlook 2.0 Beta, it became clear that we need to clean about about 500 duplicate records from Outlook.   Our task is to first disable these 500 problematic records in Outlook from being shared with NetSuite and then delete them to get Outlook cleaned up. The synchronization client should then update NetSuite to deactivate or delete contact records.

The challenge is that the synchronization client appears to have a 100 record update limit built-in.  As such, we needed to select blocks of records 100 at a time (we did 99 records just to be safe) to allow the client to do its work.

This could be troublesome if there are many records to update.

Update July 26, 2009

After working with NetSuite support, we have decided that it would be better to clean our machine (using virtual machines, we basically threw it away and started with a fresh instance) and start again.  In this case, we have cleaned up duplicate outlook records and effectively have bypassed the 100 record update limit.

Be Sociable, Share!

Marty Zigman

Holding all three official certifications, Marty is regarded as the top NetSuite expert and leads a team of senior professionals at Prolecto Resources, Inc. He is a former Deloitte & Touche CPA and has held CTO roles. For over 30 years, Marty has produced leadership in ERP, CRM and eCommerce business systems. Contact Marty to set up a conversation.

More Posts - Website - Twitter - Facebook - LinkedIn - YouTube

| Tags: , , | Category: NetSuite | Leave a comment

Leave a Reply

Your email address will not be published. Required fields are marked *