Extractor Pattern with Vars

Yes, you are right in your observation that this variable-referencing syntax is no longer supported, even though it would certainly proove useful to you at a time like this!

An alternative would be to attempt something like the following:

• Match the whole table body into DATARECORD (or some other variable, if you would like. No extractor pattern in the token is needed.)
  ~@DATARECORD@~
  

• Make a script, and set it to run "After each pattern Application" (even though it'll only match one time in the document). The script would have to perform something like the following...
  
  // Code is in interpreted Java.
  // Change "DATARECORD" to the name of the variable that you used in the extractor pattern
  String tableBody = dataRecord.get("DATARECORD");
  String lookFor = "
  String endMark = "

  ";
  String tableRow = "";

  if (tableBody.contains(lookFor)) {
  tableRow = tableBody.substring(tableBody.indexOf(lookFor), tableBody.indexOf(endMark, tableBody.indexOf(lookFor)));
  }

  session.setVariable("ROW_TO_EXAMINE", tableRow);
  

  
  Make sense? Sorry for my everything-in-one-line approach. That assignment to tableRow is "get the substring", while supplying the arguements: "beginning with where the found TR starts" and "get the index of the end mark, beginning the search from where the lookFor variable is found".

Now you've got a session variable called "ROW_TO_EXAMINE" (or whatever you choose to call it) that contains the row that you were after.

If you're not concerned about the row having a possibility of not existing in the table, you could remove the defensive IF statement, and just make the assignment to tableRow.

Does that help to answer your question?