Custom developed solution called Timer2013.wsp. This solution has been globally deployed and activated as site feature. This Timer Job is supposed to copy data (items) between 2 lists. Expected behavior is farm solution
Timer2013.wsp with its Timer Job as a feature will be successfully deployed on production farm and copy list items between lists. This solution worked fine on version 2010 after SharePoint ungraded to 2013 this solution fails.
(Visited 76 times, 1 visits today)
We have the code as it's in house development but i am sys admin and can not perform any change
on code side. But if i have any good suggestion i will send them to our dev to test. Till now we know
where it fails - when we start with creating SPWorkflowAssociationCollection object to which is added
the list of all Workflow Associations of the current list (l). For some reason, that property is not returninganything back, that is the rest is just being skipped. This is most likely caused by workflow not
associated with any content type.
(Visited 1 times, 1 visits today)
