Is there a way to catch eConnect exceptions before the eConnect call to the GP? Maybe through pre stored procedure?
The problem I am running into is when the end user click the "integrate" button on the UI, eConnect goes through the business logic and checks the source data with GP setups. If the Integration fails it throws an error which is far from what exactly happened. The real error is logged in the event viewwe but the end user cannot see it.
Anyone know the best practice to accomplish this?
Thanks