Info

Info fields display runtime information such as app title, screen title, row counts, row position, and pagination values from the current Buzzy context.

Info fields are read-only display fields that show information Buzzy already knows at runtime. They do not collect data and they do not calculate values with a formula. Instead, they read from the current app, screen, row, view, or pagination context.

Common uses include showing the current screen title, numbering rows in a list, showing a total result count, or displaying pagination text such as Showing 1-10 of 42.

Information types

Information Type	Displays	Context required
buzzTitle	The app title	App context
screenTitle	The current screen title	Screen context
rowIndex	The current row's position in a repeating view	Row/view context
rowIndexReverse	The current row's reverse position in a repeating view	Row/view context
rowCount	The total number of rows in the current view	View context
embeddedRowCount	The total number of rows in an embedded/subtable view	Embedded view/subtable context
pageIndex	The current page number for a paginated view	Paginated view context
pageCount	The total number of pages for a paginated view	Paginated view context
firstOnPage	The first row number on the current page	Paginated view context
lastOnPage	The last row number on the current page	Paginated view context

How context works

Buzzy screens are built from nested components. Some components provide data context to their children. A view component, for example, fetches rows and repeats its result layout for each row. Info fields read from the nearest relevant context around them.

This means placement matters. If an Info field is outside the view it is meant to describe, it may not have access to that view's rows, page information, or embedded child records.

For counts and pagination, put the Info field inside the same view component as the rows it describes. For embedded or subtable counts, put the Info field inside the embedded child view context.

Placement rules

Use these rules when placing Info fields:

• Use buzzTitle and screenTitle anywhere that has normal app or screen context.

• Use rowIndex and rowIndexReverse inside a repeating row/card layout.

• Use rowCount inside the view component whose rows you want to count.

• Use pageIndex, pageCount, firstOnPage, and lastOnPage inside the paginated view component they describe.

• Use embeddedRowCount inside the embedded/subtable view context.

Do not place count or pagination Info fields in a header, footer, or nearby container that sits outside the view component unless that container is still inside the same view context.

Standard view counts

For a normal list, table, gallery, or card view, place the rowCount Info field inside the relevant view component.

Example structure:

Screen
`-- Customers view
    `-- Results layout
        |-- Summary text: "Customers"
        |-- Info field: rowCount
        `-- Customer row/card
            |-- Name
            `-- Email

In this structure, rowCount can read the row count from Customers view.

If the same rowCount field is moved outside Customers view, it may show 0, stay blank, or show a count from a different context.

Pagination values

Pagination Info fields must be placed inside the paginated view they describe.

For example, to show Showing 1-10 of 42, place these Info fields inside the same paginated view:

• firstOnPage

• lastOnPage

• rowCount

To show Page 2 of 5, place these Info fields inside the same paginated view:

• pageIndex

• pageCount

Example structure:

Screen
`-- Orders view
    `-- Results layout
        |-- Text: "Showing"
        |-- Info field: firstOnPage
        |-- Text: "-"
        |-- Info field: lastOnPage
        |-- Text: "of"
        |-- Info field: rowCount
        `-- Order row/card

Keep pagination buttons and pagination Info fields inside the relevant view component so they share the same page state.

Embedded and subtable counts

Use embeddedRowCount when you need to show the number of child rows in an embedded view, such as a view inside a sub-table field.

Example:

Project detail screen
`-- Current Project row
    `-- Tasks sub-table field
        `-- Embedded Tasks view
            `-- Results layout
                |-- Text: "Tasks"
                |-- Info field: embeddedRowCount
                `-- Task row/card
                    |-- Task title
                    `-- Status

In this structure, embeddedRowCount can read the number of task rows for the current project.

If the count is placed outside the embedded tasks view, it may not be connected to the child-row context. A common symptom is that task rows are visible elsewhere on the screen, but the count still shows 0.

For more detail on parent and child records, see Sub-tables.

Troubleshooting

Rows are visible, but the count shows 0

Check whether the Info field is inside the same view context as the visible rows.

For a normal view, use rowCount and place it inside that view component. For a subtable or embedded child view, use embeddedRowCount and place it inside the embedded child view.

Pagination numbers are blank or wrong

Check that pageIndex, pageCount, firstOnPage, and lastOnPage are inside the paginated view component. If they are outside the view, they may not have access to the page state.

Row numbers are blank or repeated

Check that rowIndex or rowIndexReverse is inside the repeating row/card layout, not in a static area outside the results layout.

---