Error Displaying Form in Power Portals

[Anonymous]

I was trying out a flow that updates a record upon creation, it went well on model driven however when i tried it on Portals this error message appeared. Is this normal and is there a way to fix it? Thank you in advance!

[justinburch · Accepted solution]

Hi @Anonymous,

You'll need to disable Custom Error Logging in order to see what the actual issue is (Yellow-Screen-of-Death with error logging). A couple of other questions:

1. Does this only occur on submission of a record, or does it occur when you open a record updated from the model driven app?
2. Flow is asynchronous, so are you sure this is because of the flow or could this be something else - like an invalid input (e.g. putting "Justin Burch <admin@justinburch.com>" will throw the same error from any form

I hope this helps,

Justin

[Anonymous]

Hey @justinburch 

So i have a webform with few steps in it, after i submit a step, this error occurs. About the flow I'm not sure but when i deactive the flow there is no error. Can a webform display step that is recently updated?

[v-xida-msft]

Hi @Anonymous ,

Regarding the issue that you mentioned, I agree with @justinburch 's thought almost. Please disable the Custom Errors option in your Portal's Administrator, then you would see the details info about this error.

Have you tried to create a new workflow for your Entity, then bind it into your Web Form Step again, then check if the issue is solved.

In addition, also please make sure that the Web Role assigned to you has sufficient permission to access the Entity resource related to your Web Form.

Regards,

[OliverRodrigues · Accepted solution]

@Anonymous take a look at this video if you need help with disabling the custom error page: https://www.youtube.com/watch?v=F8QxoyOIzAc&

------------

If you like this post, give a Thumbs up. Where it solved your request, Mark it as a Solution to enable other users find it.

[justinburch]

Hi @Anonymous,

I see - it does sound like the flow is causing the issue then, and if your first step is an Insert you won't be able to duplicate it from a model driven app created record.

A few things to consider:

1. Have you disabled the custom error logging to see the stack trace?
2. Can you quickly create a new web form for "Edit" with just that step and see if that opens existing records?
3. Does your flow perform logic - or can you make the post-create update via Entity Form Metadata (Set Value on Save)?