Export-only call-based ECMA Exception handling broken
Has anyone else seen this?
If you have a call-based ECMA configured as Export-Only and in the ExportEntry() method you throw a "EntryExportException", the exception goes into the event
log but it doesn’t appear in the Sync manager UI as an "entry-export-error" and the export is treated as completed (no longer a pending export)
If you switch to "Import and Export", it works properly - you get the UI message and it's re-queued for export.
(Sync service build 3576.2)
**several other issues as well..btw..
July 13th, 2011 9:21pm


