[Tony]

Hey folks,

In finally getting into figuring out what people need from their dashboards in the organization I'm currently working in, I've found a great need for historical data analysis. While it was brought to my attention that adding date criteria to the SQL query in the request might provide information from a specified period of time, there has got to be an easier way to view information from a certain time period only.

An example would be a simple chart listing file transfers and their attributes. One of these attributes is date. With a basic dashboard built based on information from training or the 2 examples provided, you can sort by date, but we can't even scroll down. Ideally, we'd like to be able to get just a certain date, or time period. Has anybody accomplished this? Does anybody have an idea how we would accomplish this?

Obviously Sentinel and Composer are not the most intuitive tools in the world, but they're not rocket science either, which makes it frustrating to not be able to figure out!

Thanks in advance,

Tony

[GuitarCrazyo]

Best way to get defined is by doing lots of cardio..I also found out from past experiences that doing dips,pull ups & chin ups really help makes you cut..

[Stench]

i understand the problem to be "a table element cannot be scrolled"

hmmm(?), i guess i never noticed that because i have always limited the number of records a user receives back so that it actually fits on the dashboard. For data which needs to be scrolled, i would provide a "Monitoring" request.

i suggest, "use dashboard variables" ...
... to allow the user to limit the retrieved records to a number that will fit on the dashboard element.
You mentioned just date, --
try adding more criteria like sender id, receiver id, message type
or whatever other fields your records have to provide more uniqueness in the retrieved data.
Make the data (num records) fit the dashboard element (table element) or use a Monitoring request.