Alexander M

Hello @einnar82 , I guess you have copied the code example from the demo. Have a look at the "src" attribute of the annyang script. It is `` You have...

https://github.com/IgniteUI/igniteui-cli/pull/1060#discussion_r988903737

@Eralmidia can you please take a look at [this example](https://stackblitz.com/edit/all-your-memory-belongs-to-chrome), demonstrating how this functionality may be achieved.

FYI - The Grid Row Drag documentation is now updated to cover this scenario - https://www.infragistics.com/products/ignite-ui-angular/angular/components/grid/row-drag#improving-ux-in-row-drag-scenarios

@SkylerLutz The behavior that you observe is the expected for the Transaction service - this is how it was designed to work. Every time the user executes an operation (transaction),...

@SkylerLutz You can try such implementation, however do not expect it to be a simple for implementation solution. Have in mind that the transactions that your "second" Transaction Service would...

@SkylerLutz Just an idea for another approach (not that it would be easier). You can try creating your custom Transaction Service, where the "pending changes" are kept permanently and undo...