InfoPath Dev

I have it for my benefit... basically for testing so I can see if everything is moving and changing as it should.  

Right, feasibly you wouldn't have that many. I only ran into it because I was running a query on a secondary datasource (SharePoint list) where I needed to bring all my list fields in (in a section hidden to the user), in order to use the CopyTable qrule for something I needed to perform. I was able to get rid of a couple ...

I've run into something in InfoPath 2010 (web browser form)... When you insert a custom table in the form, you can only have a maximum of 63 columns. Does anyone know if this is a InfoPath (2010) limitation, html table (etc), browser thing, etc.? I've searched online, but can't find ...

 No we are good. Thanks! I don't know why but I thought it would write the delete directly to the list for some reason (I wasn't thinking about when I do write to the list, it's via a map). I just didn't think the process through :).  I just tried it and it worked great (and very fast). Thanks!

 Hi Hilary!  So, will this write back to SharePoint and actually delete the data (I always assumed it would, so never tried this, sorry that may be stupid thinking :) )? I don't want to do that, I just want to delete what's cached in the form.  Gwen 

In an InfoPath form, is there an easy way to clear the data that was previously queried from a secondary data source (i.e. SharePoint list)?  Basically what I've been doing is re-querying that same datasource by setting a query field to a value that wouldn't ever match any records (so no data is returned). For a big ...

Thanks, Hilary.  I haven't used one before. I'll dig around and see what I can find. 

I have an InfoPath 2010 browser form (with qRules). I'm querying a secondary data source using a data connection. I have multiple fields where I am setting the query values of the secondary data source fields to values captured on the form (Action rule - Set a Fields Value). This works fine. However the user now wants to ...

In case anyone is trying something similar... I added a rule on my button  (to fire before the rules that are the main purpose of the button) where it queries the main dataset for the main records to pull in the data that I need. I then pass those values into InfoPath fields (set default values) in order to hold the values until the ...

There is a button with a SubmitToSharePointList command and a map for the sub fields.