Question 1

How do I implement server-side pagination with PrimeNG table in Angular?

Accepted Answer

Bind (onLazyLoad) to your data-fetching method and pass the event to primengTableHelper.getMaxResultCount and getSkipCount to compute page size and offset. Add a p-paginator with totalRecords bound to primengTableHelper.totalRecordsCount and call the same method on onPageChange.

Question 2

Why does my PrimeNG table load data twice on page init?

Accepted Answer

The double load happens when you call getRecords() in ngOnInit while (onLazyLoad) is also bound, because the table triggers onLazyLoad automatically on initialization. Remove the ngOnInit call and let the lazy load event fetch the data.

Question 3

How do I bind a signal to an input with ngModel in Angular?

Accepted Answer

Use [ngModel]="filterText()" together with (ngModelChange)="filterText.set($event)" to read and update the signal value. Do not use [(ngModel)]="filterText", which binds to the signal function reference instead of its value.

Question 4

Should I pass individual parameters or a DTO to NSwag-generated list services?

Accepted Answer

Always pass a single typed DTO input object such as new GetProductsInput({...}). NSwag generates HttpPost list methods that expect a typed DTO body, not individual query-string parameters.

Question 5

When should I use a simple table versus a paginated PrimeNG table?

Accepted Answer

Use the simple table pattern for small datasets where all records fit on one page, setting totalRecordsCount from the result items length. Use the paginated pattern with p-paginator and server-side skip/maxResultCount for large datasets.

angular-primeng-table-patterns

SYSTEM DOCUMENTATION & REQUIREMENTS

Frequently Asked Questions about angular-primeng-table-patterns

Related Skills

shared-api-types

syncfusion-aspnetcore-rich-text-editor

react/compose-with-tanstack-form

aggrid