As I had posted before, this is actually a fairly complex request.  It isn't just a matter of setting the row state, it entails dealing with many handlers, bindings, etc.  In a simple scenario, it would be a pretty simple problem, just make the row state match the source record.  But the problem is making this work in a scenario where binding has been implemented.  This is still on our radar, but until we test this in all of theses scenarios, we cannot do a "quick and dirty" release.

That said, we still have this on our list.

It is on the list of enhancements. I'll pass on your "Up vote" for the feature to the development team.

Oh, yeah, I see what you are talking about.  I have actually had this issue before myself.  This is actually quite a bit more work and why I didn't implement it when I ran into it the last time.  However, I still think that this is a good request and will add it to the list to look at again.  Thanks.

Hi,







Yes.







Currently, SF BO always acceptchanges after copy data. It caused datarow.rowstate = unchanged. I need a overload to preserve it so that copied datarow.rowstate = added / modified.



Thank you

Are you referring to the CopyDataFrom having an overload to prevent the RowState from changing?  I assume that is what you are referring to, which would be easy to do, but I just wanted to clarify.  Thanks.

Just FYI, you could force this right now in another line of code:

Hi,

Firstly, I would like to appreciate the enhancement made to CopyDataFrom method which only copy data from column that exist in target table.



I would like to ask for enhancement to have additional option whether want to preserve the data rowstate. It is very usually while we are working on feature like copy, import data from other txn (import purchase order txns to purchase invoice) and etc.



Thank you