Print Page | Close Window

Error Saving Object Tree with multiple objects

Printed From: IdeaBlade
Category: DevForce
Forum Name: DevForce 2009
Forum Discription: For .NET 3.5
URL: http://www.ideablade.com/forum/forum_posts.asp?TID=1414
Printed Date: 19-Apr-2025 at 7:53am


Topic: Error Saving Object Tree with multiple objects
Posted By: fuekor
Subject: Error Saving Object Tree with multiple objects
Date Posted: 05-Aug-2009 at 6:53am
Hello,
 
maybe someone can help me with a problem, that seems to be new since official release of sl3 and/or devForce.
The Problem:
There is a part generating invoices in a batch. I save objects in two different entities and after one invoice is done with 1 – x positions I use the saveChangesAsyncto persist the changes.

This has worked fine. Now (I believe after changing to devforce and sl rtw) I always get the following error;

------ 

+                      args.Error         {IdeaBlade.EntityModel.EntityManagerSaveException: Als Typ des Schlüsselfelds 'ID' wird 'System.Guid' erwartet, der bereitgestellte Wert weist jedoch tatsächlich den Typ 'System.DateTime' auf. ---> IdeaBlade.EntityModel.EntityServerException: Als Typ des Schlüsselfelds 'ID' wird 'System.Guid' erwartet, der bereitgestellte Wert weist jedoch tatsächlich den Typ 'System.DateTime' auf.

   --- Ende der internen Ausnahmestapelüberwachung ---

   bei IdeaBlade.EntityModel.EntityManager.HandleEntityServerException(Exception pException, Boolean pTryToHandle, PersistenceOperation pOperation)

   bei IdeaBlade.EntityModel.EntityManager.HandleSaveResultException(SaveWorkState saveWorkState, SaveOptions saveOptions, Boolean isAsyncOp)}        System.Exception {IdeaBlade.EntityModel.EntityManagerSaveException}

 ------

There is absolutely no error in the object. All guid fields are filled with guids, all mandatory fileds are populated.

Is there anybody who has an idea about it?
 
Thanks in advance
 
Ralph


Replies:
Posted By: kimj
Date Posted: 06-Aug-2009 at 2:21pm
My first thought would be to check for discrepancies between the client and web versions of the Domain Model, especially if you're using a separate model assembly.  By discrepancy I mean that one assembly is possibly out of date.  You might also want to check that you've re-generated the Domain Model after you made the upgrade, just to ensure that the auto-generated code is current.  If the Domain Model looks good, next thing to look at would be the Entity Model, and whether it's stayed in sync with the Domain Model.   Lastly, I'd try a full clean and re-build of your solution within Visual Studio.  


Print Page | Close Window