Custom fields missing in JSON response when retrieving service cases via OData

CRM Microsoft Dynamics 365 Sales
, , , , , , , ,
1

We added custom fields to service cases in Power Apps (priority_reason, escalation_notes, sla_override_flag) but they don’t appear in API responses. Standard fields like title and status return fine, but our custom fields are missing from the JSON. Query:


GET /api/data/v9.2/incidents?$select=title,new_priorityreason
Authorization: Bearer {token}

The response includes title but new_priorityreason is null even though it has data in the UI. We need these fields for our reporting dashboard that pulls case data every hour. Is this a schema naming issue or an API permissions problem with Power Apps customizations?

2

Custom fields in D365 use schema names with publisher prefixes. If you created the field as ‘priority_reason’, the actual schema name might be ‘new_priorityreason’ or ‘cr123_priorityreason’ depending on your solution publisher. Check the exact schema name in Power Apps customization.

3

Try querying without the $select parameter first to see if the fields appear in the full response. Sometimes OData $select usage can be tricky with custom fields. Also, verify the fields are actually populated with data - null in the API response could mean genuinely empty fields rather than a permissions issue.