Difference between revisions of "ConnectR Interface Troubleshooting"
(<pre></pre>) |
|||
| Line 4: | Line 4: | ||
[[Image:ConnectR_Debug_Documentation_Img2.jpg]]<br><br> | [[Image:ConnectR_Debug_Documentation_Img2.jpg]]<br><br> | ||
3. Remove beginning and end parens<br> | 3. Remove beginning and end parens<br> | ||
| − | 4. Find | + | 4. Find ' (single quote) -> Replace with '' (two single quotes). Notes that SQL does not process double quotation marks.<br> |
[[Image:ConnectR_Debug_Documentation_Img6.jpg]]<br><br> | [[Image:ConnectR_Debug_Documentation_Img6.jpg]]<br><br> | ||
5. Run sp_idxgenspcall, sp_name, SQLCommand encapsulated in single quotes (ensure results are sent to text for easy copying)<br> | 5. Run sp_idxgenspcall, sp_name, SQLCommand encapsulated in single quotes (ensure results are sent to text for easy copying)<br> | ||
Revision as of 18:55, 18 March 2011
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 ' (single quote) -> Replace with (two single quotes). Notes that SQL does not process double quotation marks.
5. Run sp_idxgenspcall, sp_name, SQLCommand encapsulated in single quotes (ensure results are sent to text for easy copying)
6. Copy text results & paste into new query window
7. 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
