Forms Designer Forum

Getting error below. Contacted Microsoft and they said to contact third party.
Can you help me fix this error. This error has just started occurring when an edit page is opened or saved. Its sporadic.

Error:
unable to display this web part. To troubleshoot the problem, open this web page in a Microsoft sharepoint foundation - compatible HTML editor sas as Microsoft SharePoint designer. ...Correlation ID:...

Microsoft Response:
We have got update from our team, form which is created using third party tool using XSLT code. and XSLT code uses high CPU resources on server, whenever high CPU resources is used by code at that moment forms are getting throttled by sharepoint online, throttling limits can be exceeded for custom XSLT execution if one or both of the following conditions are true:
• The custom XSLT causes a stack overflow.
• The XSLT execution time exceeds one second.
We can see in trace that stack overflow is causing issue. which is causing the issue and hence the issue is intermittent. and below is the article for the same
https://support.office.com/en-us/articl ... n-US&ad=US

Below is the workaround, where we need to change value if form is created using sharepoint designer but as form is created using third party tool, you have to contact form designer support to get below string value updated:

Reduce the size of the code by replacing the existing value of ddwrt:EscapeDelims(string(@ID)) with the new value @ID .
Remove all <SharePoint:FieldDescription> strings.
For an edit form page, break the XSL template for <xsl:template name="dvt_1.rowedit"> into multiple XSL templates by dividing the table rows into multiple XSL templates. You can do this by using SharePoint Designer 2013 to edit and add the strings.

Hi!

The article describes how to optimize the XSLT execution. I can assure you Forms Designer product has as much XSLT optimization as can possibly be.

Most probably, the problem is that there are too many fields in the form so they can't sometimes render in time (1-sec limit).

Please try the following solutions:

1) Set some fields to Readonly (in Designer specifically, not with JS)

2) Export the form, so you don't lose any progress, and try to delete more complex fields from it - Lookups, People Picker, Taxonomy, etc. Some of them could be broken, or have some issue with permissions, etc. Fields like Single Line text or Choice should cause no such issue

Anyway, you can also consider about the modern Forms, they don't have restrictions on the number of fields.

thanks for the quick reply...what do you mean by modern forms?

Thanks for the quick reply.
If I use modern forms, will I have to start from scratch and recreate all new forms?
Will I have to purchase Plumsail Forms instead of using Form Designer?

Hi!

1) Yes, the forms cannot be migrated from one product to another due to different architecture and will have to be recreated from scratch.
2) Yes, Plumsail Forms has a separate license.

Appreciate this is an older post, but could the number of related items webparts also have an effect on the form?

I have a form which has less than 40 fields on it, but about 8 related items web parts - could this also cause the form to overload the stack?

Hi!

No, the related items web parts are the separate web parts and can't affect DataFormWebPart which renders the form fields.

Did you encountered this issue?

Good to know that related items are not affecting the form.

I did a field count, there are 6 new fields added recently, but this is well within the 70 limit, and I still can't see why I'm getting the correlation issues. I removed all custom JS from the form, but still seemed to get issues.

Total field count is: 46

choice - 10
slt - 5
mlt - 7
Cross Site Lookup - 5
people picker - 3
boolean - 14
date - 2

related items webparts - 8

custom js - none
jslink - none
view changes to related item webparts - none

Could there be something wrong elsewhere that is causing this? I'm reluctant to start from scratch as there is an underlying architecture to the site based on many content types and site columns. Before I try that, can you recommend checking anything?

Kind regards
Andy

Dear Andy,

It worth ensuring that this is the case by removing some fields, one by one, to see if the certain field can cause time overflow. You can export and save your form before that procedure.

I will keep reducing the forms down to see if I can spot where this might be happening.

I just also noticed that the site collection had publishing features turned on. Could this adversly affect the performance of forms?