C_LCNC_2406 · Question #48
While creating the collection of data records for a Data variable in SAP Build Apps, which of the following are available? Note: There are 2 correct answers to this question.
The correct answer is B. Paging D. Filter condition. When configuring a Data variable's collection of records in SAP Build Apps, Paging (B) and Filter condition (D) are built-in options that control how data is fetched - paging limits how many records are retrieved at once, while filter conditions narrow down which records are…
Question
While creating the collection of data records for a Data variable in SAP Build Apps, which of the following are available? Note: There are 2 correct answers to this question.
Options
- AAnnotation extensions
- BPaging
- CUser access permissions
- DFilter condition
How the community answered
(50 responses)- A6% (3)
- B92% (46)
- C2% (1)
Explanation
When configuring a Data variable's collection of records in SAP Build Apps, Paging (B) and Filter condition (D) are built-in options that control how data is fetched - paging limits how many records are retrieved at once, while filter conditions narrow down which records are returned based on criteria you define. These directly map to common OData/REST query capabilities that Data variables expose in their configuration panel.
Why A and C are wrong: Annotation extensions are a backend metadata concept (used in CAP/OData service definitions), not a client-side Data variable setting. User access permissions are managed at the backend service or BTP security level, not within the Data variable configuration in the Build Apps visual editor.
Memory tip: Think of a Data variable as a "smart query" - it lets you control how many records come back (Paging) and which records come back (Filter). Everything else - who can access data or how the schema is annotated - lives outside the app's data variable layer.
Topics
Community Discussion
No community discussion yet for this question.