Survey123 Power Automate Error 'GetWebhookPayloadSchema' is too large

RickeyFight · ‎01-09-2025

My fire department wants to have a survey123 checklist for each vehicle for daily, weekly, and monthly check in.
We have 12 vehicle surveys each with a quite a few questions. We are running Enterprise 11.1 and these were made with survey123 connect.

What they now want is a way to get an email if something is missing from a vehicle (example Medication).
I have used power automate in the past and thought this would be perfect. Sadly it is not working. Due to having too many fields. Is there another way to get an email? I also cannot auto make reports either. I need those generated every day. In my research I have found that there might be a way to limit the schema down for just the yes no questions for the output to power automate but I am not sure how to do that. If I scale down the power automate it will not help me in the report because I need all questions.

Basically the survey is a bunch of yes no questions and if the answer is no there is a comments box that appears. Then each section has an option for images.

Here is my error:
The dynamic schema response from API '***' operation 'GetWebhookPayloadSchema' is too large, only schemas with at most '1024' properties are supported.

Any advice would be appreciated.

@IsmaelChivite

abureaux · ‎01-09-2025

Have you tried disabling "include submitted record" yet?

You can also specify this in the Webhook in the Surveys Site:

AndyBills

Hi @abureaux

I have the same problem, with some S123 surveys generating about 100-200 fields. Would you know if signing up for MS Power Automate Premium solve the issue? I can't remove questions in the Forms; each yes/no question is required and needs the ability to provide comments and photos. Also do not know what '1024 properties' actually refers to.
Anyone else have the same issue and has solved it, it would be really appreciated for any input thanks!

abureaux

I had this issue on Power Automate Premium, so no, that will not resolve the issue. The limit isn't tied to account type.

Have you tried the suggestion I have posted above?

Honestly, I am moving away from that specific connector. Web hooks are far to unreliable. I am swapping to a timer and the Arcgis Get Data From a Feature Layer connector (with a filter query). A little more work to set up, but considerably more reliable. This is part of the reason I have been so busy this year.

AndyBills

Hi @abureaux

Thank you for advising Premium does not resolve the issue. I have tried your suggestion thanks, but unfortunately this seems to prevent ObjectID or other fields being listed for the Report action. So I was stumped!

A colleague has apparently come up with a fix this morning. I might post this here if anyone is interested.

Thanks!

DavidSolari · ‎01-09-2025

If @abureaux's idea doesn't work and you have to pare the schema down, you can replace all those yes/no questions with one select_multiple question where each choice is a former yes/no. The downside is everything outside of Survey123 will see a field with a bunch of tiny codes with a comma in between so you'll need to document things in your metadata, use Arcade to extract legible yes/no answers etc. etc. Still, a bad fix is better than no fix at all.

RickeyFight · ‎01-10-2025

I was able to get the survey to generate a report but I cannot seem to get it to save yet. Thank you for your input. It is a start. I need to be able to run yes no query and I am not sure that will work without the submitted record.

AndyBills

Hi @RickeyFight

I am having exactly the same issue. May I ask - how did you solve it?!!
My S123 surveys sound very similar to yours - I have 6x surveys all with yes/no questions. A 'no' response then requires a text input and photos. I cannot remove questions - the client needs them all. Using MS Power Automate, it would appear I have to include the submitted record, in order to be able to specify a specific ID or WHERE clause to generate S123 Reports (which are then intended to be emailed via PA).

RickeyFight

@AndyBillsSadly I have not resolved this.