Is there a way to catch a key conflict error rised by dataverse in order to present a user friendly error to the user instead of the long technical generic message of key conflicts?
I have an entity E on Dataverse with a key constraint composed by 2 fields A,B. Currently when I patch a record in E if dataverse incurs in a key conflict it raises an excelption causing a long technical message to be prompted to the user.
I would like to catch this error in order to prompt a more user friendly message to our user.
With this in mind I wrote the following snippet of code:
Patch(E,myRecord,{A:"myValueA",B:"myValueB"});
If(
IsEmpty(
Errors(
E,
myRecord
),//doStuff
Notify("My User friendly message",Error)
)
how can I handle the exception rised by the Patch formula in order to grab the message and substitute it with a more user friendly message?
Solved! Go to Solution.
I implemented a workaround: for not incurring in the key conflict error I am fatching the record before patching it
UpdateContext(
{
recordAlreadyExists: CountIf(
E,
A=myrecord.A && B=myRecrod.B
) = 0
}
);
then I am patching the update just in case the variable recordAlreadyExists is false.
Let me know if you can find another way to accomplish this
I implemented a workaround: for not incurring in the key conflict error I am fatching the record before patching it
UpdateContext(
{
recordAlreadyExists: CountIf(
E,
A=myrecord.A && B=myRecrod.B
) = 0
}
);
then I am patching the update just in case the variable recordAlreadyExists is false.
Let me know if you can find another way to accomplish this
This training provides practical hands-on experience in creating Power Apps solutions in a full-day of instructor-led App creation workshop.
Come together to explore latest innovations in code and application development—and gain insights from experts from around the world.
User | Count |
---|---|
199 | |
71 | |
48 | |
41 | |
30 |
User | Count |
---|---|
267 | |
121 | |
94 | |
89 | |
82 |