here is the sample project and data

I was finally able to recreate the problem I was having. But before I send the whole sample, I figured I'd show this code where the last change that was made caused the problem.



The problem started when I added the rollback command after if (result != SaveUndoResult.Success). I know it doesn't make much sense to have it there because no database changes are made at that point, but I don't think it should be causing problems like this.



I'll post the sample in a few minutes

When faced with something like this.  The best advice that I have, especially since you are pretty confident on how to reproduce, is to post a simple sample that reproduces the behavior.  This way we can logically step through this and know that we are setting up the test the same as you.  WHen we do this, we come to resolutions much faster than going back and forth via forum posts.

Trent,



you were right about the an exception occuring. What I had to do to see it, though, was to install the SF source code. Then I was able to see the handled exceptions, but I'm still confused about what's happening.



The first exception that's hit is in SetPropertyValue: "Object of type 'System.Int32' cannot be converted to type 'System.String'."



The line is 188:

GetPropertyInfo(OwnerType, PropertyName).SetValue(Owner, Value, Nothing)



based on the comments there, this is an issue that you've encountered before. Also, it looks like the code that would work for me has been comment out.... ?





Got any advice?



Thanks,

Govinda

Hi,

May I know if SF team is checking on it?

I need it to be solve urgently.



Please advice.

Thank you

Still getting this weird behavior. Maybe I'll cook up a batch of programming funkiness.



Throw in some.... I'm not handling BusinessRulesCheck so I'm not influencing a force save.



And a little... there's no exception occuring in Common Language Runtime (thrown or unhandled).



mmmmm... This might be strange too, on the second save, the BO.CurrentRow.RowState == Added. I guess I should mention here that the testing I've been doing after finding the problem has been to create a new row, skip a required field and hit save. The second save is where the problem is. So it makes sense that the row state would be Added, but based on your previous comment, Trent, the BO should detect this and set IsDirty to true. But it's not.



And an extra dash of weirdness... on the second save, when my code sees that the save result was "success", I call TransactionCommit("") (I just noticed this), and after that line, IsDirty is set to true again.



mmmm... smell that?

Hi,

In my case, the exception thrown caused by database FK constraint. I am able to catch it and call BusinessLayer.TransactionRollback(). However, the IsDirty doesn't return correct value.

Why don't TransactionRollback() call ResetIsSavedOnTransactionFlagOnBusinessObjects() ?



Thank you

I am using transactions. I'll try running through it in debug mode with that setting in the Exceptions dialog set.



Thanks guys, I'll let you know how I make out.

Chan has a point about the transactions on his other post.  If you are using transactions, this could have an effect as well.

In any of these cases, the very first thing that I would do, is look to see if an exception is being thrown anywhere and just now showing up.  The best way to do this is to put your app in debug mode, run it, and then before you execute the code that is failing, do a Ctrl+Alt+E (default shortcut) in Visual Studio which should show the Exceptions dialog.

Check the Common Language Runtime Exceptions action:

Click OK, then go execute the code that is failing and see if any exceptions break.  This would be the first place I would start.  Remember to turn this off later otherwise you will see a lot of exceptions that are not actually causing issues and could be legtimatelly thrown and handled exceptions.

Well, I am unsure of exactly what is happening to you, so let'st just talk about how it works which may help you out.  The IsDirty flag is a dynamic property meaing that it reflects the internal DataTable to determine if there are any modified, added, etc. records.  So the only way that this property will reflect a False is if there is nothing modified within the DataTable.

Now if an unhandled exception occurs, then you can start to have goofy behavior like this.  But the Save will always stop unless you handle the BusinessRulesChecked event and set the e.IgnoreRulesAndForceSave parm to True (The property name may be slightly differently named that what I posted...but it will be close ).

I would imagine that it is one of these elements that is causing this.