1. Go to Setup > Customization > Install Bundle > List, and click Update next to Celigo CloudStorage File Browser.
2. On the next Preview Bundle Update screen, Select “Update and Preserve Data” option under the action column. Click Update Bundle to complete the process.

The following is required from the client (pre-install):

• Administrator credentials to the NetSuite account.
• AWS Access Key ID, and AWS Secret Access Key

Installing the Celigo CloudStorage File Browser Bundle:

To install the bundle for Celigo CloudStorage File Browser for NetSuite:

1. Log in to NetSuite using the Administrator role, and then go to Setup > Customization > Install Bundle.
2. On the Install Bundle screen, in the Location field, select Production Account.
3. In the Account ID field, enter TSTDRV181091, and click Search.

Click the Celigo CloudStorage File Browser link to open the Bundle Details page, and then click the Install button. On the Preview Install page, click Install Bundle to complete the bundle installation process. Once installation is in progress, you are redirected to the Installed Bundles page, where you can keep track of the installation progress. Once the bundle has been installed, the Install Status should change to Succeeded.

The following NetSuite actions are required from the client (post-install):

1. Go to Setup > Custom > Celigo CloudStorage Bundle Settings.
   You may need to logout, clear your browser cache, and log back in as Administrator to see this option.
2. Verify that you receive the message “CloudStorage bundle settings updated successfully.”

To set permissions for the Celigo CloudStorage File Browser:

1. Go to Setup > Customization > Scripts, and select Suitelet in the Type field. Click Deployments next to Celigo-AS3_NS Top Nav Builder. If the deployment record does not open automatically, click Edit next to the record. Click the Audience tab, select the roles that need access to the Celigo CloudStorage File Browser, and click Save.

   

2. Go to Documents > Files > File Cabinet > SuiteBundles > Bundle 9385, and download the crossdomain.xml file.
3. Connect to Amazon S3 using S3 Fox, a Firefox add-on. Create a new bucket, and upload the crossdomain.xml file. Make a note of the bucket name you create for later reference. The bucket name should NOT contain a period in the name and must be all lower case. For example, “NetSuite.Data” must be “netsuitedata” when naming the bucket.
4. In Amazon S3, right-click crossdomain.xml, and click Edit ACL to set Everyone Read permissions.
5. In NetSuite, go to Setup > Company > General Preferences, and click the Custom Preferences tab. In the AWS S3 Bucket Name field, enter the bucket name you created in step 3. Fill in the details for the AWS Access Key ID and AWS Secret Access Key fields, and provide a value for the Pre-Signed URL Expiration (seconds) field.
6. Go to Setup > Customization > Record Types, and set Full permission to the following record types:
   • Celigo Amazon S3 File
   • Celigo Amazon S3 Folder
   • Celigo AS3 File Associations
   • CeligoCloudStorageRecordType1
   • CeligoCloudStorageRecordType2

     Note: Roles that have access to the Celigo CloudStorage File Browser also need Full access to the above record types.

7. To enable the Amazon S3 Files subtab for record types go to Setup > Customization > Scripts, and select User Event in the Type field.Click Deployments next to the Celigo – AS3 – File SubTab Manager. Click Edit next to a record type to set the role permission for viewing S3 files on that type of record.

   

To change the name of a record grouping as it appears in the Celigo CloudStorage File Browser (NetSuite Record View pane):

1. Go to Setup > Customization > Record Types.
2. Click List next to CeligoCloudStorageRecordType1.

   

3. Click Edit next to a record group to give a custom name to the folders in the NetSuite Record View pane of the CloudStorage File Browser.

   
   

To change the record type name in the Celigo CloudStorage File Browser (NetSuite Record View Pane):

1. Go to Setup > Customization > Record Types.
2. Click List next to CeligoCloudStorageRecordType2.
3. Click Edit next to a record type to match a record name to renaming already used in the account at Setup > Company > Rename Records/Transactions.

   
   

