General – Mismatched IR Tags

This topic has 3 replies, 3 voices, and was last updated 11 years, 6 months ago by Jeff Anderson.

Creator

Topic
May 29, 2013 at 3:32 pm #53675
Jon Melin
Participant
Hello,

I was wondering if there was a way to identify where the mismatched IR tags are within an XLATE. I am receiving that error in my watch output but when I go through the XLATE I can’t see any groups or segments that don’t line up (could just be missing it). I’m assuming that is the only causation of mismatched IR tags error is when you don’t have the mapping correct with the variant on IB and OB.

Thank you in advance.
Creator

Topic

Viewing 2 reply threads

Author

Replies
- June 12, 2013 at 7:44 pm #78511
  Mike Grieger
  Participant
  not an elegant solution, but it works: add a new Xlate action (just a @null to @null COPY or whatever), and put an echo statement in the xlt pre proc. Use testing tool. If your echo statement displays prior to the mis-match error, the tag error is farther down, else, it is above your echo.
  
  Think binary sort… put the echo in the middle to find if the problem is in the top half or bottom half, then keep doing that to narrow it down.
- June 12, 2013 at 7:46 pm #78512
  Jon Melin
  Participant
  Good idea. I will give it a shot. Thank you
- June 20, 2013 at 4:43 pm #78513
  Jeff Anderson
  Participant
  The way I was shown is to go into the testing tool, deactivate everything and then slowly reactive several lines at a time until you figure out exactly where the issue is.
  
  Hope this helps!
Author

Replies

Viewing 2 reply threads

The forum ‘Cloverleaf’ is closed to new topics and replies.