I'm currently working on a form that has 765 fields/headings/attachments. And Composer keeps crashing on me. It also takes a long time to apply changes to the xml and save the form.
Any tips on how to avoid these issues when working with large forms?
I tried turning off the wireframe when I load the form and locking the wireframe when I'm editing, but it doesn't seem to make much of a difference.
Can you give us a pointer to the form so we can have a closer look.
In answer to your question, one way to deal with very large forms is to break them up into smaller pieces known as parts. You can find documentation here: Composer Form Parts
Below is the form info. I'm still working on this form, so you'll have to take a copy if you want to look at it.
We have regular Composer crashes, using both Firefox and Chrome. But it happens more frequently when it's a very large form (this is our largest to date though) or when we do lots of visibility/validation script editing. I can ask my team mates to add more info, but we are a tad under the pump today.
-- Form Details --Account: Canberra ConnectOrganization: Access CanberraProject: ACTPLAForm: Construction Licence ApplicationTemplate Name: Template-CanberraConnect-- Build Details --Version: 4.3.2Build Date: 3 June 2016Build Number: 47396Build Type: cloud-- Search Path Details --Release Path: Release v4.3.0Service Pack path: v4.3 Service Pack 2Custom Path: Avoka Bizpacks__BizPack AU Support,Avoka Bizpacks__BizPack Universal Support,Canberra Connect__Canberra Connect Pack 41,Canberra Connect__Canberra Connect Google Maps Pack,Avoka Datapacks__Maguire Support-- Browser Details --Firefox/46.0https://transact.composer.avoka.com.au/composer/secure/composer.htm
Thanks Howard. That would have been useful for this form. Unfortunately, it has to go live at midnight today, but we will definitely explore this solution in the future. None of us had ever heard of it.