InfoPath Dev

Hi W, Obviously, there is some rule that is setting a value which is triggering another rule that changes a value and triggers the original rule. And, around and around you go. Check your conditions on your rules. This should be easy to prevent. Attach the form if you can't figure it out. 

Hi CToper11 and thank you for your patience, Unfortunately, there is no automatic way to do this. You can export your list data to an Excel file and use our XLS2XML tool to auto-populate a new form in a form library, but that assumes you have the template for the new form. To create the new form, you can copy the view over by just ctrl-a and ...

Hi Bhagvan, I'm sorry but I don't understand your first sentence very well. You can add javascript code to the page to do popups and open forms in Read or Edit mode depending on the results.  

Please right click the text box and choose properties and select the Display tab and check the box that says limit the text box to N where N is the number of characters in your bar code. Then, check the box underneath it to move to the next field. This will let you run a rule to automatically fire the query. You can auto insert another row in ...

Here's an idea... Add two repeating sections to the form that are bound to the same repeating group. In one section, right click and specify don't allow insert or delete. In the other one, leave it with the defaults which are to enable insert and delete. Then, add a conditional formatting rule to each that hides it if the count is >1 ...

Hi RocketGirlOT and thanks for posting. Are you using the rare and rather undocumented File->Merge feature?   If so, are these both the same InfoPath 2013 version or are they earlier? Please attach your XSN form along with the XMLs you are trying to merge and we can take a deeper look. Should be easy to fix the XSLT ...

Hello Brian and thank you for your patience, Unfortunately, the out-of-box InfoPath never supported parameterized SQL querying and that has always been a bit of an issue. We have provided two gap-filling solutions over the years - qRules has a ModifySQL command in it and our DBXL Web service support parameterized querying. Both can ...

How about upgrading the form's to be 2013 compatible? Open in InfoPath 2013 Designer and go to File->Form Information and Compatibility. Set as 2013 and save-republish. Just a guess, but easy and worth a try. :) 

Hello Iaingra741 and thank you for your patience. List forms have maximum widths for some fields. Library forms do not. Library forms can also support repeating data. Both list and library forms do support image and file attachments. List forms can support multi-line text entry. Hope that helps a little.  

Hi Amanda, Thank you for your patience.  I don't think the namespace is the issue here. I think it has to do with a new restriction in calling the Web service from O365. Can you confirm you are using O365?  If not, we'll investigate further. Thanks!