19.03.2024
21:31
Hi,
I'm sorry, if this a duplicate, but I'm not sure if I added it already or maybe someone else.
If selecting a value of a choose field from a data source throws and this causes an error, it's not easily possible to see the actual "request" which was used to get the data.
There are ways around this:
- In case of SQL and you have access to the server you could activate the SQL profiler
- In case of rest/soap requests you could add an http interceptor which can be used as a proxy.
If you don't have access to the server or the request uses OAuth authentication you are out of luck.
Therefore it would make our live easier, if the would see the final request which is send to the server in the saved diagnostic session. This would be similar to the "Invoke rest web service" action log displayed in admin mode.
Now I'm going back to see what the problem is in my case.
Best regards,
Daniel
