Another thing I would find useful at present and I think we have touched on before is the ability to cancel an entire import rather than have to do it for individual records using an ImportProvider.RecordImporting event handler. This is particularly a problem for my customer that has a load balanced setup and the import gets triggered on slave as well as master servers and on occasion results in duplicated imported content.
It's something that is on the list. Propably V4. But to set excpectations. A cancel at 50% of the import process will not rollback the imported records.
Allow Cancellation of Import not just individual records
Hi Richard,
Another thing I would find useful at present and I think we have touched on before is the ability to cancel an entire import rather than have to do it for individual records using an
ImportProvider.RecordImportingevent handler. This is particularly a problem for my customer that has a load balanced setup and the import gets triggered on slave as well as master servers and on occasion results in duplicated imported content.Cheers, Simon
Hi Simon,
Completely agree with you.
We faced the same issue.
Sometimes, our users start the Import, and then want to cancel it, but there is no such an option. And even "App Recycle" does not stop the import.
It became worse when two or more imports are running at the same time. In this case we may receive DB deadlocks and performance problems.
Richard, It will be very helpful if this feature will be included into the nearest release.
Thank you
Hi,
It's something that is on the list. Propably V4. But to set excpectations. A cancel at 50% of the import process will not rollback the imported records.
Best,
Richard
Hi Richard,
Well, most of the time that's exactly what we need.
Also, it will be a awesome to have some kind of trigger in "BulkImporting" and "RecordImporting" events which can cancel import "in progress".
Thank you
is working on a reply...