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
Move relationship methods to client.tables namespace
- Add create_one_to_many, create_many_to_many, delete_relationship,
get_relationship, and create_lookup_field to TableOperations
- Remove flat relationship methods from DataverseClient (not yet published)
- Update relationships example and README to use client.tables.*
- Update tests to use namespaced API
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: README.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -112,7 +112,7 @@ The SDK provides a simple, pythonic interface for Dataverse operations:
112
112
| Concept | Description |
113
113
|---------|-------------|
114
114
|**DataverseClient**| Main entry point; provides `records`, `query`, and `tables` namespaces |
115
-
|**Namespaces**| Operations are organized into `client.records` (CRUD), `client.query` (queries), and `client.tables` (metadata) |
115
+
|**Namespaces**| Operations are organized into `client.records` (CRUD), `client.query` (queries), and `client.tables` (metadata & relationships) |
116
116
|**Records**| Dataverse records represented as Python dictionaries with column schema names |
117
117
|**Schema names**| Use table schema names (`"account"`, `"new_MyTestTable"`) and column schema names (`"name"`, `"new_MyTestColumn"`). See: [Table definitions in Microsoft Dataverse](https://learn.microsoft.com/en-us/power-apps/developer/data-platform/entity-metadata)|
118
118
|**Bulk Operations**| Efficient bulk processing for multiple records with automatic optimization |
0 commit comments