mapping file help - InfoPath Dev
in

InfoPath Dev

mapping file help

Last post 09-15-2011 03:00 PM by jasonwhitestl. 2 replies.
Page 1 of 1 (3 items)
Sort Posts: Previous Next
  • 09-12-2011 09:33 AM

    I have a list with a group of fields, and then a repeating table with a group of fields. My thought was to create two mapping files, and then combine everything into one file. I don't get any errors when submitting the form, but only the values from my repeating table gets populated into the SharePoint list. I am using SharePoint 2010, and qRules SubmitToSharePointList command. Thanks, Jason
  • 09-12-2011 10:26 AM In reply to

    Hi,

    You're denoting this as a repeating group for the mapping, with the base node being my:myFields/my:TaskItems/my:group2. I believe the problem is that, within that mapping, you are using an absolute path, which is not going to work.

    So if the xpath to the repeating group is my:myFields/my:TaskItems/my:group2, and you add a mapping for my:myFields/my:CorpEvents/my:Title the command ends up looking for my:myFields/my:TaskItems/my:group2/my:myFields/my:CorpEvents/my:Title, which of course does not exist.

    Instead of using the absolute path, use a relative path. i.e. instead of my:myFields/my:CorpEvents/my:Department use ../../my:CorpEvents/my:Department.

    That way, the form goes to look for that xpath, it'll result to:

     my:myFields/my:TaskItems/my:group2/../../ (which brings us back to the root, my:myFields) and then my:CorpEvents/my:Department.

    I believe you'll have to enter those paths manually because the form won't let you select a node outside of the repeating group.

    Does that make sense? Please try it out and let us know how it goes. Thanks!

    Ernesto Machado
    Qdabra® Software/ InfoPathDev.com
    The InfoPath Experts – Streamline data gathering to turn process into knowledge.™


  • 09-15-2011 03:00 PM In reply to

    Hi Ernesto,

        changing the xpath solved my problem

     

    Thanks,

    jason

Page 1 of 1 (3 items)
Copyright © 2003-2019 Qdabra Software. All rights reserved.
View our Terms of Use.