What It Means

In Joomla Component Builder (JCB), every Dynamic GET can be marked as either a:

• 🧾 List GET — designed to return multiple records (array or object list)
• 🔍 Item GET — intended to return a single row (single item detail view)

This setting directly affects:

• The model method’s return behavior
• Whether pagination and filters are auto-applied
• The context of use (list views, detail pages, modals, etc.)

You control this setting via the Dynamic GET configuration screen using a toggle or dropdown labeled something like “Result Type” or “Return Mode”.

Why It Matters

• ✅ Contextual Output
  In a Site View’s list screen, you’ll want a GET to return many records. But on a detail page (or modal), you want only one — typically by ID or slug.
• 🔁 Shared Logic, Separate Usage
  The same base query (joins, filters) could be used in both forms — one as a list (table), one as an item (card or profile).
• 📦 Model Code Optimization
  JCB compiles efficient code for the intended use. In list mode, you’ll see loadObjectList() and pagination logic; in item mode, loadObject() or loadAssoc() is used instead.
• 💡 Combined GETs
  Some views in JCB support multiple Dynamic GETs. You can assign one as the list source and another as the item fetcher — letting you fetch related data or secondary lookups in parallel.

Use Cases

• Frontend blog view (list of articles) + article detail (item)
• Admin import list + modal for editing one row
• Dashboard summary (list) + modal drill-down (item)

Tips for Usage

• Always filter Item GETs by primary key or slug
• List GETs benefit from pagination and ordering
• Choose the right return type early in development to avoid unexpected behavior

Conclusion

Switching between List and Item modes in Dynamic GETs ensures your data logic is suited for the view's purpose. Whether you're building complex interfaces or simple listings, this toggle saves time while keeping data fetching clean and purpose-driven.