InfoPath Dev

So, back to me being a pain again - this all depends on what stuff is bound to. I'd anticipate seeing something more like the screenshot I'll attach here. A single repeating section, bound to the Project Status data source. Instead, in your screenshot, there are multiple repeating sections inside of another repeating section. Which makes ...

That worked perfectly......I can't tell you how much I appreciate the help. 

I am having a really bizarre issue with calculated values. In a repeating table, I have a text box control that contains a decimal data type. In the table footer, I've set up a calculated value function to display the sum of this column [i.e., sum(textBox) ]. In the InfoPath preview screen, the form works flawlessly. I can add and remove ...

You can add files under the Options tab - if your file is a picture, it will display in the post. So, you add this as another row in the mapping tool. The XPath needs to be relative to the RepeatTableFields node. Your XPath then would be: ../../my:Franchise ../../my:Client You'll hand enter those in the form field column and then select ...

Thinking out loud now - What if I include a "Kit" Checkbox in my table.  The main item will be checked by default (set on sharepoint).  If someone orders 1 or more of the main item, it will check the kit box (or set it to 1) for the following items with the same gear id?  Then just format on that.  Or visa versa ...

Thank you for the reply.

I can't set up column type as text, because there are a lot of code behind involved on that Sharepoint document library, and i think i will cause bigger problem with that solution. Niether the round and floor functions can't fix the problem. I can't format the number of decimal places, because i don't know how many numbers will be ...

Hi Hilary, THANK YOU SO MUCH!!! You are right - I have checked the 'Relink Document' view and sure enough, the problem forms were pointing to a different XSN.  I did what you suggested and tried a couple first and its works great - Now to relink the rest of them Thanks again Tony

OK, so if GearID = preceding-sibling::PullSheet/GearID hides all the sub items by default.  Now how do I get it to hide those sub items only if the first instance of all of those repeating values has a specified value in another column? 

Okay so we just tried 3 things: -Tested the submit button in Preview mode and it worked fine, no errors. In hindsight this might have been because we had set a new data connection for it, but this new connection had no effect on the submitting form the browser, same error. -The UDC file is indeed approved in All Site Content > Data ...