ConnectR Interface Troubleshooting

Debug Procedure

1. Ensure Error Message Definitions are loaded into ConnectR database. Run ConnectR Error Message script available via Allscripts Interface Team Wiki: http://intwiki/wiki/index.php?title=ConnectR_ErrorMessage (Allscripts VPN access required).
2. Copy command from Target Message Grid into SQL Query window


3. Remove beginning and end parens
4. Find ‘ -> Replace with ‘’
Note that SQL does not process double quotation marks. Find Single Quotation Mark and replace with two Single Quotations Marks.

5. Run sp_idxgenspcall, sp_name (for example, FileApppointment_CMS), with the remaining SQLCommand encapsulated in single quotes (both at the beginning and end). Before you execute this query, make sure the results are set to 'Results to Text'.
6. Copy text results & paste into new query window


7. Add begin tran/rollback tran to query. Execute query and Utilize this information to root cause the error.

Example

In the example shown below, required fields were present in the Stored Procedure called by the mapping, but were not present in the current Interface mapping. Thus the outcome was that the target message had to be changed to include the additional fields.

Hint

Cycle systems after changing a mapping

Notes

If you are encountering SQL formatting, syntax, or other errors when trying to run the script check the following:

1. There should be a comma after the name of the stored procedure. For example, the beginning of the query should read, "sp_idxgenspcall FileAppoinment_CMS,"
2. The text immediately following this comma should be enclosed in a single quotation, and the corresponding single closing quotation should be the last character input as part of the query.
3. Make sure the results of the query in step 5 are sent to text, as this information is needed for step #7.