Databases
StackOverflow2013
Postsdbo
POProblem with WF4 Poco persisting
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POProblem with WF4 Poco persisting
    primarykey
    data
    text
    <p>I have a workflow and am persisting it into the database. It all worked fine until I tried using entities in the workflow. Because I'm using POCOs the workflow seems to have trouble serializing the object, especially the relationships.</p> <p>Now the weird thing is, the first time I start the workflow the serialization works and the object is realoaded into the workflow on resuming the bookmark. But this time when persisting the workflow, I get the following exception: "The EntityCollection object could not be serialized. This type of object cannot be serialized when the RelationshipManager belongs to an entity object that does not implement IEntityWithRelationships."</p> <p>I saw that this might help, but I don't have a service and haven't figured out how to get it working without one. <a href="http://msdn.microsoft.com/en-us/library/ee705457.aspx" rel="nofollow">http://msdn.microsoft.com/en-us/library/ee705457.aspx</a></p> <p>Does anyone have suggestions? Or do you think switching to use services would solve my problem?</p> <p>Thanks</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USNischo
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POProblem with WF4 Poco persisting
      1. This table or related slice is empty.
      1. VTUpMod
    1. COWhat are these objects? Often WF uses objects which are actually domain objects, not objects that "belong" to the WF. I always want my domain objects available, and not persisted and or duplicated in a WF. So all my object persistence is by conventional ORM. The WF only keeps Ids. When the WF activates it retrieves any objects it needs, then releases them all when done. WF should not persist Domain objects anyway , only persist its's owned objects i.e ones that only have scope in the WF. If your POCOs actually belong to the WF, not sure what is best, I've never needed that myself.
      singulars
      1. POProblem with WF4 Poco persisting
      1. USSisyphus
    2. CO@Sisyphus Thanks, I decided to to it this way and only save the IDs. I need the values of a user in the workflow. Is there any way I can load the user only once and using it in all activities, without it being persisted?
      singulars
      1. POProblem with WF4 Poco persisting
      1. USNischo
    3. COYou can add a member and mark it NonSerialized. That way it is available for all activities to use. When and where and how you choose to instantiate any members that are not persisted will depend on your specifics. The only rule is the obvious one - you are responsible for explicitly instantiating any members that were not persisted before they are accessed. If you use member variables instead instantiating objects at the point of use make sure you are aware of all the points where your workflows can idle then rehydrate, don't overlook any delays etc.
      singulars
      1. POProblem with WF4 Poco persisting
      1. USSisyphus
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload