Open aqndev1 opened 2 months ago
Upon deployment, the path is altered with the data-api prefix. However, when the result exceeds the 100-row limit, a nextLink property is provided, but the nextLink doesn't contain the data-api prefix. So when using for example ADF, the absoluteUrl is the REST-connector cannot be used. URL: https://xxxxxx.x.azurestaticapps.net/data-api/rest/entityName nextLink property: https://xxxxxx.x.azurestaticapps.net/rest/entityName
latest
Azure SQL
Static Web Apps (SWA)
REST
No response
What happened?
Upon deployment, the path is altered with the data-api prefix. However, when the result exceeds the 100-row limit, a nextLink property is provided, but the nextLink doesn't contain the data-api prefix. So when using for example ADF, the absoluteUrl is the REST-connector cannot be used. URL: https://xxxxxx.x.azurestaticapps.net/data-api/rest/entityName nextLink property: https://xxxxxx.x.azurestaticapps.net/rest/entityName
Version
latest
What database are you using?
Azure SQL
What hosting model are you using?
Static Web Apps (SWA)
Which API approach are you accessing DAB through?
REST
Relevant log output
No response
Code of Conduct