> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/public-finance/v2.3/exemplar/mgramseva/features/tabular-dashboard-collection.md).

# Tabular Dashboard - Collection

Clicking on the Dashboard on the home screen navigates the user to the revenue dashboard view for the current month. This provides a tabular view with the list of consumer records.

Following are the data points/actions needed on the screen

|     |                         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
| --- | ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| 1   | Search Consumer records | <ul><li>Search by name or connection ID</li><li>Name should be a partial match. As the user starts typing a consumer name, respective consumers get filtered in the table displayed below</li><li>Connection ID should be a partial match. This is the new connection ID. As the user starts typing a New connection ID, respective consumers get filtered in the table displayed below</li></ul>                                                                               |
| 1.1 | Filters                 | <ul><li>Default is “All” View. Switching to Residential or commercial filters table accordingly. Alongside the filter, how many consumers fall into that filter is shown in numbers</li><li>The table also has sort options for each column (ascending, descending)</li></ul>                                                                                                                                                                                                   |
| 1.2 | Columns                 | <ul><li><p>Connection ID</p><ul><li>New Connection ID of the consumer- this should be clickable, and take users to the HH details page</li><li>A metered connection should have “M” in a ⭕️ that is followed across as standard for metered connection</li></ul></li><li><p>Name</p><ul><li>name of the consumer. Show until 20 Characters and truncate by showing 3 dots if the name is longer</li></ul></li><li>Collections - Amount paid by the user in that month</li></ul> |

![](https://2287351256-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-Mfb8ehcimjt6ER7QOME%2F-MjDU6YPRZRpTobJGOJv%2F-MjDUIrFxJxoaFLsS254%2Fimage-20210802-100536.png?alt=media\&token=6dc4f08a-6715-4ea0-b8d5-6e724ac6b25d)

> [![Creative Commons License](https://i.creativecommons.org/l/by/4.0/80x15.png)*​*](http://creativecommons.org/licenses/by/4.0/)*All content on this page by* [*eGov Foundation*](https://egov.org.in/) *is licensed under a* [*Creative Commons Attribution 4.0 International License*](http://creativecommons.org/licenses/by/4.0/)*.*


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.digit.org/public-finance/v2.3/exemplar/mgramseva/features/tabular-dashboard-collection.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.