The documentation for Power Pages Server Logic is still quite thin since it is in preview, so you are hitting real gaps.
Here is what is confirmed and what is not.
The additionalParameters argument in Server.Connector.Dataverse.RetrieveMultipleRecords maps to OData query string options passed to the Dataverse Web API. The syntax should follow standard OData format starting with ? and then the query options. For example:
Server.Connector.Dataverse.RetrieveMultipleRecords("contacts", "?$select=firstname,lastname&$filter=statecode eq 0&$top=10")
The not supported error you are getting on filter and top likely means one of these things:
1. The additionalParameters value is being passed incorrectly. It needs to start with ? and the options need to be URL-encoded where necessary. Special characters like spaces in filter values must be URL-encoded.
2. The Server.Connector.Dataverse connector in server logic may not support the full set of OData options that the standard Dataverse Web API does. Since this feature is in preview the supported subset is not fully documented. Based on what the docs show, the second argument is passed through as an OData query string but there are known cases where certain options may not be supported depending on the preview version.
3. Table permissions on the Power Pages site must also allow the read operation. If table permissions are too restrictive, filters that rely on fields not covered by the permission scope can fail.
What to try:
- Confirm the exact error message from Server.Logger.Error to see what the server returns
- Try a minimal filter first: "?$top=5" only, to confirm top works in isolation
- Then add "?$select=name" to confirm select works
- Then add "?$filter=statecode eq 0" to confirm filter works
- If individual options work but combined ones fail, this is a preview limitation worth reporting via the Power Pages feedback
Also worth knowing: if Server.Connector.Dataverse proves too limited for complex queries, the alternative is to call the Dataverse Web API directly using Server.Http (if available in your preview version), which gives full OData flexibility.
What exact error message are you getting and what does your additionalParameters value look like?
Best regards,
Valantis
✅ If this helped solve your issue, please Accept as Solution so others can find it quickly.
❤️ If it didn’t fully solve it but was still useful, please click “Yes” on “Was this reply helpful?” or leave a Like :).
🏷️ For follow-ups @Valantis.
📝 https://valantisond365.com/
