InfoPath Dev

Can you attach your latest form? I don't see that first table in the copy I have... ?

Oh - I must have misunderstand what you wanted to happen - you wanted 3 rows in the second table if there were 3 in the first? I'm afraid IP just doesn't do that... you could add rows by default, use defaults to set the first field to your other table value, and hide blanks, but that is sort of messy.

I think that should work. You plan to have 5 rows in each table? You should be able to use count of preceding-sibling to get the right row for each.

 I like this site a lot: http://zvon.org/comp/r/tut-XPath_1.html As far as using the same formula, the XPaths change based on the field, the location, the desired fields you wish to use - so let me know if you need a hand and which view / field & I can help you with this. :) As to what happened when you tried a repeating ...

I just realized you are publishing to Office 365 - so that takes REST out of the equation. I'll try to publish to my O365 site while running Fiddler to see if I can see why you are getting an error, but you may just not be able to do this leveraging a list. You may just have to use default data after all.

I would add a field for this - set the default to something that would be true for the first instance and false for the others - then you could use that for your workflow condition. Perhaps the default could be: boolean(count(../preceding-sibling::*) = 0)

I don't quite understand what you mean by "a different Vendor Pricing Table per step", but give this a try. Save the linked form locally, right click & select design to open in design mode & then you can preview.

The vendor pricing table should be repeating. You can use defaults to include 5 rows for new forms, and then disable the insert widget, if you only ever want 5 rows. It would be easier then to create a default that would get the correct price based on the qty in the other table. I'll make some mods to your for this so you can see what I mean.

So - is this form in production yet? Or are you still developing it? Because if we normalize the schema a bit for your Vendor Pricing table, this would be a lot simpler....

I usually run Fiddler and then run the design checker to see if I can get any better info on the issue (or check your ULS logs on the server). If that doesn't help, I tear the form down, saving a copy of it, publishing to a test library, and removing one view at a time. Sometimes the issue can be as simple as a bad default value, but IPFS ...