General

Re: Recursive Section renders InfoPath Form useless.

hooked82 — Tue, 19 Jan 2010 17:11:57 GMT

Qazi Anis:

what exactly do you want to do from your form. if it is changing data connections, you can just do the same from manifest.xsf. save your template as source and make the changes to its manifest.xsf. that should be pretty fast for you. but take care that you have a backupof template

Sorry, I should have explained how I am using my form. I use InfoPath that has an XML Schema file as it's main data source for creating XML files when the user saves the form. The resulting XML will then be used to transform via XSLT and render web pages. This is the reason for the recursive sections. For example, my base body group has elements such as paragraph, list, table, etc. This means you can insert a paragraph into a table into a table into a table, and so on.

The problem is that this makes the form very sluggish. Especially when I get a change request for additional options, and I have to update the XML Schema, Conver the Main Data Source in InfoPath, then the form pretty much needs to be started over at this point.

Thanks

Re: Recursive Section renders InfoPath Form useless.

Qazi Anis — Tue, 19 Jan 2010 09:05:28 GMT

what exactly do you want to do from your form. if it is changing data connections, you can just do the same from manifest.xsf. save your template as source and make the changes to its manifest.xsf. that should be pretty fast for you. but take care that you have a backupof template

Recursive Section renders InfoPath Form useless.

hooked82 — Tue, 19 Jan 2010 06:48:35 GMT

I've got a major problem on my hands, and I figured that I would turn to everybody here in hopes of some help, or maybe even some direction on how to solve my problem. Before I get into the problem, just want to say that I've been working with InfoPath for a while now, but have never came across this issue before. Just a forewarning, I'm a lot better vocalizing the problem, than trying to explain it in text, lol.

I have a repeating choice group named "body" that has multiple child elements such as list, paragraph, table, image, link, etc. etc. Some of the child elements can contain the same type of elements that body has, so these elements have a child element referencing "body", thus creating the recursive section. Everything works great, though the form slows down a little bit from normal, I'm assuming because the form recursion has no end, though it's still pretty usable.

My problem is when I need to update my Main Data Source, I update my .xsd, select Tools > Convert Main Data Source, and about 5-10 minutes later, the form responds. Once the main data source is converted, clicking through elements in the Data Source tasks pane is unbearably slow! The form at this point is pretty much junk! I've deleted, recreated, reedited the form about 15 times doing different things to maybe correct the problem, but I just can't get the form to be usable with this layout. I can't scrap this, as the customer needs the recursion in the form.

Can anybody think of some things that will help me resolve my problem? Can I possibly limit how many levels deep my recursive section can go and then it hits the last level of recursion or something like that? If there's any other info that I can provide to help you better understand my problem, let me know, I am at your mercy!