BUG REPORT: Inconsistency with error messages

[Sienna]

I have tried to add same value into a SQL unique column and display the error in the label with

First(Errors('dbo name')).Message

I get an error message on my pc 

The request operation is invalid

and on my iphone

Unknown error

Can anyone please take a look at it and fixed it.

BTW there is also automatically generated error message in published app on iphone at the top of the screen which says exactly the same thing. Any chance to disable that message?

[Meneghino]

This is just a comment.  In your app you should check for duplicate values before the Patch operation so that you can manage the error before it occurs.

[Sienna]

@Meneghino

You can't do that in 2 scenarios.

1/ When 2 users will try add same value into a unique column at the same time

2/ When the value which is added into the unique column is  already in more then 2000th row which is the limit for sql tables as far as i know

[Sienna]

@Meneghino

I appologise for the second point. I've just tested it and it looks like we can look for a duplicates even in above 2000 row limit. But still first point remains imposible to check for duplicates. I'm just thinking... When we are not able to check 100% for duplicates,  do we really have to check for duplicates when we can only trigger error message? It would lighten up the code and even performance of the app. But we need reliable error message... Please any answers here

[Sienna · Accepted solution]

Just got my PA updated on my phone and it looks like the error messages are fixed now. 

Any chance to get rid of the system message marked on the picture? User of the app doesn't need to know the details and therefore it is not very user-friendly for him anyway. The message should be displayed in studio rather then in publised app

[Sienna]

Also it would be very useful to pull the value which is duplicated.

The Error.Column return blank which according to 

• Column. The column that caused the error, if the error can be attributed to a single column. If not, this will be blank.

should be only single column in unique column so it should have a value

[Meneghino]

I fully agree with @Sienna that the Errors function is not really up to standard.

It should be improved.