Skip to main content
Insert Banner Message here.



Welcome to Community

Formatted Output Template Child Records



1 comment

  • Official comment
    Chris Boschen

    Hello Roy,

    Thanks for reaching out - this is achievable! You need to add VQL into the element definition (Tablerow) where you're returning the set of data you wish to pare down. For example, assume a table called myTable and a tablerow within it which is returning audit information. If you wanted to specify which Findings related to this Audit as related to the audit through my_audit__c field should be shown as rows of the table, you'd edit the XML of the form's tablerow element such that it looks like this:

    <subform_layout="table" name="mytable">
         <subform_layout="row" name="VLT__my_audit__cr" vql="{{query}}">

    {{query}} may be a WHERE, FIND or ORDER BY clause (or any combination of the three, provided the ordering rules of VQL are followed). SELECT, LIMIT, OFFSET etc are not supported. For ease of testing, keep in mind that your formatted output is, in a way, simulating a VQL call - the one above is akin to

    SELECT {fields} FROM finding__v WHERE my_audit__c = '{FormattedOutputStartingAuditRecordID}'

    With your form definition you're just appending additional WHERE, FIND or ORDER BY information to that query. As such your VQL subquery can be performed via a tool like Postman directly on our API to return results akin to what you're looking for before updating your form's template file. 

    If you are trying to leverage VQL's '<' or '>' operators, you will need to use &lt; and &gt; respectively in your template file's xml.

    For the most up-to-date reference documentation, VQL definitions and documentation for use with our API are available at

    For Formatted Output configurations like you're looking in to, I strongly encourage you to engage with Managed Services for diving any deeper than we've discussed here.



Please sign in to leave a comment.

Powered by Zendesk