Nicolas Knoll

I've got the same problem. I use the IncludeGraph, but it seems that the newly created Id is not propagated to the second BulkOperation. Is there a possibility to do...

I resolved my issue by using tOptions => tOptions.ForceOutputFromUnmodifiedRow for the dependent Entity

Hello @JonathanMagnan , I think I found a workaround. I'm now setting "AutoMapOutputDirection" to false. This strips the "MATCHED" part and "OUTPUT" completely out of the MERGE statement. Which in...

Hi @JonathanMagnan, this is my code: ``` dataContext.Messages.BulkInsert(newRecords, options => { options.IncludeGraph = true; options.IncludeGraphOperationBuilder = operation => { if(operation is BulkOperation senderOperation) { senderOperation.ColumnPrimaryKeyExpression = sender => new {sender.SenderName};...

I will check on monday. Thanks for looking into this.

Sorry for the delay. I checked your new Version. I changed my ForceOutputFromUnmodifiedRow to false for the second operation and it works as expected now. Thanks again for your time.

I second this. We have a "LastModified"- Column in place which is basically a DATETIME2 based timestamp. Would be nice to be able to configure this column as the "ETAG"...

Sorry for my the misunderstanding. But isn't the RowVersion a db table column either? Sorry for bothering, I have to do a little more reading on that topic.

We have this issue currently, and cannot get rid of it. Are there any workarounds we can try?