I'm trying to load an Entity from a stored procedure where the procedure doesn't return a real entity (in this case, it returns a generated key value).   I've gone so far as to define an actual database table so I can create an entity type from it (rather than creating the 'fake' table in the edmx) that has an integer key field along with the other fields that match the select statement from the proc.

 

The proc doesn't use a RETURN value (since that doesn't seem to work with EF/DevForce) and it just returns local variables in a select statement (just to test this concept out).

 

The entity is defined exactly the same as the select statement (same column names; same datatypes).  I've added the function import in the edmx and it's set to return an entity of the type.  I've even tried inserting the row into the db table from the procedure and then just retrieving from it.

 

The problem is that with an Async query, the procedure executes but the entity doesn't get loaded with the data.

 

Since Silverlight needs to run this ASYNC, I build the query using the StoredProcQuery and then I use ExecuteQueryAsync to run it (I have an event handler for the callback with the right event args):

 

    StoredProcQuery query = EntityManager.GetNewKeyQuery('Test', 1);

    EntityManager.ExecuteQueryAsync (query, callback, null);

 

If the procedure just does a SELECT on local variables (or I suppose mixes them with actual columns from actual tables) then EF (I think this is an EF thing and not a DevForce issue) doesn't seem to think the datatype matches the entity type. 

 

   DECLARE @myNewKey BIGINT

   SET @myNewKey = 1

If I wrap a convert around the variable in the select, then EF populates the entity correctly:

 

   SELECT CONVERT (BIGINT, @myNewKey)

 

I mentioned in my original post that I tried replacing the local variable select with a select against a physical table but it didn't work.  However,  I was inserting a row into that table in the procedure and I had already inserted a test row with the same value (that I forgot to delete) so I thought it didn't work but that was because when I ran it again, there was already a row with that value in the table and after looking at the DebugLog.xml I saw that error.  Clearing the table and then re-running worked. 

 

So the issue is resolved.