Best widget to use to display a list of records from multiple tables

[david_myers]

Use Case details:     I want to present a list of a user's active tickets on the Service Portal.     These 'tickets' are records in tables extended from the task table, but also will include records from a few custom applications that were not extended from task.   I plan to include display a few columns common to all these tables in the list view, and display 10 records at a time.   If there are more than 10 records I want the ability to click the next set of 10 records.  

What widget would you suggest is best to use for this?   I have been looking at the data table by instance definition, since this meets most requirements, but it will only allow for one table.  

I understand I will need to modify or create a widget to do what I want it to do, but I was hoping for some suggestions or advice to get me started.   Has anyone built something similar?

[Matt Saxton - G]

Hi David,

You need to create a Database View and then do a join to bring that data together. I still don't think that is going to work. You'll need to create a custom widget for what exactly you are looking for if the DB View didn't work.

-Matt

[davidself3]

What I've done is create a new page, then on that page add however many "Data Table from Instance Definition" widgets needed. Each of those widgets can be edited. I had to add several fields to the form that weren't there in the default view to get it to work.

Here's a pic of what the form should look like when you've added the fields you'll need to configure the widget properly. *select open in platform from the hamburger:

From there, you'll probably see a different form because you need to add several fields.

Once you've decided on the table, filter, fields and order. Save it, and load the page:

As far as I know right now, this is the best way to show several lists of records in a page. You can add these widgets anywhere you want in the portal, just have to configure them.

Always keep in mind that these are running queries server side. So if you hit tables with millions of rows, you'll see the performance hit..