InfoPath Dev

I work in IT for a medical company and want to develop a simple inventory control system using our Office365 infrastructure which is (Enterprise) SharePoint 2013 and InfoPath 2013. I'm following your tutorial on "Add SharePoint List Items with InfoPath" to try to accomplish this using a custom list. The problem is that the UI has changed a lot in 2013 so I cannot follow some of your instructions as controls in InfoPath have been moved around. I have the custom list created, have it's GUID, have created the appropriate CAML template to receive the desired fields and have a default form view created. I get lost (due to the UI changes) once I begin to setup the data connections shown in figure 2 ... adding the 'refresh' and 'listname' textbox to my form. I do not see the controls needed to finish this connection or add a repeating table in the manner that you describe. Again, much has changed in InfoPath's user interface. I write tutorials myself and know it is time consuming. But, would you kindly consider updating your tutorial for those using Office 2013? We are about to launch an EMR system that was written with the help of a 3rd party dev team which is proving to be costly. I know I can create this simple inventory control system using the tools we have in Office365. If I could attach a snapshot of my default form view I think you'd like the approach I'm taking. Or, any updates to your tutorial to help those using the new UI features in InfoPath 2013 would be greatly appreciated. Below is my CAML template and a short list of fields I'm using in my form. Fields: ProductCode, Description, Manufacturer, QtyInStock, QtyToAlert, QtyOrdered, Location. CAML:

 Hi - are you referring to this blog post? http://www.infopathdev.com/blogs/matt/archive/2006/02/02/Add-SharePoint-List-Items-with-InfoPath.aspx

You can attach a file under the Options tab -  I'm guessing I've found the wrong blog post, because I'm having trouble understanding where you are stuck - and yah, that post is from 2006, so pretty old.

That's the one but I think I've found a work-around. Thanks