IPowerPortalsProService

The IPowerPortalsProService interface provides methods for performing CRUD operations, executing queries, managing relationships, and retrieving metadata from Dataverse. It is the primary service for server-side data access in PowerPortalsPro.

Note

In most cases you do not need to call IPowerPortalsProService directly. The RecordContext, MainContext, and grid components handle data operations automatically. Use this service for custom logic that falls outside the standard component workflow.

Server and Client Implementations

IPowerPortalsProService ships with two implementations registered automatically by the framework — your component code is identical against both, and the runtime injects whichever one matches the active render context:

• Server implementation (PowerPortalsPro.Web.Server, registered by AddPowerPortalsProWebServer) — runs in-process, talks to Dataverse directly through IOrganizationService, and applies your ITablePermissionHandler / ITableRecordPermissionHandler interceptors before any read or write. Selected when the page renders under InteractiveServerRenderMode or static SSR.
• Client implementation (PowerPortalsPro.Web.Client, registered by AddPowerPortalsProWebClient) — runs in the browser under WebAssembly, has no Dataverse SDK at all, and instead JSON-serializes each call out to the corresponding server-side HTTP endpoint (/api/table/{name}, /api/retrieveMultiple, etc.). Permission handlers still apply because the request lands back on the server's endpoint. See the Client API page for the wire format and the routes the client implementation calls.

Because the contract is identical, the same component works under any interactivity mode (Server, WebAssembly, or Auto). Code that calls _powerPortalsProService.RetrieveRecordAsync(...) in a Server-rendered page does an in-process Dataverse call; the same line in a WASM-rendered page issues an HTTP request — no branching required.

Injecting the Service

Inject IPowerPortalsProService into any Blazor component or service via constructor or property injection.

Retrieving a Record

Use RetrieveRecordAsync to fetch a single record by table name and ID. Optionally specify which columns to return; if omitted, all columns are returned.

Querying Multiple Records

Use RetrieveRecordsAsync with a FetchXML query string to retrieve multiple records with filtering, sorting, and linked entity support.

Creating a Record

Use CreateRecordAsync to create a new record in Dataverse. The response contains the ID of the newly created record.

Updating a Record

Use UpdateRecordAsync to update an existing record. Only the properties set on the TableRecord are sent to Dataverse.

Deleting a Record

Use DeleteRecordAsync to delete a record by table name and ID.

Associating Records

Use AssociateAsync and DisassociateAsync to manage many-to-many relationships between records.

Executing Requests

Use ExecuteAsync for a single request or ExecuteMultipleAsync to execute multiple requests in a single database transaction. If any request in a transactional batch fails, all changes are rolled back.

Retrieving Metadata

Use RetrieveTableMetadataAsync and RetrieveViewMetadataAsync to retrieve table and view metadata. For cached access, prefer ITableMetadataCache and IViewMetadataCache instead.

Working with Files

Use GetFileInfoAsync to retrieve file or image metadata and optionally the binary content from a file or image column.