SEARCH
RSS Feed
Knowledgebase : NotifyLink Enterprise Server > FirstClass
Device created tasks/events with identical subject/description d...
Tasks created on the device with the same subject/description as a task previously created on the device may not appear on the FirstClass server, even when other fields of information on the task are not identical.  This same issue has been observed fo...
Event location field has a maximum of 1024 characters
Information: The FirstClass server will truncate the location of an event if it is longer than 1024 characters.
Low Priority status on a device created task is not synchronized
"Low Priority" status on a device created task is not synchronized to the FirstClass server (FirstClass equivalent is "Priority Bulk"). On the server, the task priority shows as "Normal" on the task dialog window priority d...
Meeting invitations are not removed from the device if deleted b...
FirstClass: If a NotifyLink (NL) user's accepted meeting invitation is deleted by the organizer or the organizer removes the NL attendee from the meeting calendar event, the NL user's calendar is updated on the server, but not on the device.  The even...
NotifyLink LookBack/LookAhead ranges are ignored in FirstClass
LookBack/LookAhead ranges set in either the NotifyLink Administrative or Client web under "Calendar Sync Settings" or "Task Sync Settings"are ignored.  Calendar event and task synchronization ranges are governed by the FirstClass se...
PIM fields that do not synchronize between FirstClass and Notify...
First Class:Some PIM fields will not be synchronized between FirstClass and NotifyLink.   Calendar Event Fields Contacts Fields Tasks Fields Supported fields that do not sync -Middle name -Personal Email -Personal Web Site -Quick Name (DisplayName) ...
Remote lookup fails when more than 20 matches are encountered in...
First Class:When issuing a lookup where the results exceed 20 matches, the LDAP search failed and either locked the device or returned an error message details: ERROR: LDAP SEARCH failed. Issuing a remote lookup on the device should return results for 2...
Tracking notifications cannot be implemented for FirstClass user...
First Class:The folder necessary for tracking notifications cannot be created in FirstClass, thus email/PIM tracking notifications to the device cannot be tracked.  "Track Notifications" enabled in the Server IT Policies > Control Options wil...
A change to an all day event on the device does not sync correctl...
First Class:When an all day event is edited on the device, the change is synchronized to the FirstClass server, but the "all day event" box becomes unchecked and the event duration is set to 23 hours 59 minutes 59 seconds.
A change to an all day event on the device does not sync correctl...
When an all day event is edited on the device, the change is synchronized to the FirstClass server, but the "all day event" box becomes unchecked and the event duration is set to 23 hours 59 minutes 59 seconds.
Adjust configuration file to remedy PIM "slow sync" conditions
Several 'slow sync' issues experienced with NotifyLink may be rectified by adjusting a configuration file setting on the FirstClass server. Behavior: -PIM Slow Sync resulting in mass delete/add of PIM items -Errors in the FirstClass log, such as: PENDIN...
Changed meeting invitation results in duplicate meetings on devic...
FirstClass: Accepting the original meeting invitation on the server synchronizes the calendar event to the device. Accepting a change (in description, notes, location, time, etc.) to the original meeting invitation event on the server, synchronizes the...
Changing the recurrence pattern on the device does not change it ...
FirstClass does not allow the user to change the recurrence pattern on the server or the device.  Therefore, if such a change is made on the device, for example changing an event from Daily to Weekly, it is not changed on the server.
Contact changes must include change to phone or address field to ...
Contact changes made on the device will not synchronize to the FirstClass server unless a change to the phone or address field is made as well.  If a change is made to the notes field, for example, but the phone or address fields are not edited, the ...
Contact Email addresses must comply with accepted format
I.  FirstClass Client allows the entry of control characters, brackets, quotation marks, etc., in the Email address field of a contact.  Email addresses containing these characters, however, will not synchronize to the device.  The contact will appea...
Contacts created on device with same name don't all sync to the s...
Issue: If you create several contacts on the device with the same name, only one contact will synchronize to the server. Solution: There is currently no solution to this issue. This is an issue with the FirstClass server and will be fixed in the upcomi...
Contacts created on the FirstClass server must be marked to synch...
Contacts created on the FirstClass server include an option to "Synchronize Entity with handheld device."  If the option is disabled, the contact will not synchronize to the device via NotifyLink Enterprise Server.
Contacts updates from the server sent to a device when there are ...
FirstClass: A device created contact will sometimes cause the server, within a pim cycle or two, to send down an update for the contact to the device, but the contact does not appear changed. On the device, the updated contact appears to have a blan...
Contacts with only a first and last name do not synchronize to th...
When processed through the PIM cycle, the "Synchronize entry with handheld device" option is disabled for contacts created on the FirstClass server with only a first and last name.  Consequently, any adds/changes/deletes for the contact are...
Contacts without a name or company do not synchronize
Contacts created on either the device or the FirstClass server that do not have the name or company field filled in do not synchronize.
Deletes/Additions do not occur when synchronization range changes
If you change the "Synchronize only after date" in the FirstClass Client, no deletes or adds are sent to the device for events or tasks that fall out of or enter the new range.
Deleting calendar events , contacts, or tasks on the device
FirstClass: PIM items deleted on the device will remain on the server. Contacts deleted on the device remain on the server, but uncheck the "Synchronize entry with device" option.  Result is contact is gone on the device, but remains on the...
Deleting calendar events , contacts, or tasks on the device.
First Class:PIM items deleted on the device will remain on the server. Contacts deleted on the device remain on the server, but uncheck the "Synchronize entry with device" option.  Result is contact is gone on the device, but remains on the ser...
Events created before lookback on the device have different behav...
FirstClass: Information: The behavior for events that are created on the device before the lookback date (IT Policies -> Calendar Sync Settings) differs depending on whether the events are recurring or not. Recurring events that have all their insta...
Events created on the device must occur after the sync date set i...
First Class:An event created on the device before the "Synchronize only after date" does not appear on the server.  This "Synchronize only after date" parameter is one set in FirstClass and it overrides any LookBack/LookAhead range set...
Expected FirstClass Calendar Behavior
The following situations are expected behavior for calendar events synchronizing between FirstClass and NotifyLink. I.  Calendar events created on the server without a subject synchronize to the device with "No Subject" in the subject field. I...
Meeting invitation events created on server sync only after accep...
Meeting invitations created on the FirstClass server are not synchronized to the device until the the invitation is either accepted or accepted as tentative on the server.  The invitation itself is not synchronized to the device Inbox, but once the inv...
Meeting invitations created on the device do not completely synch...
Meeting invitations created on the device do not synchronize to the FirstClass server (older than version 9.1).  The event is added to the NotfiyLink user's calendar, but attendees do not receive the meeting invitation. This can be resolved in FirstClass ...
Meeting organizer's reminder triggers a new meeting invitation to...
When a meeting organizer's event reminder expires on the FirstClass server, it causes the server to see the event as an updated appointment.  Consequently a second meeting invitation is sent to the invitees server Inbox.  If this second invitation is a...
Modified or deleted instances of recurring events
First Class:The deletion of or modification to an instance of a recurring event on a device is not synchronized to the FirstClass server. A modified instance will appear in duplicate to the original instance on the server and a deleted instance will remai...
Modified or deleted instances of recurring events
The deletion of or modification to an instance of a recurring event on a device is not synchronized to the FirstClass server. A modified instance will appear in duplicate to the original instance on the server and a deleted instance will remain on the s...
Modifying an event on the device can clear event category
An event originally created on the FirstClass server with a category will lose the category if the event is modified on the device.
Monthly recurring event, set by position in the month, may be off...
First Class:A monthly by weekday position recurring event created on the FirstClass server sometimes shows occurrences off by one week on the device. Example:  Recurring event set on the server for third Tuesday of every month may show up on the fourth T...
Monthly recurring event, set by position in the month, may be off...
A monthly by weekday position recurring event created on the FirstClass server sometimes shows occurrences off by one week on the device. Example:  Recurring event set on the server for third Tuesday of every month may show up on the fourth Tuesday of t...
Multiple address books are not supported for FirstClass user acco...
From the FirstClass server, users may create multiple address books (Contact Databases), however, these address books are not available for selection in the NotifyLink Contact Sync Settings and thus contacts from these address books cannot be synchroniz...
Multiple carriage returns in a PIM item note field are removed wh...
This issue involves events/contacts/tasks (PIM) created or edited on the FirstClass server with multiple carriage returns in the notes field.  When synchronized to the device all but the first carriage return are removed. When PIM items are created on...
Occasionally an OTA load will not return all the items
Issue: Occasionally if you perform an OTA load on a large number of items, the FirstClass server will not return all those items. It is possible that this issue is related to the amount of stress on the FirstClass server at the time NLES requests the ...
PIM fields that do not synchronize between FirstClass and NotifyL...
Some PIM fields will not be synchronized between FirstClass and NotifyLink.   Calendar Event Fields Contacts Fields Tasks Fields Supported fields that do not sync -...
Port Requirements for NotifyLink Enterprise Server - FirstClass I...
Port Requirements for NotifyLink Installation can be found in the NotifyLink for FirstClass Pre-Installation Guide  under Pre-Installation Tasks #8, Port Requirements Port numbers used for connections with NotifyLink Enterprise Server (NLES) components a...
Random single events are sometimes created on the server
When single or recurring events are created on the FirstClass server, sometimes the server will create a separate, unrelated, "No Subject" single event that occurs on the same day as one of the user created events.  The "No Subject"...
Recurring Events created on Windows Mobile devices
This issue involves recurring events that are created on a Windows Mobile device and synchronized to the FirstClass server. Recurring events that are set to occur every weekday (M,T,W,TH,F) synchronize to the server with instances of the event for 5 wee...
Remote lookup fails when more than 20 matches are encountered in ...
FirstClass: When issuing a lookup where the results exceed 20 matches, the LDAP search failed and either locked the device or returned an error message details: ERROR: LDAP SEARCH failed. Issuing a remote lookup on the device should return results fo...
Return lines in contact fields are converted to spaces when synce...
The FirstClass Client allows the use of return lines in a Contact's Job Title, Company, and Department fields.  These will be converted to spaces by NLPim to be compatible with all device types supported for NotifyL...
Russian and Chinese characters in PIM items do not synchronize co...
First Class:Chinese or Russian characters in a PIM item, originating on the FirstClass server, do not synchronize to the device in the expected UTF-8 format.   Russian characters sync as Quoted-Printable character =1A Chinese characters sync as &#Some...
Slow Sync Status 508 error
FirstClass: This issue involves server created contacts with only a first and last name and with the "Synchronize entry with handheld device" setting enabled. If the contact is saved and then reopened before the next pim cycle and kept open...
Some recurring event patterns will not synchronize properly to th...
Recurring events, created on the device with a pattern not supported in FirstClass will only synchronize properly to the server.  Only the first instance appears on the server.    Examples of recurring event patterns that are not supported are events r...
Task completion status or subject changes on the device do not sy...
For a task that has been marked as completed, the following changes do not synchronize to the FirstClass server:    -Marking the task as "in progress" or "not completed"    -Editing the task subject On the server, the task is not mar...
Task time of midnight does not change on serve
Issue: If you modify a task reminder time on the device so that it occurs at midnight on a particular day, the server will ignore the change in time. However, it will change the date, if that was changed. Note: This applies to all task times which incl...
Task time of midnight does not change on server
First Class:Issue: If you modify a task reminder time on the device so that it occurs at midnight on a particular day, the server will ignore the change in time. However, it will change the date, if that was changed. Note: This applies to all task times w...
Tasks deletes on the FirstClass server do not get synced to devic...
Task deletions made on the FirstClass server do not get synchronized to the device.
Tasks with blank start or due dates do not sync properly
Tasks created on the FirstClass server with no Start Date and no Due Date are not synchronized to device. Tasks created on the server with a Start Date, but no Due Date synchronize to the device with a Due Date the same as the Start Date.
Tasks with the same reminder and due date do not sync properly
This issue involves tasks created on the device with the same reminder and due date (with any reminder time). When synchronized to the FirstClass server, the task appears with the correct reminder date, but the reminder time is either 30 minutes or bl...
Tasks without a Subject do not sync to the device
Tasks created on the FirstClass server without a Subject do not synchronize to the device.  If something is added to the Subject (even a space) the task synchronizes.
Tracking notifications cannot be implemented for FirstClass user ...
The folder necessary for tracking notifications cannot be created in FirstClass, thus email/PIM tracking notifications to the device cannot be tracked.  "Track Notifications" enabled in the Server IT Policies > Control Options will not imp...
Updates for PIM items are sent from the server when no changes ha...
Random updates from the FirstClass server have been observed for calendar events, contacts and tasks that have been created and synchronized.  Even though no changes have been made to the item, the device showed updates that had been received from the ...