## TL;DR

The Dynamics Web API property name is wrong. Check the exact logical name (case-sensitive, no display names) and fix it.

## Error

```text
dynamics 365 web api error: invalid property name
```

## Steps

1. Check the property's logical name in the metadata Expected: you have the exact name.
2. Fix the casing and spelling in your request Expected: it matches.
3. Re-run the call Expected: it succeeds.
4. Generate field names from metadata, not memory Expected: it cannot regress.

## When to use

- Dynamics invalid property name
- The field name is wrong

## When not to use

- The name is right (then check the entity set name)
- It worked before (then check for solution updates)

## Tool compatibility

- Dynamics Web API
- CRM integrations

## Variant phrasings

### dynamics invalid property name

Use the exact logical name. Display names do not work.

### web api invalid property dynamics

Same: check casing and the entity set.

## Why it happens

Display names and logical names differ, and agents use the human-readable one. The API wants the logical name exactly.

## Edge cases

- Navigation properties have their own naming (_x002e_ encoding)
- Custom fields need the publisher prefix

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_xc60cJCkzeaN5KK4EtftGg