Adding ClientSpace Drilldown to Business Intelligence Reports

Functionality can be added to Izenda reports for drilling into ClientSpace records from ad-hoc reports - follow the guidelines below. 

The numbers in curlybraces are the field positions for the parameter you want to pass, so {0} indicates the field you are on, {2} indicates the second column (field) in the Izenda report.  It is important to know that fields (columns)  that are visually grouped in an ad-hoc report are not included when counting columns for use in these parameter curlybraces - so if the first two fields on your report are visually grouped and you wanted to send the parameter in field #4 you would actually use {2} unless the link is on field 4 in which case you would use {0}.

 By using the code samples below and the appropriate data fields you can add robust functionality to ad-hoc reports. 

In order to add linkto drilldown functionality inline on a report the following codes (see list below) should be added on the Fields Tab | Advanced Settings  | Url line.

Step-by-step guide - code samples

Standard formatting is as follows: /next/linkto/{TableCode}/{ID}

next/linkto  - this alerts BI that you are creating a link to another record

{TableCode} is the predetermined "Code" of the dataform or core table that you want to link to. This code is hardcoded into the url you're embedding into your report. 

{ID} is the key of the detail record you want to drill into, and will be dynamically replaced in your url by Izenda, keep in mind that Visual Group fields on reports do not count when figuring out the order.

Dataform TableCode  - You can link to dataform pages with the following format:

• /next/linkto/clientservicecase/{ID}

A new column, called TableCode, has been added to the ProjectTypes table, this has been defaulted to the AttributeTableName with the "gen_" prefix stripped off.

So, in the example above, it will use the TableCode "clientservicecase" to hit the ProjectTypes table, find the associated ProjectTypeID, and build the Url to the dataform edit page with that ProjectTypeID and the provided RecordID.

Core TableCode -- You can also link to "Core" detail page through this mechanism, a pre-defined set of core TableCode-to-detail page url mappings are checked first:

• Organization      usage: /next/linkto/organization/{ID}
• Contact               usage: /next/linkto/contact/{ID}
• Workspace         usage: /next/linkto/workspace/{ID}
• Task                     usage: /next/linkto/task/{ID}
• Activity                usage: /next/linkto/activity/{ID}
• TimeTracker       usage: /next/linkto/timetracker/{ID}
• User                     usage: /next/linkto/user/{ID}

Secondary TableCode - If the specified TableCode is not found in the list of known core/peo TableCodes, it will then hit tblTableMetadata, where there are two new columns: TableCode and DetailUrl. It will use the specified TableCode to lookup the tblTableMetadata row with the matching TableCode, and pull the associated DetailUrl field, it will look for the string {ID}, and replace it with the record id that was passed to the LinkTo page.

So, if you have a row in tblTableMetadata with a TableCode = "Foo", and a DetailUrl = "~/foo/bar/{ID}

Then, embed a link using the LinkTo page like this: /next/linkto/foo/123

An example of this is /next/linkto/workspace/{0} where the Projects Table entry in tblTableMetadata has been updated to allow direct linking to the Workspace Landing Page

Adding custom links to dataform File fields 

If a dataform in your report contains a file upload field you can create a link to download the file using the following format

/next/Files/Download?id={ID}

{ID} is the file upload field in your report (containing the file GUID), and will be dynamically replaced in your url by Izenda, keep in mind that Visual Group fields on reports do not count when figuring out the order.

For more information about configuring advanced functionality in ad hoc reporting, contact your account manager at NetWise technology to schedule a training

Related articles

• Page:
  "Invalid Cast Exception" When Clicking Ad-Hoc Report Link
• Page:
  Ad-Hoc Reporting Workshop