You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fix File-column typing and suppress OData-shadowed nav props
- Bump Microsoft.CrmSdk.XrmTooling.CoreAssembly to 9.1.1.65 so the SOAP
deserializer returns FileAttributeMetadata instead of silently dropping it
- Type File columns as string | null (matching the Web API GUID wire value)
- Add isShadowedByScalar filter: nav props whose name is claimed by a
non-lookup scalar (File, Uniqueidentifier, etc.) are now excluded from
ManyToOne read/write interfaces and @odata.bind entries, matching the
OData CSDL which cannot expose both a Property and NavigationProperty
under the same name
Copy file name to clipboardExpand all lines: CHANGELOG.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,6 +18,8 @@
18
18
### Fixed
19
19
- Updated `xrm.d.ts` from the original XRM library
20
20
- Fixed ManyToMany relationship navigation property names being swapped when the current entity is the second entity in the relationship
21
+
- File-type columns now appear in generated typings as `string | null` (previously silently dropped by the old SDK SOAP deserializer); requires `Microsoft.CrmSdk.XrmTooling.CoreAssembly` ≥ 9.1.1.65
22
+
- Navigation properties that are shadowed by a same-named non-lookup scalar (e.g. File, Uniqueidentifier) are now suppressed from `ManyToOne` read/write interfaces and `@odata.bind` create/update interfaces, matching the OData CSDL wire surface
0 commit comments