Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
RowState is unchanged on consecutive adds for a BO
Message
Information générale
Forum:
ASP.NET
Catégorie:
The Mere Mortals .NET Framework
Divers
Thread ID:
01297505
Message ID:
01298385
Vues:
30
Kevin,

I tried doing what you say below, meaning bypassing the check for unchanged, but the problem still remains since there are two records in the dataset passed to the business rule and only the first record is checked. Since the first record was checked on the first go around this doesn't do any good.

Why are there two records passed on the second time around? Why isn't the dataset getting cleared when I save the first time around? How can I get the dataset to have just the one record that needs to be checked each time I save?


>A few things you can do...you can change the business rule class so it doesn't check for Unchanged. Another thing you can do is manually begin, commit, and roll back a transaction that includes both business objects. Just register one object as a child of other, and check out the MM .NET Dev Guide topic "Working with Transactions" to see how to use transactions manually.
>
>Best Regards,
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform