Is table metadata designed more for custom modules that would only require one URL parameter. I ask because:

1. Create a list
- person_id PK
- name
- age
2. Create a page to display the data
- name: person
- source:

<script type="text/javascript">

Ext.onReady(function(){
  console.log(LABKEY.ActionURL.getParameter('person_id'));
});


</script>

(just for testing purposes)

3. Go to schema browser: lists: Person.
4. Edit MetaData
5. Edit Source
6. XML Metadata tab
7. Specify (just to verify it works)
<ns:tables xmlns:ns="http://labkey.org/data/xml">
  <ns:table tableName="Person" tableDbType="NOT_IN_DB">
    <ns:updateUrl>/wiki/page.view?name=person</ns:updateUrl>
  </ns:table>
</ns:tables>
8. Save and go to Data Tab. Verify Edit link. Yep works.
9. XML Metadata tab
10. Specify (add pk field)
<ns:tables xmlns:ns="http://labkey.org/data/xml">
  <ns:table tableName="Person" tableDbType="NOT_IN_DB">
    <ns:updateUrl>/wiki/page.view?name=person&person_id=${person_id}</ns:updateUrl>
  </ns:table>
</ns:tables>
11. Save and go to Data Tab. At this point, no data is returned due to an error:

error: Unexpected character encountered (lex state 3): 'p' (line 3, column 47)
Metadata XML error: Unexpected character encountered (lex state 3): 'p' (line 3, column 47)

So it obviously doesn't like having 2 parameters.