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!
Solved! Go to 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:
I hope this helps,
Justin
@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.
Power Pages Super User | MVP
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:
I hope this helps,
Justin
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?
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,
@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.
Power Pages Super User | MVP
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: