|
Folders with Errors |
  
|
|
Folders with Errors |
|
Folders with Errors
CGX (and all new CG products) use MAPI to retrieve Contact information since it is the only way to rapidly retrieve contact information from Outlook.
Unfortunately, there are cases where MAPI indicates that one or more fields within a given folder cannot be retrieved for no apparent cause or explanation. There is no ryhme or reason as to what fields can encounter an error but once encountered, experience has shown that it cannot be bypassed. The only way to retrieve any field that has reported such an error is to use the Outlook engine (otherwise referred to as the Outlook Object Model or OOM). Unfortunately, using OOM degrades performance to extremely unacceptable levels for very large contact folders. However, sometimes getting the data is more important then the time it takes to get it.
To that end, CGX (and all new CG products/versions) will automatically <fall back> to using OOM if any field is selected that is reported as having encountered a MAPI error. This scenario can occur on any folder whether or not a custom form is used.
An example of a selected contact folder with some MAPI field errors is shown below along with how CGX identifies those errors:
Two things change when a folder with errors is encountered:
| 1. | The number of fields within the folder (with or without a custom form) that have incurred the error along with the number of error fields selected for <Export>. In the example above - there are 6 fields within the folder with an error, one of which has been selected for <Export>. |
| 2. | Fields that have encountered an error are highligthed in red |
CGX will only fall back (revert) to OOM when a field with an error is included in the export map.
There is no way to duplicate this issue "at will" - it either occurs or it doesn't. This problem was discovered after reviewing several hundred customer supplied custom forms at which point it was also noticed to randomly occur on internal test folders with or without any custom forms being assigned or even published to the folder.
We have also found that sometimes the problem fields disappear when a new folder is created and the contacts copied to that folder. Other times, problems remain but with a completely different set of fields. In short, this is not an issue that has been attributed to any CG product since using the same program code on different folders with or without a custom form can produce entirely different results.
Some sample results of the what we've encountered:
The reason for including this information is simply that there is no way of knowing whether or not the results we have shown above will occur with your Outlook folders (we have more examples of folders with no errors (reviewing hundreds of custom form examples supplied to us by customers) then we do of those that do encounter errors). However, if it does occur with your folders, it is not something that the code used by CG can address but strongly urge to contact us with your examples in our continued effort to find an explanation for this issue.
To assess your folder - refer to the Tools (Custom Form Info) section of CGX.