The CloudStorage File Browser is the central location for all of your AS3-stored files in NetSuite. In the File Browser, you can do any of the following:

• Organize and view files in file system, similar to the NetSuite File Cabinet
• View which NetSuite records and transactions have files attached
• Attach, update, or remove files on records and transactions
• Drag and drop files to move them between folders in the file system
• Drag and drop files to attach or remove them from records and transactions
• Search for files by file type, the record type attached to, and more

To access the CloudStorage File Browser, go to Setup > Custom > Celigo CloudStorage File Browser.

To set preferences for the CloudStorage File Browser:

1. Click the Preferences button in the toolbar.
2. Check boxes to set the following preferences:
   • Check advanced checkbox on upload screen – Check this box to have the Advanced checkbox checked by default when you upload files.
   • Show confirmation after moving files – Check this box to confirm that a file has moved when you drag and drop files to a new location in the NetSuite Record View pane or the File System pane.
3. Click Submit.

You can also the use the Select Record Type filter at the bottom of the pane to only see a certain type of records and transactions, such as customers. Once you select a record type, you can use the Search field to find a specific file or record.

To attach a new file(s) to a record:

1. In the NetSuite Record View pane, select a record name or transaction number, and click the Add button. You can also right-click a record name and choose New File.
2. In the Upload to Amazon S3 popup, click the Add File(s) button, and select the file or files you want to add. Hold the CTRL key to select more than one file.
   The files you have selected are added to the queue.
3. To add files from a different location, click the Add File(s) button again.
4. Check the Available without login box at the top of the popup window to upload all files in the queue as available without login. Files available without login can be shared to anyone using the URL assigned to the file after upload.
   You can find a file’s URL by right-clicking the file after upload and selecting Properties.
5. Check the Advanced box in the popup to add editable columns for Name and Notes to store with the file.
6. Click Upload File(s) to upload all files in the queue. The popup window closes when the upload is complete.
   Note: If you close the window, your file upload may not complete.

To attach an already uploaded file(s) to a record:

1. Locate the record or transaction you want to attach a file to and expand the folder view so that the record is accessible.
2. In the File System pane or the File Browser pane, locate the file you wish to attach.
3. Select the file you want to attach. You can hold the CTRL key to select more than one file to attach.
4. Drag and drop the file(s) to the record or transaction.

To update a file:

1. Select the file you want to update to a newer version.
2. Click the Update button.You can also right-click the file and select Update.
3. In the Upload to Amazon S3 popup, click the Add File(s) button, and select the file you want to update.
4. The files you have selected are added to the queue.
5. Check the Available without login box at the top of the popup window to upload all files in the queue as available without login. Files available without login can be shared to anyone using the URL assigned to the file after upload.
   You can find a file’s URL by right-clicking the file after upload and selecting Properties.
6. Check the Advanced box in the popup to add editable columns for Name and Notes to store with the file.
7. Click Upload File(s) to update all files in the queue. The popup window closes when the upload is complete.
   Note: If you close the window, your file upload may not complete.

To remove a file(s) from a record or transaction:

1. Open the folder for the record or transaction you need to remove a file from.
2. Select the file you want to remove, and click the Remove button at the top of the File Browser. You can also right-click the file name, and choose Remove.
   Note: Removing a file from a record or transaction does not delete the file. If you stored the record in the File System or attached the file to other records or transactions, it remains in those locations.

To delete a file:

1. Select the file(s) you want to delete from all locations.
2. Click the Delete button. You can also right-click the file and select Delete.

To search all files by keyword:

1. Go to Setup > Custom > Celigo CloudStorage File Browser.
2. In the Search field at the top of the file browser, enter a keyword included in the file name.

The search results show as you type just below the Search field. Click a file name to download it.

Note: If you do not see the Search field, you may need to make the window larger or maximize the window.

To search for records or transactions with files attached:

