Why won't workflows edit some of my InfoPath fields? - InfoPath Dev
in

InfoPath Dev

Why won't workflows edit some of my InfoPath fields?

Last post 02-16-2012 01:07 PM by Patrick Halstead. 1 replies.
Page 1 of 1 (2 items)
Sort Posts: Previous Next
  • 02-06-2012 05:07 PM

    • ChrisR
    • Not Ranked
    • Joined on 12-19-2011
    • Posts 4

    Why won't workflows edit some of my InfoPath fields?

    I have made an InfoPath form which I've published to a SharePoint site. The fields in the form will have to be reviewed/changed slightly in the future and so my client would like to know that we have an automated way of translating the info in the current form to whatever the changed form will be. I've decided that workflows should be able to provide me the capability to do this, and I even have an implementation that works on paper, but I can't seem to get past a really annoying bug.

    The step I'm having trouble with is simply copying an item from one document library to another.

    1. In my "source" library, I have my old forms, which include the old set of fields along with newly made fields to match with the new form. They have been autopopulated other fields in the form using workflows and this works fine.

    2. In my "target" library, I have a new version of the library. 90% of the fields are the same, with some gone and some new ones made to replace them. These new fields match with the new fields that I've created in my "source" library.

    3. After I have created the new fields in the "source" items, from what I understand, all I should have to do is simply COPYITEM Action them over to the "target" library. Any fields that match(including the new ones) will be recognized and ported over and the old obsolete ones will be dropped.

    My problem is that when I COPYITEM, some of my fields don't copy over. The strange thing is that if I attempt to copy the other way; from the "target" library to the "source" library, the copy works fine. What's more, is that it seems that i can't even update the those particular fields in my target library. If I simply try an UPDATEITEM action, then I get an error.

    Things I've tried: - I've made sure to "enable editing" when promoting the fields to columns upon publishing. - I've tried creating site columns and then matching my fields in the target library to them as well.

    Neither of these solutions seem to work. Does anybody know what the problem is?

    I would really appreciate the help. Thanks, Chris

    P.S. I'm going to post some screenshots later this evening, but please ask if you would like anymore information and I'll do my best to provide it.

    Filed under: ,
  • 02-16-2012 01:07 PM In reply to

    Re: Why won't workflows edit some of my InfoPath fields?

    Interesting solution to data migration problem. Why not just use Content Types and map the fields to similar site columns? Could save you a lot of time.
    Patrick Halstead
    Project Manager at Qdabra
Page 1 of 1 (2 items)
Copyright © 2003-2019 Qdabra Software. All rights reserved.
View our Terms of Use.