Save Conflict on Workflow Change

[jakobm]

Hi,

i am currently testing the Forms Designer for Displaying Information of one Parent and two child Lists in one form. Everything works great, I just have the same issue as described in another thread that when an item in the child list is created, a workflow performs a status change of the parent list item which leads to a save conflict when saving the EditForm. Do you have any idea on how to resolve this while maintaining status change of the parent item upon child item creation?

Thank you!

[Dmitry Kozlov]

Hi,

Yes, it's a known issue that is reproduced with default forms too. You should re-design your solution, say, create a separate list ParentStatuses with the Status field and create a separate item for each item from the parent list. Then create a lookup field in the parent list and link it to the ParentStatuses (one-to-one). The Status field can be added to the parent list as an additional column. Please, note that you need to create an item in the ParentStatuses list every time an item is added to the parent list. Does it make sense?

[jakobm]

Thank you, this is what I also was thinking of, I will go on and reengineer the process then. Another Requirement I have are cascading Lookup - DropDowns - is that only possible with Cross Site LookUp? Or is there another solution for this when Lookup is only within one site.

Regards,

Jakob

[Dmitry Kozlov]

Hi Jakob,

You can try to implement cascading drop-downs with the help of SPServices:

http://spservices.codeplex.com/wikipage ... eDropdowns