1. Go to Setup > Custom > Celigo CloudStorage File Browser.
2. In the NetSuite Record View, check the box to Show only records with files.
3. In the Select Record Type dropdown, choose the type of record or transaction with files attached.
4. In the Search field, enter all or part of a record or transaction name.

The NetSuite Record View pane filters to show only those meeting your criteria. Click Clear Results to clear the search results and view all files.

To search for files attached to records or transactions:

1. Go to Setup > Custom > Celigo CloudStorage File Browser.
2. In the right side pane of the CloudStorage File Browser, choose a record or transaction type in the Record Types dropdown.

The File Browser filters to show only files attached to the type of record or transaction you select. Click Clear Results to clear the search results and view all files.

To search for files of a certain type:

1. Go to Setup > Custom > Celigo CloudStorage File Browser.
2. In the right side pane of the CloudStorage File Browser, choose a file type in the File Type dropdown.

The File Browser filters to show only files of the type you select. Click Clear Results to clear the search results and view all files.

Please follow these steps in order to update your current installation to CloudExtend Google Calendar Sync.  Note that CloudExtend is currently in private beta. Therefore, please proceed with this upgrade only if  you have gotten a beta invite from Celigo.

Step #1 – Contact Celigo Support to begin the transfer

Please contact Celigo Support and request a transfer of your existing Celigo Google Calendar Sync license to CloudExtend Google Calendar. CloudExtend comes with a fully functional 14 day trial license and therefore is ready for your users as soon as the installation is completed.  At this time Support will also turn off your old Celigo Google Calendar Sync’s Calendar Import flow to prevent event duplication

Step #2 – Undeploy the Celigo NetSuite Google Event Sync SuiteScript

In NetSuite, go to Setup > Customization >  Script Deployments, and set the drop-down field “Script” to User Event, and click “Edit” on the deployment record for Celigo NetSuite Google Event Sync.  Uncheck the “Deployed” checkbox and save the deployment record.

Step #3 – Install the CloudExtend Bundle

If you do not know how to install the CloudExtend bundle please check this FAQ.  When you install the bundle you should set it to “Replace Existing Object” on every object included in the bundle.  Adding and renaming these components may cause CloudExtend Google Calendar to malfunction.

Click on the “wrench” icon next to Celigo Gmail Sync for NetSuite and select Update.

Beta 1.0

CloudExtend Google Calendar

New Features

• Support for Dummy Owner in NetSuite – It may happen that the owner of an event in Google is not available in NetSuite (in case you received event invite in Google from a non-NetSuite employee). The product has been enhanced to provide the functionality of syncing such events from Google with the Owner as a dummy employee in NetSuite.
• Choosing not to Sync Events in NetSuite – Now, by checking a field on the event record you can choose not to sync an event in NetSuite with Google.
• More Secure Google Authentication – The product has been enhanced to use to a secure key when connecting to Google, increasing the security.
• One-time Batch Sync of Events in NetSuite – The option of syncing all future events in NetSuite has been provided when the user registers their Google account.
• Support for Recurrence Exceptions – Very often it happens that an instance of a recurring meeting needs to be canceled or moved. Now, the recurrence exceptions created in either calendar are synced.
  • Due to a limitation of the SuiteScripts API, this feature is broken in the CloudExtend Google Calendar. Celigo has a workaround in place for this feature until the feature is officially supported by the SuiteScript API.

Other Changes

• Google to NetSuite event sync runs every 30 minutes now instead of 15, because CloudExtend Google Calendar is using NetSuite scheduled scripts for the batch import.
• Individual users are registered solely via the licensing manager—you no longer need to enter your Google credentials into a suitelet to get access to the Calendar Sync.  The Licensing Manager check just makes sure that you have enough seats to add this employee, and then adds him/her as a licensed user
• The “dummy employee” who owns events created in another Google apps domain no longer needs web services access for use with the sync.
• Calendar event attendee responses are not sync’d with Google because of a limitation in their API.  It will be fixed eventually—their API guide says the fix is “Coming Soon.”

CloudExtend Google Contacts

CloudExtend Gmail

CloudExtend Gmail

• When an email is attached to a Contact record, the email will also will be displayed under the Messages sub tab of the relevant Customer record.
• The button to open the Netsuite business object on the Dahsboard, will now cause the object to be opened in Edit Mode enabling the user to quickly make additional modifications to the object.
• Recipient’s email address will auto populate when composing a new email from the Gmail sub-tab on NetSuite business objects.
• Fixed an issue where the Gmail sub-tab was not displayed on the NetSuite Calendar Event record.

CloudExtend Google Calendar

• The user-level configuration or the user’s Web services credentials are no longer required for the proper handling of recurring event exceptions. This feature is now supported out of the box, with no additional setups or configurations.
• Fixed an issue that caused events created in certain timezones to be synced incorrectly between Google and NetSuite.

CloudExtend Google Docs

• Fixed an issue where the search displayed the first page of the results when multiple pages of results were returned.
• Fixed an issue with handling long file names.

CloudExtend Google Contacts

• Few minor bug fixes.

Known Issues and Limitations

CloudExtend Google Contacts

• Contacts created/updated in NetSuite are updated in Google in real-time. However, due to a limitation in the way Google Domain Shared Contacts list works, it takes up to 24 hrs for the changes to propagate to individual user’s (i.e. it may take up to 24hrs before a new contact will appear on the Gmail compose window’s auto complete list).
• Changing a contact’s primary email address from Goolge Domain Shared Contacts List will cause a new contact to be created in NetSuite rather than the existing contact being updated.
• Duplicate email addresses are not supported.
  • If the same email address is assigned to more than one Contact record in NetSuite, the sync will update only the first Contact it finds.
• The current version cannot import Google Domain Shared Contacts Lists that contain over 5000 contacts. This limitation does not affect the exporting of contacts from NetSuite to Google and therefore is considered a low priority concern.

CloudExtend Google Docs

• Upload File Size Limits (Note: These limits apply only when conversion is turned on. When it’s off, files up to 5 MB can be uploaded).
  • Convert documents – up to 1 MB per file:
    • Microsoft Word (.doc, .docx), OpenDocument text (.odt), StarOffice text (.sxw)
    • Rich text (.rtf), Plain text (.txt), HTML (.htm, .html)
  • Convert presentations – Less than 5 MB per file*:
    • Microsoft PowerPoint (.ppt, .pps)
  • Convert spreadsheets – Less than 5 MB per file*:
    • Microsoft Excel (.xls, .xlsx) files,
    • OpenDocument spreadsheets (.ods).
    • Comma-separated values (.csv)
  • Convert drawings – up to 2 MB per file:
    • Windows Metafile (.wmf)
  • Convert text from PDF or image files – up to 2M per file:
    • Photos, scanned documents, screenshots, etc (.jpg, .png)
    • PDF files (.pdf)

* Google Docs allows over 5MB files to be uploaded for these file types. However, as we are uploading through a NetSuite suitielet, we are bound by a NetSuite limitation that allows the entire upload size (file + metadata) to be limited to 5MB.

• An existing Google Doc cannot be overwritten (or updated to a new version) by uploading a file with the same name. In order to update a file (such as an image) attached to a record, the user has to attach the new file and remove the old attachment.
• Attached files deleted or renamed in Google Docs, will not automatically be reflected in NetSuite. Click the “Refresh” button to update the list once a document is renamed.
• Refresh button will only detect renamed/deleted files for the first 500 attachments of a record. E.g. if the record has 510 attachments, refreshing will detect only the changes to the first 500.
• The time taken to complete a refresh may drastically increase with the number of attachments starting with a little over 1 second per attachment.
• The number of attachments per record is limited to 10,000. In general, we do not recommend attaching more than 500 documents per record due to the above refresh limit.