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
Copy file name to clipboardExpand all lines: README.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -99,12 +99,12 @@ The SDK provides a simple, pythonic interface for Dataverse operations:
99
99
| Concept | Description |
100
100
|---------|-------------|
101
101
|**DataverseClient**| Main entry point for all operations with environment connection |
102
-
|**Records**| Dataverse records represented as Python dictionaries with logical field names |
103
-
|**Logical Names**| Use table logical names (`"account"`) and column logical names (`"name"`) |
102
+
|**Records**| Dataverse records represented as Python dictionaries with column schema names |
103
+
|**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)|
104
104
|**Bulk Operations**| Efficient bulk processing for multiple records with automatic optimization |
105
105
|**Paging**| Automatic handling of large result sets with iterators |
106
106
|**Structured Errors**| Detailed exception hierarchy with retry guidance and diagnostic information |
107
-
|**Customization prefix values**| Custom tables and columns require a customization prefix value to be included for all operations (e.g., `"new_Title"`, not `"Title"`). See: [Table definitions in Microsoft Dataverse](https://learn.microsoft.com/en-us/power-apps/developer/data-platform/entity-metadata)|
107
+
|**Customization prefix values**| Custom tables and columns require a customization prefix value to be included for all operations (e.g., `"new_MyTestTable"`, not `"MyTestTable"`). See: [Table definitions in Microsoft Dataverse](https://learn.microsoft.com/en-us/power-apps/developer/data-platform/entity-metadata)|
108
108
109
109
## Examples
110
110
@@ -176,7 +176,7 @@ for record in results:
176
176
print(record["name"])
177
177
178
178
# OData query with paging
179
-
# Note: filter and expand parameters require exact casing
179
+
# Note: filter and expand parameters are case sensitive
180
180
pages = client.get(
181
181
"account",
182
182
select=["accountid", "name"], # select is case-insensitive (automatically lowercased)
plural_hint=" (did you pass a plural entity set name instead of the singular logical name?)"iflogical.endswith("s") andnotlogical.endswith("ss") else""
697
+
plural_hint=" (did you pass a plural entity set name instead of the singular table schema name?)"iftable_schema_name.endswith("s") andnottable_schema_name.endswith("ss") else""
698
698
raiseMetadataError(
699
-
f"Unable to resolve entity set for logical name '{logical}'. Provide the singular logical name.{plural_hint}",
699
+
f"Unable to resolve entity set for table schema name '{table_schema_name}'. Provide the singular table schema name.{plural_hint}",
700
700
subcode=ec.METADATA_ENTITYSET_NOT_FOUND,
701
701
)
702
702
md=items[0]
703
703
es=md.get("EntitySetName")
704
704
ifnotes:
705
705
raiseMetadataError(
706
-
f"Metadata response missing EntitySetName for logical '{logical}'.",
706
+
f"Metadata response missing EntitySetName for table schema name '{table_schema_name}'.",
0 commit comments