none
SP List Item ID error RRS feed

  • Question

  • Env: VS 2012, SP2013, Win2012, WFM 1.0, SB 1.0, SB CU 1, WFM CU 1, SP Tools for VS, VS Update for Office tools

    I have two solutions, one which deploys lists as features as a dependency feature to my list workflow feature, one which deploys List workflows as a feature with lists pre-existing on the SP site.

    The second when deployed works fine (both are simple Sequence workflows with LookupSPListItemId, LookupSPList, LookupSPListItem, SingleTask, WritetoHistory objects - the lookups are to a secondary list to retrieve data for use in the SingleTask).

    The first produces a Suspended state on the workflow with the following error once it hits the LookupSPListItemId:

    System.FormatException: Expected hex 0x in '{0}'. at System.Guid.GuidResult.SetFailure(ParseFailureKind failure, String failureMessageID, Object failureMessageFormatArgument) at System.Guid.TryParseGuidWithHexPrefix(String guidString, GuidResult& result) at System.Guid.TryParseGuid(String g, GuidStyles flags, GuidResult& result) at System.Guid.Parse(String input) at System.Activities.CodeActivity
    InternalExecute(ActivityInstance instance, ActivityExecutor executor, BookmarkManager bookmarkManager) at System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor executor, BookmarkManager bookmarkManager, Location resultLocation) 

    I tried making the listinstance feature (where the lists are activated on the sp site) a dependency in the feature for the workflow feature, tried recycling the site, the app pools (all involved) and rebooting the server after a deployment, all to no avail. The first solution simply fails.

    Any ideas?

    Wednesday, April 24, 2013 2:29 PM

Answers

  • So after trial and error, it turns out that for dynamically deployed lists the GUID is not retrieved properly by the WFM XAML when selecting the name from the list of available 'ListId' options in the VS UI input section.

    Fix/HACK involves selecting one of the lists, clicking the elipse (...) and in the resulting edit box replace:
    System.Guid.Parse("{$ListId:Lists/Tasks;}")
    With the list GUID:
    System.Guid.Parse("{4CGG7172-6EB0-4414-82E6-92BBE8A5E64A}")
    This means the list cannot be deployed dynamically as the GUID changes (so conflict resolution on the list = none). Would like to find a better solution for this.
    Thursday, April 25, 2013 8:36 PM

All replies

  • So after trial and error, it turns out that for dynamically deployed lists the GUID is not retrieved properly by the WFM XAML when selecting the name from the list of available 'ListId' options in the VS UI input section.

    Fix/HACK involves selecting one of the lists, clicking the elipse (...) and in the resulting edit box replace:
    System.Guid.Parse("{$ListId:Lists/Tasks;}")
    With the list GUID:
    System.Guid.Parse("{4CGG7172-6EB0-4414-82E6-92BBE8A5E64A}")
    This means the list cannot be deployed dynamically as the GUID changes (so conflict resolution on the list = none). Would like to find a better solution for this.
    Thursday, April 25, 2013 8:36 PM
  • Hello!

    Please, check out the solution of this issue in my blog

    http://sp2013workflows.blogspot.ru/2013/07/lookup-activities-in-visual-studio-2012.html

    It's solving deploying problem.

    Sunday, July 28, 2013 7:14 PM