You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Client errors that are reported back and available for review in the Admin Console very consistently (although maybe not always) have a name and message property on the serialized exception itself.
It would be helpful if we (safely) parsed the JSON error payload and extracted those two fields to promote to top-level fields on the grid records. You can add the JSON error to the grid and get some approximation of this, but it would be simpler/cleaner if I could just view/sort/filter the error name itself.
For any client errors that lack either property, we can just leave the field null.
The text was updated successfully, but these errors were encountered:
Client errors that are reported back and available for review in the Admin Console very consistently (although maybe not always) have a
name
andmessage
property on the serialized exception itself.It would be helpful if we (safely) parsed the JSON error payload and extracted those two fields to promote to top-level fields on the grid records. You can add the JSON error to the grid and get some approximation of this, but it would be simpler/cleaner if I could just view/sort/filter the error name itself.
For any client errors that lack either property, we can just leave the field null.
The text was updated successfully, but these errors were encountered: