First of all I'd like to say that this is most likely a problem with the way the page is contructed by me. I know that because I created a small test web app that does show what I'm about to explain.



I coded this page doing testing here and there. One day I was on a record that was saved before I had set the require fields validation on the BO. I saved the record, saw the validation error message for one of the required fields being blank, and for some reason I just hit Save again. To my surprise, the form saved successfully. Or rather, the BO.Save() method return "Success". After some digging I found that the BO was losing track of the fact that the record was dirty. It was registering as dirty for the first save (IsDirty == true) but on the second save, IsDirty was false. So I think what's happening is that Strataframe isn't attempting to check rules or save. And I don't do any reloading of the record in between. The BO is part of the BasePage so it's getting stored in the Session.



I tried manually setting the record to dirty with BO.CurrentRow.SetModified() but I get an error saying that the row state has to be Unchanged in order to use SetModified or SetAdded. I tried updating a timestamp field on the BO (ex. Customer.Created = DateTime.Now) and the record was still not registering as dirty.



I'm just going to validate the required fields manually and move on, I've spent too much time on this already.



So I know there's something I'm doing wrong because it works in a simple implementation. But I wanted to get it out there and see if anyone else has had a similar experience and if they found a reason and a solution.



Thanks

Govinda

I will probably just remove that rollback command

Looks like I spoke too soon. I can't just remove the command to Rollback the transaction because the second time the submit button is clicked the transaction is still active and calling the BeginTransaction command causes the following exception "A transaction with the key [DEF_TRANS_KEY] is already started".



So I tried calling Commit instead and that seems too work.



I don't think this is the greatest behavior when dealing with transactions, because I should be able to call the RollbackTransaction method where I was calling it. Are the developers looking into this? If so, do you need anything else from me?

Trent,



Do you think my solution is appropriate or is this something that needs to be fixed in Strataframe?



Thank You,

Govinda

I am sorry I have not yet responded to this post.  I have not had a chance to look at it.   Everything came flying at me all at the same time.  We have been dealing with some server issues as well as some strange forum posts lately which has slowed down the "pipe."  We still have this on the stack to look at.  Sorry for the wait.

Thanks for the update.



While I'm here, I'll add that when running the sample probject, you'll see the behavior by filling only one of the fields and hitting submit twice, the first time you should see AbortedWithBrokenRules and the second time Success.



Thanks again

Hi,

Any update?



Thank you