Populating field in current node - InfoPath Dev
in

InfoPath Dev

Populating field in current node

Last post 01-10-2007 01:48 AM by Patrick Halstead. 1 replies.
Page 1 of 1 (2 items)
Sort Posts: Previous Next
  • 12-22-2006 02:14 PM

    Populating field in current node

    Hi, I've searched high and low and can't seem to figure this out. First let me describe what I'm trying to do. I have a form that is going to be used as a tracking system. The form saves to a document library but also sends some data elements from a repeating table to a customer list. What I need to do is update the custom list records if the user modifies the form. I've already set up the caml template and it will work if I hard code the record ID into the caml template so what I need to do now is identify the record ID in of the repeating table node. I added the custom list as a secondary data source and pulled the ID and a tracking number field that's unique. When the form opens the idea is to have the ID field populated if it exists in the custom list. Here is the xpath that works but it populates all fields with the ID from the first row.


    xdXDocument:GetDOM("IncomingCapture")/dfs:myFields/dfs:dataFields/dfs:IncomingCapture/@ID[../@TRACKNUM = xdXDocument:get-DOM()/my:myFields/my:Waste_Line_Items/my:TRACKNUM]

    I've tried adding current() every which way I could but it still doesn't work. If anyone knows the answer, I would be eternally greatful for the help. Thanks!
    Shaun Nieves
    Sharepoint Manager
  • 01-10-2007 01:48 AM In reply to

    Re: Populating field in current node

    Hi Shaun,

    Sorry for the huge delay over the holidays responding to this. Current() is one of the most difficult functions to figure out. We do this all the time, but it's not easy. Good luck and if you need more assistance feel free to buy some hands-on time from us. We have blocks available in our store.

    Why not just use SQL? SharePoint is not good at tying lists and forms together. You can do it but you get in trouble because transactions aren't atomic and if you have dependencies you can end up with refIDs that point to dead ends.

    Regards!
    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.