Answered

Error 'An unknown failure has occurred.' on Entity Form when no matching record associated to Current Portal User

(0) Share

Report

Posted on by AInglis

I have a Read Only Entity Form linked using the Record Source Type - Record Associated to Current Portal User.

The Entity Form displays correctly when there is Data for the Portal Contact in my custom Entity, however when there is no matching record the error "An Unknown failure has occurred. Error ID # [[f5425d2f-9fae-44a0-8910-74b7d293c43d] is displayed.

Is there a way to set this to display a 'No Data for your Login' message. 'The Record Not Found Me...' setting has a message entered

Contact without data on Package Entity

Contact with data on Package Entity

Entity form No Error.JPG

Thanks in advance

Categories:

Power Apps portals

I have the same question (0)

All responses (4)

Answers (1)

Sort by

v-siky-msft Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hi @AInglis ,

Please check this blog, we can show the plug-in error in following portal screens by adding “Site/EnableCustomPluginError” entry in Dynamics CE Portals -> Site Settings.
https://rajeevpentyala.com/2019/03/01/dynamics-portals-display-plug-in-error-messages/
Hope this helps.
Sik

Was this reply helpful? Yes No
AInglis 38 on at

Like (0)

Report
Copy link

Link copied!

Thanks Sik,

Adding this setting has changed the message displayed as below. This is a clearer error, however it would still lead to queries from the end user. Is there a way to display a custom error message or have the message in the 'The Record Not Found Me...' option displayed?

Thanks
Andrew

Was this reply helpful? Yes No
v-siky-msft Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hi @AInglis

Please check the first step from the blog.
You should first create and register a plugin with logic so that you can handle exceptions to show the custom error message. It requires the special skills of a developer. Reference: https://docs.microsoft.com/en-us/powerapps/developer/common-data-service/handle-exceptions
Sik

Was this reply helpful? Yes No
Verified answer

AInglis 38 on at

Like (1)

Report
Copy link

Link copied!

This answer on this post may lead to a solution.

I have not implemented the conditional Web Template as yet, as the production version of my portal should not have an instance where there is no matching record.

https://community.dynamics.com/365/customerservice/f/dynamics-365-for-customer-service-forum/306014/how-do-i-get-a-friendly-error-in-d365-portals-when-entity-form-tries-to-get-a-record-which-doesn-t-exist/884088

Was this reply helpful? Yes No