From ceb9e998d07f4a2dfd60cec8b64496301deea671 Mon Sep 17 00:00:00 2001 From: Microsoft Graph DevX Tooling Date: Tue, 10 Dec 2024 12:27:53 +0000 Subject: [PATCH] feat(generation): update request builders and models Update generated files with build 173698 --- ...resource_connection_item_request_builder.py | 6 +++--- .../updatable_asset_item_request_builder.py | 8 ++++---- .../compliance_change_item_request_builder.py | 12 ++++++------ .../invite/invite_request_builder.py | 6 +++--- .../hardware_oath_devices_request_builder.py | 6 +++--- .../assign_to/assign_to_request_builder.py | 6 +++--- ...ation_method_device_item_request_builder.py | 6 +++--- .../invite/invite_request_builder.py | 6 +++--- ...led_action_for_rule_item_request_builder.py | 6 +++--- ...heduled_actions_for_rule_request_builder.py | 6 +++--- .../retrieve_review_status_request_builder.py | 5 +++-- .../retrieve_snapshots_request_builder.py | 7 ++++--- .../set_review_status_request_builder.py | 5 +++-- ...ntication_method_devices_request_builder.py | 6 +++--- .../hardware_oath_devices_request_builder.py | 12 +++++++----- .../assign_to/assign_to_request_builder.py | 6 +++--- ...ation_method_device_item_request_builder.py | 17 ++++++++++------- .../workbook/tables/add/add_request_builder.py | 6 +++--- .../item/tables/add/add_request_builder.py | 6 +++--- ...uthorization_system_item_request_builder.py | 6 +++--- .../item/schema/schema_request_builder.py | 6 +++--- .../data_connectors_request_builder.py | 6 +++--- .../inbound_flows_request_builder.py | 6 +++--- .../generated/groups/groups_request_builder.py | 6 +++--- .../delta/delta_request_builder.py | 6 +++--- .../delta/delta_request_builder.py | 6 +++--- .../instances/delta/delta_request_builder.py | 6 +++--- .../instances/delta/delta_request_builder.py | 6 +++--- .../delta/delta_request_builder.py | 6 +++--- .../events/delta/delta_request_builder.py | 6 +++--- .../delta/delta_request_builder.py | 6 +++--- .../instances/delta/delta_request_builder.py | 6 +++--- .../instances/delta/delta_request_builder.py | 6 +++--- .../delta/delta_request_builder.py | 6 +++--- .../delta/delta_request_builder.py | 6 +++--- .../delta/delta_request_builder.py | 6 +++--- .../instances/delta/delta_request_builder.py | 6 +++--- .../instances/delta/delta_request_builder.py | 6 +++--- .../delta/delta_request_builder.py | 6 +++--- .../conversations_request_builder.py | 6 +++--- .../item/conversation_item_request_builder.py | 14 +++++++------- .../item/reply/reply_request_builder.py | 6 +++--- .../item/events/delta/delta_request_builder.py | 6 +++--- .../delta/delta_request_builder.py | 6 +++--- .../instances/delta/delta_request_builder.py | 6 +++--- .../instances/delta/delta_request_builder.py | 6 +++--- .../delta/delta_request_builder.py | 6 +++--- .../item/notebook_item_request_builder.py | 6 +++--- .../notebooks/notebooks_request_builder.py | 6 +++--- .../item/onenote_page_item_request_builder.py | 6 +++--- .../onenote/pages/pages_request_builder.py | 6 +++--- .../item/section_group_item_request_builder.py | 6 +++--- .../section_groups_request_builder.py | 6 +++--- .../onenote_section_item_request_builder.py | 6 +++--- .../sections/sections_request_builder.py | 6 +++--- .../item/notebook_item_request_builder.py | 6 +++--- .../notebooks/notebooks_request_builder.py | 6 +++--- .../item/onenote_page_item_request_builder.py | 6 +++--- .../onenote/pages/pages_request_builder.py | 6 +++--- .../item/section_group_item_request_builder.py | 6 +++--- .../section_groups_request_builder.py | 6 +++--- .../onenote_section_item_request_builder.py | 6 +++--- .../sections/sections_request_builder.py | 6 +++--- .../item/reply/reply_request_builder.py | 6 +++--- .../named_location_item_request_builder.py | 6 +++--- ...m_callout_extension_item_request_builder.py | 8 ++++---- ..._workflow_extension_item_request_builder.py | 6 +++--- .../access_package_item_request_builder.py | 8 ++++---- ...ackages_with_unique_name_request_builder.py | 8 ++++---- .../item/agreement_item_request_builder.py | 8 ++++---- .../risk_detection_item_request_builder.py | 8 ++++---- msgraph_beta/generated/kiota-lock.json | 4 ++-- .../models/android_managed_app_protection.py | 4 ++-- .../generated/models/authentication.py | 2 +- .../models/authentication_method_device.py | 4 ++-- .../generated/models/base_site_page.py | 2 +- ...c_cross_region_disaster_recovery_setting.py | 4 ++-- .../models/device_compliance_policy.py | 2 +- ..._configuration_choice_setting_definition.py | 4 ++-- ...nfiguration_referred_setting_information.py | 2 +- ...tion_setting_group_collection_definition.py | 4 ++-- ...t_configuration_setting_group_definition.py | 2 +- ...ion_simple_setting_collection_definition.py | 4 ++-- msgraph_beta/generated/models/directory.py | 2 +- .../models/educational_activity_detail.py | 6 +++--- .../generated/models/expiration_pattern.py | 4 ++-- .../external_connectors/configuration.py | 2 +- .../models/external_connectors/external.py | 2 +- .../hardware_oath_authentication_method.py | 2 +- ..._oath_token_authentication_method_device.py | 18 +++++++++--------- msgraph_beta/generated/models/identity.py | 4 ++-- msgraph_beta/generated/models/identity_set.py | 6 +++--- msgraph_beta/generated/models/initiator.py | 2 +- .../generated/models/item_attachment.py | 2 +- .../generated/models/key_value_pair.py | 4 ++-- .../mac_os_lob_app_assignment_settings.py | 2 +- msgraph_beta/generated/models/mail_tips.py | 10 +++++----- .../models/mailbox_restore_artifact.py | 4 ++-- .../models/networkaccess/connectivity.py | 4 ++-- .../generated/models/networkaccess/profile.py | 6 +++--- .../generated/models/news_link_page.py | 6 +++--- ...tion_external_users_self_service_sign_up.py | 2 +- .../on_interactive_auth_flow_start_listener.py | 2 +- ...one_drive_for_business_protection_policy.py | 4 ++-- .../one_drive_for_business_restore_session.py | 2 +- msgraph_beta/generated/models/onenote.py | 8 ++++---- .../models/restore_session_artifact_count.py | 8 ++++---- .../generated/models/restore_session_base.py | 4 ++-- .../windows_domain_join_configuration.py | 2 +- ..._universal_app_x_app_assignment_settings.py | 2 +- .../item/policy_link_item_request_builder.py | 6 +++--- .../item/policies/policies_request_builder.py | 6 +++--- .../item/policy_link_item_request_builder.py | 6 +++--- .../item/policies/policies_request_builder.py | 6 +++--- .../remote_network_item_request_builder.py | 6 +++--- .../remote_networks_request_builder.py | 6 +++--- .../item/policy_link_item_request_builder.py | 6 +++--- .../item/policies/policies_request_builder.py | 6 +++--- ...identity_synchronization_request_builder.py | 6 +++--- ..._token_validation_policy_request_builder.py | 8 ++++---- .../risk_detections_request_builder.py | 8 ++++---- .../claims_policy_request_builder.py | 12 ++++++------ .../item/notebook_item_request_builder.py | 6 +++--- .../notebooks/notebooks_request_builder.py | 6 +++--- .../item/onenote_page_item_request_builder.py | 6 +++--- .../onenote/pages/pages_request_builder.py | 6 +++--- .../item/section_group_item_request_builder.py | 6 +++--- .../section_groups_request_builder.py | 6 +++--- .../onenote_section_item_request_builder.py | 6 +++--- .../sections/sections_request_builder.py | 6 +++--- .../sites/item/pages/pages_request_builder.py | 6 +++--- ...ive_protection_unit_item_request_builder.py | 6 +++--- ...ve_restore_artifact_item_request_builder.py | 6 +++--- .../item/messages/messages_request_builder.py | 6 +++--- .../open_shifts/open_shifts_request_builder.py | 4 ++-- ...ph_managed_tenants_apply_request_builder.py | 4 ++-- .../join_request_request_builder.py | 4 ++-- ...ulti_tenant_organization_request_builder.py | 6 +++--- .../assign_and_activate_request_builder.py | 5 +++-- ...ctivate_by_serial_number_request_builder.py | 5 +++-- .../hardware_oath_methods_request_builder.py | 6 +++--- .../item/activate/activate_request_builder.py | 5 +++-- .../deactivate/deactivate_request_builder.py | 5 +++-- .../assign_to/assign_to_request_builder.py | 6 +++--- .../item/device/device_request_builder.py | 6 +++--- .../hardware_oath_devices_request_builder.py | 6 +++--- .../assign_to/assign_to_request_builder.py | 6 +++--- ...ation_method_device_item_request_builder.py | 6 +++--- ...thentication_method_item_request_builder.py | 6 +++--- .../delta/delta_request_builder.py | 6 +++--- .../delta/delta_request_builder.py | 6 +++--- .../instances/delta/delta_request_builder.py | 6 +++--- .../instances/delta/delta_request_builder.py | 6 +++--- .../delta/delta_request_builder.py | 6 +++--- .../events/delta/delta_request_builder.py | 6 +++--- .../delta/delta_request_builder.py | 6 +++--- .../instances/delta/delta_request_builder.py | 6 +++--- .../instances/delta/delta_request_builder.py | 6 +++--- .../delta/delta_request_builder.py | 6 +++--- .../delta/delta_request_builder.py | 6 +++--- .../delta/delta_request_builder.py | 6 +++--- .../instances/delta/delta_request_builder.py | 6 +++--- .../instances/delta/delta_request_builder.py | 6 +++--- .../delta/delta_request_builder.py | 6 +++--- .../item/events/delta/delta_request_builder.py | 6 +++--- .../delta/delta_request_builder.py | 6 +++--- .../instances/delta/delta_request_builder.py | 6 +++--- .../instances/delta/delta_request_builder.py | 6 +++--- .../delta/delta_request_builder.py | 6 +++--- .../delta/delta_request_builder.py | 6 +++--- .../delta/delta_request_builder.py | 6 +++--- .../instances/delta/delta_request_builder.py | 6 +++--- .../instances/delta/delta_request_builder.py | 6 +++--- .../delta/delta_request_builder.py | 6 +++--- .../delta/delta_request_builder.py | 6 +++--- .../delta/delta_request_builder.py | 6 +++--- .../instances/delta/delta_request_builder.py | 6 +++--- .../instances/delta/delta_request_builder.py | 6 +++--- .../delta/delta_request_builder.py | 6 +++--- .../item/events/delta/delta_request_builder.py | 6 +++--- .../delta/delta_request_builder.py | 6 +++--- .../instances/delta/delta_request_builder.py | 6 +++--- .../instances/delta/delta_request_builder.py | 6 +++--- .../delta/delta_request_builder.py | 6 +++--- .../retrieve_review_status_request_builder.py | 5 +++-- .../retrieve_snapshots_request_builder.py | 7 ++++--- .../set_review_status_request_builder.py | 5 +++-- .../item/events/delta/delta_request_builder.py | 6 +++--- .../delta/delta_request_builder.py | 6 +++--- .../instances/delta/delta_request_builder.py | 6 +++--- .../instances/delta/delta_request_builder.py | 6 +++--- .../delta/delta_request_builder.py | 6 +++--- .../messages/delta/delta_request_builder.py | 6 +++--- .../messages/delta/delta_request_builder.py | 6 +++--- .../messages/delta/delta_request_builder.py | 6 +++--- .../item/notebook_item_request_builder.py | 6 +++--- .../notebooks/notebooks_request_builder.py | 6 +++--- .../item/onenote_page_item_request_builder.py | 6 +++--- .../onenote/pages/pages_request_builder.py | 6 +++--- .../item/section_group_item_request_builder.py | 6 +++--- .../section_groups_request_builder.py | 6 +++--- .../onenote_section_item_request_builder.py | 6 +++--- .../sections/sections_request_builder.py | 6 +++--- .../item/presence/presence_request_builder.py | 8 ++++---- 204 files changed, 603 insertions(+), 588 deletions(-) diff --git a/msgraph_beta/generated/admin/windows/updates/resource_connections/item/resource_connection_item_request_builder.py b/msgraph_beta/generated/admin/windows/updates/resource_connections/item/resource_connection_item_request_builder.py index d76b514079d..1530b5d8e61 100644 --- a/msgraph_beta/generated/admin/windows/updates/resource_connections/item/resource_connection_item_request_builder.py +++ b/msgraph_beta/generated/admin/windows/updates/resource_connections/item/resource_connection_item_request_builder.py @@ -31,10 +31,10 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def delete(self,request_configuration: Optional[RequestConfiguration[QueryParameters]] = None) -> None: """ - Delete an operationalInsightsConnection object. + Delete a resourceConnection object. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: None - Find more info here: https://learn.microsoft.com/graph/api/windowsupdates-operationalinsightsconnection-delete?view=graph-rest-beta + Find more info here: https://learn.microsoft.com/graph/api/windowsupdates-resourceconnection-delete?view=graph-rest-beta """ request_info = self.to_delete_request_information( request_configuration @@ -94,7 +94,7 @@ async def patch(self,body: ResourceConnection, request_configuration: Optional[R def to_delete_request_information(self,request_configuration: Optional[RequestConfiguration[QueryParameters]] = None) -> RequestInformation: """ - Delete an operationalInsightsConnection object. + Delete a resourceConnection object. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ diff --git a/msgraph_beta/generated/admin/windows/updates/updatable_assets/item/updatable_asset_item_request_builder.py b/msgraph_beta/generated/admin/windows/updates/updatable_assets/item/updatable_asset_item_request_builder.py index 316b5a0e5ea..8695cf2799b 100644 --- a/msgraph_beta/generated/admin/windows/updates/updatable_assets/item/updatable_asset_item_request_builder.py +++ b/msgraph_beta/generated/admin/windows/updates/updatable_assets/item/updatable_asset_item_request_builder.py @@ -54,10 +54,10 @@ async def delete(self,request_configuration: Optional[RequestConfiguration[Query async def get(self,request_configuration: Optional[RequestConfiguration[UpdatableAssetItemRequestBuilderGetQueryParameters]] = None) -> Optional[UpdatableAsset]: """ - Read the properties and relationships of an updatableAssetGroup object. + Read the properties and relationships of an updatableAsset object. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[UpdatableAsset] - Find more info here: https://learn.microsoft.com/graph/api/windowsupdates-updatableassetgroup-get?view=graph-rest-beta + Find more info here: https://learn.microsoft.com/graph/api/windowsupdates-updatableasset-get?view=graph-rest-beta """ request_info = self.to_get_request_information( request_configuration @@ -109,7 +109,7 @@ def to_delete_request_information(self,request_configuration: Optional[RequestCo def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[UpdatableAssetItemRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Read the properties and relationships of an updatableAssetGroup object. + Read the properties and relationships of an updatableAsset object. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -189,7 +189,7 @@ class UpdatableAssetItemRequestBuilderDeleteRequestConfiguration(RequestConfigur @dataclass class UpdatableAssetItemRequestBuilderGetQueryParameters(): """ - Read the properties and relationships of an updatableAssetGroup object. + Read the properties and relationships of an updatableAsset object. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/admin/windows/updates/update_policies/item/compliance_changes/item/compliance_change_item_request_builder.py b/msgraph_beta/generated/admin/windows/updates/update_policies/item/compliance_changes/item/compliance_change_item_request_builder.py index 7f18c9d93db..e1232f365ae 100644 --- a/msgraph_beta/generated/admin/windows/updates/update_policies/item/compliance_changes/item/compliance_change_item_request_builder.py +++ b/msgraph_beta/generated/admin/windows/updates/update_policies/item/compliance_changes/item/compliance_change_item_request_builder.py @@ -32,10 +32,10 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def delete(self,request_configuration: Optional[RequestConfiguration[QueryParameters]] = None) -> None: """ - Delete a complianceChange object. + Delete a contentApproval object. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: None - Find more info here: https://learn.microsoft.com/graph/api/windowsupdates-compliancechange-delete?view=graph-rest-beta + Find more info here: https://learn.microsoft.com/graph/api/windowsupdates-contentapproval-delete?view=graph-rest-beta """ request_info = self.to_delete_request_information( request_configuration @@ -72,11 +72,11 @@ async def get(self,request_configuration: Optional[RequestConfiguration[Complian async def patch(self,body: ComplianceChange, request_configuration: Optional[RequestConfiguration[QueryParameters]] = None) -> Optional[ComplianceChange]: """ - Update the properties of a complianceChange object. + Update the properties of a contentApproval object. param body: The request body param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[ComplianceChange] - Find more info here: https://learn.microsoft.com/graph/api/windowsupdates-compliancechange-update?view=graph-rest-beta + Find more info here: https://learn.microsoft.com/graph/api/windowsupdates-contentapproval-update?view=graph-rest-beta """ if body is None: raise TypeError("body cannot be null.") @@ -96,7 +96,7 @@ async def patch(self,body: ComplianceChange, request_configuration: Optional[Req def to_delete_request_information(self,request_configuration: Optional[RequestConfiguration[QueryParameters]] = None) -> RequestInformation: """ - Delete a complianceChange object. + Delete a contentApproval object. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -118,7 +118,7 @@ def to_get_request_information(self,request_configuration: Optional[RequestConfi def to_patch_request_information(self,body: ComplianceChange, request_configuration: Optional[RequestConfiguration[QueryParameters]] = None) -> RequestInformation: """ - Update the properties of a complianceChange object. + Update the properties of a contentApproval object. param body: The request body param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation diff --git a/msgraph_beta/generated/app/calls/item/participants/invite/invite_request_builder.py b/msgraph_beta/generated/app/calls/item/participants/invite/invite_request_builder.py index a3c03a7c1b7..c25899d22a2 100644 --- a/msgraph_beta/generated/app/calls/item/participants/invite/invite_request_builder.py +++ b/msgraph_beta/generated/app/calls/item/participants/invite/invite_request_builder.py @@ -32,11 +32,11 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def post(self,body: InvitePostRequestBody, request_configuration: Optional[RequestConfiguration[QueryParameters]] = None) -> Optional[InviteParticipantsOperation]: """ - Invite participants to the active call. For more information about how to handle operations, see commsOperation. + Delete a specific participant in a call. In some situations, it is appropriate for an application to remove a participant from an active call. This action can be done before or after the participant answers the call. When an active caller is removed, they are immediately dropped from the call with no pre- or post-removal notification. When an invited participant is removed, any outstanding add participant request is canceled. param body: The request body param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[InviteParticipantsOperation] - Find more info here: https://learn.microsoft.com/graph/api/participant-invite?view=graph-rest-beta + Find more info here: https://learn.microsoft.com/graph/api/participant-delete?view=graph-rest-beta """ if body is None: raise TypeError("body cannot be null.") @@ -56,7 +56,7 @@ async def post(self,body: InvitePostRequestBody, request_configuration: Optional def to_post_request_information(self,body: InvitePostRequestBody, request_configuration: Optional[RequestConfiguration[QueryParameters]] = None) -> RequestInformation: """ - Invite participants to the active call. For more information about how to handle operations, see commsOperation. + Delete a specific participant in a call. In some situations, it is appropriate for an application to remove a participant from an active call. This action can be done before or after the participant answers the call. When an active caller is removed, they are immediately dropped from the call with no pre- or post-removal notification. When an invited participant is removed, any outstanding add participant request is canceled. param body: The request body param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation diff --git a/msgraph_beta/generated/authentication_method_devices/item/hardware_oath_devices/hardware_oath_devices_request_builder.py b/msgraph_beta/generated/authentication_method_devices/item/hardware_oath_devices/hardware_oath_devices_request_builder.py index b6597260968..9a6e2e5931a 100644 --- a/msgraph_beta/generated/authentication_method_devices/item/hardware_oath_devices/hardware_oath_devices_request_builder.py +++ b/msgraph_beta/generated/authentication_method_devices/item/hardware_oath_devices/hardware_oath_devices_request_builder.py @@ -48,7 +48,7 @@ def by_hardware_oath_token_authentication_method_device_id(self,hardware_oath_to async def get(self,request_configuration: Optional[RequestConfiguration[HardwareOathDevicesRequestBuilderGetQueryParameters]] = None) -> Optional[HardwareOathTokenAuthenticationMethodDeviceCollectionResponse]: """ - Get hardwareOathDevices from authenticationMethodDevices + Exposes the hardware OATH method in the directory. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[HardwareOathTokenAuthenticationMethodDeviceCollectionResponse] """ @@ -91,7 +91,7 @@ async def post(self,body: HardwareOathTokenAuthenticationMethodDevice, request_c def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[HardwareOathDevicesRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Get hardwareOathDevices from authenticationMethodDevices + Exposes the hardware OATH method in the directory. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -137,7 +137,7 @@ def count(self) -> CountRequestBuilder: @dataclass class HardwareOathDevicesRequestBuilderGetQueryParameters(): """ - Get hardwareOathDevices from authenticationMethodDevices + Exposes the hardware OATH method in the directory. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/authentication_method_devices/item/hardware_oath_devices/item/assign_to/assign_to_request_builder.py b/msgraph_beta/generated/authentication_method_devices/item/hardware_oath_devices/item/assign_to/assign_to_request_builder.py index fdf6eb46329..55b1a244806 100644 --- a/msgraph_beta/generated/authentication_method_devices/item/hardware_oath_devices/item/assign_to/assign_to_request_builder.py +++ b/msgraph_beta/generated/authentication_method_devices/item/hardware_oath_devices/item/assign_to/assign_to_request_builder.py @@ -33,7 +33,7 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def get(self,request_configuration: Optional[RequestConfiguration[AssignToRequestBuilderGetQueryParameters]] = None) -> Optional[User]: """ - Get assignTo from authenticationMethodDevices + Assign the hardware OATH token to a user. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[User] """ @@ -53,7 +53,7 @@ async def get(self,request_configuration: Optional[RequestConfiguration[AssignTo def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[AssignToRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Get assignTo from authenticationMethodDevices + Assign the hardware OATH token to a user. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -93,7 +93,7 @@ def service_provisioning_errors(self) -> ServiceProvisioningErrorsRequestBuilder @dataclass class AssignToRequestBuilderGetQueryParameters(): """ - Get assignTo from authenticationMethodDevices + Assign the hardware OATH token to a user. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/authentication_method_devices/item/hardware_oath_devices/item/hardware_oath_token_authentication_method_device_item_request_builder.py b/msgraph_beta/generated/authentication_method_devices/item/hardware_oath_devices/item/hardware_oath_token_authentication_method_device_item_request_builder.py index 7e254086c2d..4e0f7c4484e 100644 --- a/msgraph_beta/generated/authentication_method_devices/item/hardware_oath_devices/item/hardware_oath_token_authentication_method_device_item_request_builder.py +++ b/msgraph_beta/generated/authentication_method_devices/item/hardware_oath_devices/item/hardware_oath_token_authentication_method_device_item_request_builder.py @@ -50,7 +50,7 @@ async def delete(self,request_configuration: Optional[RequestConfiguration[Query async def get(self,request_configuration: Optional[RequestConfiguration[HardwareOathTokenAuthenticationMethodDeviceItemRequestBuilderGetQueryParameters]] = None) -> Optional[HardwareOathTokenAuthenticationMethodDevice]: """ - Get hardwareOathDevices from authenticationMethodDevices + Exposes the hardware OATH method in the directory. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[HardwareOathTokenAuthenticationMethodDevice] """ @@ -104,7 +104,7 @@ def to_delete_request_information(self,request_configuration: Optional[RequestCo def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[HardwareOathTokenAuthenticationMethodDeviceItemRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Get hardwareOathDevices from authenticationMethodDevices + Exposes the hardware OATH method in the directory. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -157,7 +157,7 @@ class HardwareOathTokenAuthenticationMethodDeviceItemRequestBuilderDeleteRequest @dataclass class HardwareOathTokenAuthenticationMethodDeviceItemRequestBuilderGetQueryParameters(): """ - Get hardwareOathDevices from authenticationMethodDevices + Exposes the hardware OATH method in the directory. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/communications/calls/item/participants/invite/invite_request_builder.py b/msgraph_beta/generated/communications/calls/item/participants/invite/invite_request_builder.py index 9af001434e9..b0459e52c2e 100644 --- a/msgraph_beta/generated/communications/calls/item/participants/invite/invite_request_builder.py +++ b/msgraph_beta/generated/communications/calls/item/participants/invite/invite_request_builder.py @@ -32,11 +32,11 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def post(self,body: InvitePostRequestBody, request_configuration: Optional[RequestConfiguration[QueryParameters]] = None) -> Optional[InviteParticipantsOperation]: """ - Invite participants to the active call. For more information about how to handle operations, see commsOperation. + Delete a specific participant in a call. In some situations, it is appropriate for an application to remove a participant from an active call. This action can be done before or after the participant answers the call. When an active caller is removed, they are immediately dropped from the call with no pre- or post-removal notification. When an invited participant is removed, any outstanding add participant request is canceled. param body: The request body param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[InviteParticipantsOperation] - Find more info here: https://learn.microsoft.com/graph/api/participant-invite?view=graph-rest-beta + Find more info here: https://learn.microsoft.com/graph/api/participant-delete?view=graph-rest-beta """ if body is None: raise TypeError("body cannot be null.") @@ -56,7 +56,7 @@ async def post(self,body: InvitePostRequestBody, request_configuration: Optional def to_post_request_information(self,body: InvitePostRequestBody, request_configuration: Optional[RequestConfiguration[QueryParameters]] = None) -> RequestInformation: """ - Invite participants to the active call. For more information about how to handle operations, see commsOperation. + Delete a specific participant in a call. In some situations, it is appropriate for an application to remove a participant from an active call. This action can be done before or after the participant answers the call. When an active caller is removed, they are immediately dropped from the call with no pre- or post-removal notification. When an invited participant is removed, any outstanding add participant request is canceled. param body: The request body param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation diff --git a/msgraph_beta/generated/device_management/device_compliance_policies/item/scheduled_actions_for_rule/item/device_compliance_scheduled_action_for_rule_item_request_builder.py b/msgraph_beta/generated/device_management/device_compliance_policies/item/scheduled_actions_for_rule/item/device_compliance_scheduled_action_for_rule_item_request_builder.py index be5db6d5e0b..e434938edcc 100644 --- a/msgraph_beta/generated/device_management/device_compliance_policies/item/scheduled_actions_for_rule/item/device_compliance_scheduled_action_for_rule_item_request_builder.py +++ b/msgraph_beta/generated/device_management/device_compliance_policies/item/scheduled_actions_for_rule/item/device_compliance_scheduled_action_for_rule_item_request_builder.py @@ -50,7 +50,7 @@ async def delete(self,request_configuration: Optional[RequestConfiguration[Query async def get(self,request_configuration: Optional[RequestConfiguration[DeviceComplianceScheduledActionForRuleItemRequestBuilderGetQueryParameters]] = None) -> Optional[DeviceComplianceScheduledActionForRule]: """ - The list of scheduled action for this rule + The list of scheduled action per rule for this compliance policy. This is a required property when creating any individual per-platform compliance policies. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[DeviceComplianceScheduledActionForRule] """ @@ -104,7 +104,7 @@ def to_delete_request_information(self,request_configuration: Optional[RequestCo def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[DeviceComplianceScheduledActionForRuleItemRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - The list of scheduled action for this rule + The list of scheduled action per rule for this compliance policy. This is a required property when creating any individual per-platform compliance policies. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -157,7 +157,7 @@ class DeviceComplianceScheduledActionForRuleItemRequestBuilderDeleteRequestConfi @dataclass class DeviceComplianceScheduledActionForRuleItemRequestBuilderGetQueryParameters(): """ - The list of scheduled action for this rule + The list of scheduled action per rule for this compliance policy. This is a required property when creating any individual per-platform compliance policies. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/device_management/device_compliance_policies/item/scheduled_actions_for_rule/scheduled_actions_for_rule_request_builder.py b/msgraph_beta/generated/device_management/device_compliance_policies/item/scheduled_actions_for_rule/scheduled_actions_for_rule_request_builder.py index 5ee468901c3..c60fd4bed94 100644 --- a/msgraph_beta/generated/device_management/device_compliance_policies/item/scheduled_actions_for_rule/scheduled_actions_for_rule_request_builder.py +++ b/msgraph_beta/generated/device_management/device_compliance_policies/item/scheduled_actions_for_rule/scheduled_actions_for_rule_request_builder.py @@ -48,7 +48,7 @@ def by_device_compliance_scheduled_action_for_rule_id(self,device_compliance_sch async def get(self,request_configuration: Optional[RequestConfiguration[ScheduledActionsForRuleRequestBuilderGetQueryParameters]] = None) -> Optional[DeviceComplianceScheduledActionForRuleCollectionResponse]: """ - The list of scheduled action for this rule + The list of scheduled action per rule for this compliance policy. This is a required property when creating any individual per-platform compliance policies. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[DeviceComplianceScheduledActionForRuleCollectionResponse] """ @@ -91,7 +91,7 @@ async def post(self,body: DeviceComplianceScheduledActionForRule, request_config def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[ScheduledActionsForRuleRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - The list of scheduled action for this rule + The list of scheduled action per rule for this compliance policy. This is a required property when creating any individual per-platform compliance policies. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -137,7 +137,7 @@ def count(self) -> CountRequestBuilder: @dataclass class ScheduledActionsForRuleRequestBuilderGetQueryParameters(): """ - The list of scheduled action for this rule + The list of scheduled action per rule for this compliance policy. This is a required property when creating any individual per-platform compliance policies. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/device_management/virtual_endpoint/cloud_p_cs/item/retrieve_review_status/retrieve_review_status_request_builder.py b/msgraph_beta/generated/device_management/virtual_endpoint/cloud_p_cs/item/retrieve_review_status/retrieve_review_status_request_builder.py index de48842cf07..b001a0dd871 100644 --- a/msgraph_beta/generated/device_management/virtual_endpoint/cloud_p_cs/item/retrieve_review_status/retrieve_review_status_request_builder.py +++ b/msgraph_beta/generated/device_management/virtual_endpoint/cloud_p_cs/item/retrieve_review_status/retrieve_review_status_request_builder.py @@ -31,9 +31,10 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def get(self,request_configuration: Optional[RequestConfiguration[QueryParameters]] = None) -> Optional[CloudPcReviewStatus]: """ - Invoke function retrieveReviewStatus + Get the review status of a Cloud PC. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[CloudPcReviewStatus] + Find more info here: https://learn.microsoft.com/graph/api/cloudpc-retrievereviewstatus?view=graph-rest-beta """ request_info = self.to_get_request_information( request_configuration @@ -51,7 +52,7 @@ async def get(self,request_configuration: Optional[RequestConfiguration[QueryPar def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[QueryParameters]] = None) -> RequestInformation: """ - Invoke function retrieveReviewStatus + Get the review status of a Cloud PC. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ diff --git a/msgraph_beta/generated/device_management/virtual_endpoint/cloud_p_cs/item/retrieve_snapshots/retrieve_snapshots_request_builder.py b/msgraph_beta/generated/device_management/virtual_endpoint/cloud_p_cs/item/retrieve_snapshots/retrieve_snapshots_request_builder.py index 24931ba0273..0965e4298c3 100644 --- a/msgraph_beta/generated/device_management/virtual_endpoint/cloud_p_cs/item/retrieve_snapshots/retrieve_snapshots_request_builder.py +++ b/msgraph_beta/generated/device_management/virtual_endpoint/cloud_p_cs/item/retrieve_snapshots/retrieve_snapshots_request_builder.py @@ -31,9 +31,10 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def get(self,request_configuration: Optional[RequestConfiguration[RetrieveSnapshotsRequestBuilderGetQueryParameters]] = None) -> Optional[RetrieveSnapshotsGetResponse]: """ - Invoke function retrieveSnapshots + List all cloudPcSnapshot resources for a Cloud PC. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[RetrieveSnapshotsGetResponse] + Find more info here: https://learn.microsoft.com/graph/api/cloudpc-retrievesnapshots?view=graph-rest-beta """ request_info = self.to_get_request_information( request_configuration @@ -51,7 +52,7 @@ async def get(self,request_configuration: Optional[RequestConfiguration[Retrieve def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[RetrieveSnapshotsRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Invoke function retrieveSnapshots + List all cloudPcSnapshot resources for a Cloud PC. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -73,7 +74,7 @@ def with_url(self,raw_url: str) -> RetrieveSnapshotsRequestBuilder: @dataclass class RetrieveSnapshotsRequestBuilderGetQueryParameters(): """ - Invoke function retrieveSnapshots + List all cloudPcSnapshot resources for a Cloud PC. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/device_management/virtual_endpoint/cloud_p_cs/item/set_review_status/set_review_status_request_builder.py b/msgraph_beta/generated/device_management/virtual_endpoint/cloud_p_cs/item/set_review_status/set_review_status_request_builder.py index bdcbe7f1837..fcc916b9c30 100644 --- a/msgraph_beta/generated/device_management/virtual_endpoint/cloud_p_cs/item/set_review_status/set_review_status_request_builder.py +++ b/msgraph_beta/generated/device_management/virtual_endpoint/cloud_p_cs/item/set_review_status/set_review_status_request_builder.py @@ -31,10 +31,11 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def post(self,body: SetReviewStatusPostRequestBody, request_configuration: Optional[RequestConfiguration[QueryParameters]] = None) -> None: """ - Invoke action setReviewStatus + Set the review status of a specific Cloud PC device using the Cloud PC ID. Use this API to set the review status of a Cloud PC to in review if you consider a Cloud PC suspicious. After the review is completed, use this API again to set the Cloud PC back to a normal state. param body: The request body param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: None + Find more info here: https://learn.microsoft.com/graph/api/cloudpc-setreviewstatus?view=graph-rest-beta """ if body is None: raise TypeError("body cannot be null.") @@ -52,7 +53,7 @@ async def post(self,body: SetReviewStatusPostRequestBody, request_configuration: def to_post_request_information(self,body: SetReviewStatusPostRequestBody, request_configuration: Optional[RequestConfiguration[QueryParameters]] = None) -> RequestInformation: """ - Invoke action setReviewStatus + Set the review status of a specific Cloud PC device using the Cloud PC ID. Use this API to set the review status of a Cloud PC to in review if you consider a Cloud PC suspicious. After the review is completed, use this API again to set the Cloud PC back to a normal state. param body: The request body param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation diff --git a/msgraph_beta/generated/directory/authentication_method_devices/authentication_method_devices_request_builder.py b/msgraph_beta/generated/directory/authentication_method_devices/authentication_method_devices_request_builder.py index ae4c481016f..1d8c59b789e 100644 --- a/msgraph_beta/generated/directory/authentication_method_devices/authentication_method_devices_request_builder.py +++ b/msgraph_beta/generated/directory/authentication_method_devices/authentication_method_devices_request_builder.py @@ -50,7 +50,7 @@ async def delete(self,request_configuration: Optional[RequestConfiguration[Query async def get(self,request_configuration: Optional[RequestConfiguration[AuthenticationMethodDevicesRequestBuilderGetQueryParameters]] = None) -> Optional[AuthenticationMethodDevice]: """ - Get authenticationMethodDevices from directory + Exposes the hardware OATH method in the directory. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[AuthenticationMethodDevice] """ @@ -104,7 +104,7 @@ def to_delete_request_information(self,request_configuration: Optional[RequestCo def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[AuthenticationMethodDevicesRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Get authenticationMethodDevices from directory + Exposes the hardware OATH method in the directory. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -157,7 +157,7 @@ class AuthenticationMethodDevicesRequestBuilderDeleteRequestConfiguration(Reques @dataclass class AuthenticationMethodDevicesRequestBuilderGetQueryParameters(): """ - Get authenticationMethodDevices from directory + Exposes the hardware OATH method in the directory. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/directory/authentication_method_devices/hardware_oath_devices/hardware_oath_devices_request_builder.py b/msgraph_beta/generated/directory/authentication_method_devices/hardware_oath_devices/hardware_oath_devices_request_builder.py index fcabd2d1948..4a9f1568e4c 100644 --- a/msgraph_beta/generated/directory/authentication_method_devices/hardware_oath_devices/hardware_oath_devices_request_builder.py +++ b/msgraph_beta/generated/directory/authentication_method_devices/hardware_oath_devices/hardware_oath_devices_request_builder.py @@ -48,9 +48,10 @@ def by_hardware_oath_token_authentication_method_device_id(self,hardware_oath_to async def get(self,request_configuration: Optional[RequestConfiguration[HardwareOathDevicesRequestBuilderGetQueryParameters]] = None) -> Optional[HardwareOathTokenAuthenticationMethodDeviceCollectionResponse]: """ - Get hardwareOathDevices from directory + List all hardware OATH tokens in the directory. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[HardwareOathTokenAuthenticationMethodDeviceCollectionResponse] + Find more info here: https://learn.microsoft.com/graph/api/authenticationmethoddevice-list-hardwareoathdevices?view=graph-rest-beta """ request_info = self.to_get_request_information( request_configuration @@ -68,10 +69,11 @@ async def get(self,request_configuration: Optional[RequestConfiguration[Hardware async def post(self,body: HardwareOathTokenAuthenticationMethodDevice, request_configuration: Optional[RequestConfiguration[QueryParameters]] = None) -> Optional[HardwareOathTokenAuthenticationMethodDevice]: """ - Create new navigation property to hardwareOathDevices for directory + Create a new hardwareOathTokenAuthenticationMethodDevice object. Supports bulk creation. param body: The request body param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[HardwareOathTokenAuthenticationMethodDevice] + Find more info here: https://learn.microsoft.com/graph/api/authenticationmethoddevice-update?view=graph-rest-beta """ if body is None: raise TypeError("body cannot be null.") @@ -91,7 +93,7 @@ async def post(self,body: HardwareOathTokenAuthenticationMethodDevice, request_c def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[HardwareOathDevicesRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Get hardwareOathDevices from directory + List all hardware OATH tokens in the directory. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -102,7 +104,7 @@ def to_get_request_information(self,request_configuration: Optional[RequestConfi def to_post_request_information(self,body: HardwareOathTokenAuthenticationMethodDevice, request_configuration: Optional[RequestConfiguration[QueryParameters]] = None) -> RequestInformation: """ - Create new navigation property to hardwareOathDevices for directory + Create a new hardwareOathTokenAuthenticationMethodDevice object. Supports bulk creation. param body: The request body param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation @@ -137,7 +139,7 @@ def count(self) -> CountRequestBuilder: @dataclass class HardwareOathDevicesRequestBuilderGetQueryParameters(): """ - Get hardwareOathDevices from directory + List all hardware OATH tokens in the directory. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/directory/authentication_method_devices/hardware_oath_devices/item/assign_to/assign_to_request_builder.py b/msgraph_beta/generated/directory/authentication_method_devices/hardware_oath_devices/item/assign_to/assign_to_request_builder.py index c81f86dfdd2..30d9957f5de 100644 --- a/msgraph_beta/generated/directory/authentication_method_devices/hardware_oath_devices/item/assign_to/assign_to_request_builder.py +++ b/msgraph_beta/generated/directory/authentication_method_devices/hardware_oath_devices/item/assign_to/assign_to_request_builder.py @@ -33,7 +33,7 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def get(self,request_configuration: Optional[RequestConfiguration[AssignToRequestBuilderGetQueryParameters]] = None) -> Optional[User]: """ - Get assignTo from directory + Assign the hardware OATH token to a user. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[User] """ @@ -53,7 +53,7 @@ async def get(self,request_configuration: Optional[RequestConfiguration[AssignTo def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[AssignToRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Get assignTo from directory + Assign the hardware OATH token to a user. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -93,7 +93,7 @@ def service_provisioning_errors(self) -> ServiceProvisioningErrorsRequestBuilder @dataclass class AssignToRequestBuilderGetQueryParameters(): """ - Get assignTo from directory + Assign the hardware OATH token to a user. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/directory/authentication_method_devices/hardware_oath_devices/item/hardware_oath_token_authentication_method_device_item_request_builder.py b/msgraph_beta/generated/directory/authentication_method_devices/hardware_oath_devices/item/hardware_oath_token_authentication_method_device_item_request_builder.py index 378fcc8cf7c..2a7afac2df3 100644 --- a/msgraph_beta/generated/directory/authentication_method_devices/hardware_oath_devices/item/hardware_oath_token_authentication_method_device_item_request_builder.py +++ b/msgraph_beta/generated/directory/authentication_method_devices/hardware_oath_devices/item/hardware_oath_token_authentication_method_device_item_request_builder.py @@ -32,9 +32,10 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def delete(self,request_configuration: Optional[RequestConfiguration[QueryParameters]] = None) -> None: """ - Delete navigation property hardwareOathDevices for directory + Delete a Hardware OATH token. Token needs to be unassigned. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: None + Find more info here: https://learn.microsoft.com/graph/api/authenticationmethoddevice-delete-hardwareoathdevices?view=graph-rest-beta """ request_info = self.to_delete_request_information( request_configuration @@ -50,9 +51,10 @@ async def delete(self,request_configuration: Optional[RequestConfiguration[Query async def get(self,request_configuration: Optional[RequestConfiguration[HardwareOathTokenAuthenticationMethodDeviceItemRequestBuilderGetQueryParameters]] = None) -> Optional[HardwareOathTokenAuthenticationMethodDevice]: """ - Get hardwareOathDevices from directory + Read the properties and relationships of a hardwareOathTokenAuthenticationMethodDevice object. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[HardwareOathTokenAuthenticationMethodDevice] + Find more info here: https://learn.microsoft.com/graph/api/hardwareoathtokenauthenticationmethoddevice-get?view=graph-rest-beta """ request_info = self.to_get_request_information( request_configuration @@ -70,10 +72,11 @@ async def get(self,request_configuration: Optional[RequestConfiguration[Hardware async def patch(self,body: HardwareOathTokenAuthenticationMethodDevice, request_configuration: Optional[RequestConfiguration[QueryParameters]] = None) -> Optional[HardwareOathTokenAuthenticationMethodDevice]: """ - Update the navigation property hardwareOathDevices in directory + Update the properties of a hardwareOathTokenAuthenticationMethodDevice object. The token needs to unassigned. param body: The request body param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[HardwareOathTokenAuthenticationMethodDevice] + Find more info here: https://learn.microsoft.com/graph/api/hardwareoathtokenauthenticationmethoddevice-update?view=graph-rest-beta """ if body is None: raise TypeError("body cannot be null.") @@ -93,7 +96,7 @@ async def patch(self,body: HardwareOathTokenAuthenticationMethodDevice, request_ def to_delete_request_information(self,request_configuration: Optional[RequestConfiguration[QueryParameters]] = None) -> RequestInformation: """ - Delete navigation property hardwareOathDevices for directory + Delete a Hardware OATH token. Token needs to be unassigned. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -104,7 +107,7 @@ def to_delete_request_information(self,request_configuration: Optional[RequestCo def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[HardwareOathTokenAuthenticationMethodDeviceItemRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Get hardwareOathDevices from directory + Read the properties and relationships of a hardwareOathTokenAuthenticationMethodDevice object. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -115,7 +118,7 @@ def to_get_request_information(self,request_configuration: Optional[RequestConfi def to_patch_request_information(self,body: HardwareOathTokenAuthenticationMethodDevice, request_configuration: Optional[RequestConfiguration[QueryParameters]] = None) -> RequestInformation: """ - Update the navigation property hardwareOathDevices in directory + Update the properties of a hardwareOathTokenAuthenticationMethodDevice object. The token needs to unassigned. param body: The request body param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation @@ -157,7 +160,7 @@ class HardwareOathTokenAuthenticationMethodDeviceItemRequestBuilderDeleteRequest @dataclass class HardwareOathTokenAuthenticationMethodDeviceItemRequestBuilderGetQueryParameters(): """ - Get hardwareOathDevices from directory + Read the properties and relationships of a hardwareOathTokenAuthenticationMethodDevice object. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/drives/item/items/item/workbook/tables/add/add_request_builder.py b/msgraph_beta/generated/drives/item/items/item/workbook/tables/add/add_request_builder.py index d001a0e8cb8..0125786e2a8 100644 --- a/msgraph_beta/generated/drives/item/items/item/workbook/tables/add/add_request_builder.py +++ b/msgraph_beta/generated/drives/item/items/item/workbook/tables/add/add_request_builder.py @@ -32,11 +32,11 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def post(self,body: AddPostRequestBody, request_configuration: Optional[RequestConfiguration[QueryParameters]] = None) -> Optional[WorkbookTable]: """ - Create a new table. The range source address determines the worksheet under which the table will be added. If the table can't be added (for example, because the address is invalid, or the table would overlap with another table), an error is thrown. + Use this API to create a new Table. param body: The request body param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[WorkbookTable] - Find more info here: https://learn.microsoft.com/graph/api/tablecollection-add?view=graph-rest-beta + Find more info here: https://learn.microsoft.com/graph/api/workbook-post-tables?view=graph-rest-beta """ if body is None: raise TypeError("body cannot be null.") @@ -56,7 +56,7 @@ async def post(self,body: AddPostRequestBody, request_configuration: Optional[Re def to_post_request_information(self,body: AddPostRequestBody, request_configuration: Optional[RequestConfiguration[QueryParameters]] = None) -> RequestInformation: """ - Create a new table. The range source address determines the worksheet under which the table will be added. If the table can't be added (for example, because the address is invalid, or the table would overlap with another table), an error is thrown. + Use this API to create a new Table. param body: The request body param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation diff --git a/msgraph_beta/generated/drives/item/items/item/workbook/worksheets/item/tables/add/add_request_builder.py b/msgraph_beta/generated/drives/item/items/item/workbook/worksheets/item/tables/add/add_request_builder.py index 0a8f5398942..e446055ee0a 100644 --- a/msgraph_beta/generated/drives/item/items/item/workbook/worksheets/item/tables/add/add_request_builder.py +++ b/msgraph_beta/generated/drives/item/items/item/workbook/worksheets/item/tables/add/add_request_builder.py @@ -32,11 +32,11 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def post(self,body: AddPostRequestBody, request_configuration: Optional[RequestConfiguration[QueryParameters]] = None) -> Optional[WorkbookTable]: """ - Create a new table. The range source address determines the worksheet under which the table will be added. If the table can't be added (for example, because the address is invalid, or the table would overlap with another table), an error is thrown. + Use this API to create a new Table. param body: The request body param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[WorkbookTable] - Find more info here: https://learn.microsoft.com/graph/api/tablecollection-add?view=graph-rest-beta + Find more info here: https://learn.microsoft.com/graph/api/workbook-post-tables?view=graph-rest-beta """ if body is None: raise TypeError("body cannot be null.") @@ -56,7 +56,7 @@ async def post(self,body: AddPostRequestBody, request_configuration: Optional[Re def to_post_request_information(self,body: AddPostRequestBody, request_configuration: Optional[RequestConfiguration[QueryParameters]] = None) -> RequestInformation: """ - Create a new table. The range source address determines the worksheet under which the table will be added. If the table can't be added (for example, because the address is invalid, or the table would overlap with another table), an error is thrown. + Use this API to create a new Table. param body: The request body param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation diff --git a/msgraph_beta/generated/external/authorization_systems/item/authorization_system_item_request_builder.py b/msgraph_beta/generated/external/authorization_systems/item/authorization_system_item_request_builder.py index ee1cdb391f9..3f7101a175f 100644 --- a/msgraph_beta/generated/external/authorization_systems/item/authorization_system_item_request_builder.py +++ b/msgraph_beta/generated/external/authorization_systems/item/authorization_system_item_request_builder.py @@ -50,7 +50,7 @@ async def delete(self,request_configuration: Optional[RequestConfiguration[Query async def get(self,request_configuration: Optional[RequestConfiguration[AuthorizationSystemItemRequestBuilderGetQueryParameters]] = None) -> Optional[AuthorizationSystem]: """ - Represents an onboarded AWS account, Azure subscription, or GCP project that Microsoft Entra Permissions Management will collect and analyze permissions and actions on. + Represents an onboarded Amazon Web Services (AWS) account, Azure subscription, or Google Cloud Platform (GCP) project that Microsoft Entra Permissions Management collects and analyzes permissions and actions on. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[AuthorizationSystem] """ @@ -104,7 +104,7 @@ def to_delete_request_information(self,request_configuration: Optional[RequestCo def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[AuthorizationSystemItemRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Represents an onboarded AWS account, Azure subscription, or GCP project that Microsoft Entra Permissions Management will collect and analyze permissions and actions on. + Represents an onboarded Amazon Web Services (AWS) account, Azure subscription, or Google Cloud Platform (GCP) project that Microsoft Entra Permissions Management collects and analyzes permissions and actions on. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -157,7 +157,7 @@ class AuthorizationSystemItemRequestBuilderDeleteRequestConfiguration(RequestCon @dataclass class AuthorizationSystemItemRequestBuilderGetQueryParameters(): """ - Represents an onboarded AWS account, Azure subscription, or GCP project that Microsoft Entra Permissions Management will collect and analyze permissions and actions on. + Represents an onboarded Amazon Web Services (AWS) account, Azure subscription, or Google Cloud Platform (GCP) project that Microsoft Entra Permissions Management collects and analyzes permissions and actions on. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/external/connections/item/schema/schema_request_builder.py b/msgraph_beta/generated/external/connections/item/schema/schema_request_builder.py index fcfe12ed7eb..b0647e46850 100644 --- a/msgraph_beta/generated/external/connections/item/schema/schema_request_builder.py +++ b/msgraph_beta/generated/external/connections/item/schema/schema_request_builder.py @@ -52,11 +52,11 @@ async def get(self,request_configuration: Optional[RequestConfiguration[SchemaRe async def patch(self,body: Schema, request_configuration: Optional[RequestConfiguration[QueryParameters]] = None) -> Optional[Schema]: """ - Create a new or update an existing schema for a Microsoft Search connection. + Update the properties of a schema for an externalConnection. param body: The request body param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[Schema] - Find more info here: https://learn.microsoft.com/graph/api/externalconnectors-externalconnection-patch-schema?view=graph-rest-beta + Find more info here: https://learn.microsoft.com/graph/api/externalconnectors-schema-update?view=graph-rest-beta """ if body is None: raise TypeError("body cannot be null.") @@ -87,7 +87,7 @@ def to_get_request_information(self,request_configuration: Optional[RequestConfi def to_patch_request_information(self,body: Schema, request_configuration: Optional[RequestConfiguration[QueryParameters]] = None) -> RequestInformation: """ - Create a new or update an existing schema for a Microsoft Search connection. + Update the properties of a schema for an externalConnection. param body: The request body param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation diff --git a/msgraph_beta/generated/external/industry_data/data_connectors/data_connectors_request_builder.py b/msgraph_beta/generated/external/industry_data/data_connectors/data_connectors_request_builder.py index df6a77535d4..8a3a06ee981 100644 --- a/msgraph_beta/generated/external/industry_data/data_connectors/data_connectors_request_builder.py +++ b/msgraph_beta/generated/external/industry_data/data_connectors/data_connectors_request_builder.py @@ -69,11 +69,11 @@ async def get(self,request_configuration: Optional[RequestConfiguration[DataConn async def post(self,body: IndustryDataConnector, request_configuration: Optional[RequestConfiguration[QueryParameters]] = None) -> Optional[IndustryDataConnector]: """ - Create a new azureDataLakeConnector object. + Create a new oneRosterApiDataConnector object. param body: The request body param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[IndustryDataConnector] - Find more info here: https://learn.microsoft.com/graph/api/industrydata-azuredatalakeconnector-post?view=graph-rest-beta + Find more info here: https://learn.microsoft.com/graph/api/industrydata-onerosterapidataconnector-post?view=graph-rest-beta """ if body is None: raise TypeError("body cannot be null.") @@ -104,7 +104,7 @@ def to_get_request_information(self,request_configuration: Optional[RequestConfi def to_post_request_information(self,body: IndustryDataConnector, request_configuration: Optional[RequestConfiguration[QueryParameters]] = None) -> RequestInformation: """ - Create a new azureDataLakeConnector object. + Create a new oneRosterApiDataConnector object. param body: The request body param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation diff --git a/msgraph_beta/generated/external/industry_data/inbound_flows/inbound_flows_request_builder.py b/msgraph_beta/generated/external/industry_data/inbound_flows/inbound_flows_request_builder.py index 84a40af2d25..5c182ec7fb6 100644 --- a/msgraph_beta/generated/external/industry_data/inbound_flows/inbound_flows_request_builder.py +++ b/msgraph_beta/generated/external/industry_data/inbound_flows/inbound_flows_request_builder.py @@ -69,11 +69,11 @@ async def get(self,request_configuration: Optional[RequestConfiguration[InboundF async def post(self,body: InboundFlow, request_configuration: Optional[RequestConfiguration[QueryParameters]] = None) -> Optional[InboundFlow]: """ - Create a new inboundFileFlow object. + Create a new inboundApiFlow object. param body: The request body param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[InboundFlow] - Find more info here: https://learn.microsoft.com/graph/api/industrydata-inboundfileflow-post?view=graph-rest-beta + Find more info here: https://learn.microsoft.com/graph/api/industrydata-inboundapiflow-post?view=graph-rest-beta """ if body is None: raise TypeError("body cannot be null.") @@ -104,7 +104,7 @@ def to_get_request_information(self,request_configuration: Optional[RequestConfi def to_post_request_information(self,body: InboundFlow, request_configuration: Optional[RequestConfiguration[QueryParameters]] = None) -> RequestInformation: """ - Create a new inboundFileFlow object. + Create a new inboundApiFlow object. param body: The request body param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation diff --git a/msgraph_beta/generated/groups/groups_request_builder.py b/msgraph_beta/generated/groups/groups_request_builder.py index a9dc6f7172e..efefdd32524 100644 --- a/msgraph_beta/generated/groups/groups_request_builder.py +++ b/msgraph_beta/generated/groups/groups_request_builder.py @@ -74,11 +74,11 @@ async def get(self,request_configuration: Optional[RequestConfiguration[GroupsRe async def post(self,body: Group, request_configuration: Optional[RequestConfiguration[QueryParameters]] = None) -> Optional[Group]: """ - Create a new group object if it doesn't exist, or update the properties of an existing group object.You can create or update the following types of group: By default, this operation returns only a subset of the properties for each group. For a list of properties that are returned by default, see the Properties section of the group resource. To get properties that are not returned by default, do a GET operation and specify the properties in a $select OData query option. + Create a new group as specified in the request body. You can create one of the following groups: This operation returns by default only a subset of the properties for each group. These default properties are noted in the Properties section. To get properties that are not returned by default, do a GET operation and specify the properties in a $select OData query option. Note: To create a team, first create a group then add a team to it, see create team. param body: The request body param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[Group] - Find more info here: https://learn.microsoft.com/graph/api/group-upsert?view=graph-rest-beta + Find more info here: https://learn.microsoft.com/graph/api/group-post-groups?view=graph-rest-beta """ if body is None: raise TypeError("body cannot be null.") @@ -109,7 +109,7 @@ def to_get_request_information(self,request_configuration: Optional[RequestConfi def to_post_request_information(self,body: Group, request_configuration: Optional[RequestConfiguration[QueryParameters]] = None) -> RequestInformation: """ - Create a new group object if it doesn't exist, or update the properties of an existing group object.You can create or update the following types of group: By default, this operation returns only a subset of the properties for each group. For a list of properties that are returned by default, see the Properties section of the group resource. To get properties that are not returned by default, do a GET operation and specify the properties in a $select OData query option. + Create a new group as specified in the request body. You can create one of the following groups: This operation returns by default only a subset of the properties for each group. These default properties are noted in the Properties section. To get properties that are not returned by default, do a GET operation and specify the properties in a $select OData query option. Note: To create a team, first create a group then add a team to it, see create team. param body: The request body param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation diff --git a/msgraph_beta/generated/groups/item/calendar/calendar_view/delta/delta_request_builder.py b/msgraph_beta/generated/groups/item/calendar/calendar_view/delta/delta_request_builder.py index 0fe2f6c5f96..cf33beeb687 100644 --- a/msgraph_beta/generated/groups/item/calendar/calendar_view/delta/delta_request_builder.py +++ b/msgraph_beta/generated/groups/item/calendar/calendar_view/delta/delta_request_builder.py @@ -31,7 +31,7 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def get(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> Optional[DeltaGetResponse]: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[DeltaGetResponse] Find more info here: https://learn.microsoft.com/graph/api/event-delta?view=graph-rest-beta @@ -52,7 +52,7 @@ async def get(self,request_configuration: Optional[RequestConfiguration[DeltaReq def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -74,7 +74,7 @@ def with_url(self,raw_url: str) -> DeltaRequestBuilder: @dataclass class DeltaRequestBuilderGetQueryParameters(): """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/groups/item/calendar/calendar_view/item/exception_occurrences/delta/delta_request_builder.py b/msgraph_beta/generated/groups/item/calendar/calendar_view/item/exception_occurrences/delta/delta_request_builder.py index 0ac6ba3a1af..fb9da850aa2 100644 --- a/msgraph_beta/generated/groups/item/calendar/calendar_view/item/exception_occurrences/delta/delta_request_builder.py +++ b/msgraph_beta/generated/groups/item/calendar/calendar_view/item/exception_occurrences/delta/delta_request_builder.py @@ -31,7 +31,7 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def get(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> Optional[DeltaGetResponse]: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[DeltaGetResponse] Find more info here: https://learn.microsoft.com/graph/api/event-delta?view=graph-rest-beta @@ -52,7 +52,7 @@ async def get(self,request_configuration: Optional[RequestConfiguration[DeltaReq def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -74,7 +74,7 @@ def with_url(self,raw_url: str) -> DeltaRequestBuilder: @dataclass class DeltaRequestBuilderGetQueryParameters(): """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/groups/item/calendar/calendar_view/item/exception_occurrences/item/instances/delta/delta_request_builder.py b/msgraph_beta/generated/groups/item/calendar/calendar_view/item/exception_occurrences/item/instances/delta/delta_request_builder.py index 275cbceed86..deedc9075ea 100644 --- a/msgraph_beta/generated/groups/item/calendar/calendar_view/item/exception_occurrences/item/instances/delta/delta_request_builder.py +++ b/msgraph_beta/generated/groups/item/calendar/calendar_view/item/exception_occurrences/item/instances/delta/delta_request_builder.py @@ -31,7 +31,7 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def get(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> Optional[DeltaGetResponse]: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[DeltaGetResponse] Find more info here: https://learn.microsoft.com/graph/api/event-delta?view=graph-rest-beta @@ -52,7 +52,7 @@ async def get(self,request_configuration: Optional[RequestConfiguration[DeltaReq def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -74,7 +74,7 @@ def with_url(self,raw_url: str) -> DeltaRequestBuilder: @dataclass class DeltaRequestBuilderGetQueryParameters(): """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/groups/item/calendar/calendar_view/item/instances/delta/delta_request_builder.py b/msgraph_beta/generated/groups/item/calendar/calendar_view/item/instances/delta/delta_request_builder.py index 63e4a70cf4f..6ed7bb81a69 100644 --- a/msgraph_beta/generated/groups/item/calendar/calendar_view/item/instances/delta/delta_request_builder.py +++ b/msgraph_beta/generated/groups/item/calendar/calendar_view/item/instances/delta/delta_request_builder.py @@ -31,7 +31,7 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def get(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> Optional[DeltaGetResponse]: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[DeltaGetResponse] Find more info here: https://learn.microsoft.com/graph/api/event-delta?view=graph-rest-beta @@ -52,7 +52,7 @@ async def get(self,request_configuration: Optional[RequestConfiguration[DeltaReq def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -74,7 +74,7 @@ def with_url(self,raw_url: str) -> DeltaRequestBuilder: @dataclass class DeltaRequestBuilderGetQueryParameters(): """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/groups/item/calendar/calendar_view/item/instances/item/exception_occurrences/delta/delta_request_builder.py b/msgraph_beta/generated/groups/item/calendar/calendar_view/item/instances/item/exception_occurrences/delta/delta_request_builder.py index 74419bbb416..a6517e00697 100644 --- a/msgraph_beta/generated/groups/item/calendar/calendar_view/item/instances/item/exception_occurrences/delta/delta_request_builder.py +++ b/msgraph_beta/generated/groups/item/calendar/calendar_view/item/instances/item/exception_occurrences/delta/delta_request_builder.py @@ -31,7 +31,7 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def get(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> Optional[DeltaGetResponse]: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[DeltaGetResponse] Find more info here: https://learn.microsoft.com/graph/api/event-delta?view=graph-rest-beta @@ -52,7 +52,7 @@ async def get(self,request_configuration: Optional[RequestConfiguration[DeltaReq def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -74,7 +74,7 @@ def with_url(self,raw_url: str) -> DeltaRequestBuilder: @dataclass class DeltaRequestBuilderGetQueryParameters(): """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/groups/item/calendar/events/delta/delta_request_builder.py b/msgraph_beta/generated/groups/item/calendar/events/delta/delta_request_builder.py index ac1e9b94853..7dcf54c3186 100644 --- a/msgraph_beta/generated/groups/item/calendar/events/delta/delta_request_builder.py +++ b/msgraph_beta/generated/groups/item/calendar/events/delta/delta_request_builder.py @@ -31,7 +31,7 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def get(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> Optional[DeltaGetResponse]: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[DeltaGetResponse] Find more info here: https://learn.microsoft.com/graph/api/event-delta?view=graph-rest-beta @@ -52,7 +52,7 @@ async def get(self,request_configuration: Optional[RequestConfiguration[DeltaReq def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -74,7 +74,7 @@ def with_url(self,raw_url: str) -> DeltaRequestBuilder: @dataclass class DeltaRequestBuilderGetQueryParameters(): """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/groups/item/calendar/events/item/exception_occurrences/delta/delta_request_builder.py b/msgraph_beta/generated/groups/item/calendar/events/item/exception_occurrences/delta/delta_request_builder.py index 801110caac5..7c0c91018c1 100644 --- a/msgraph_beta/generated/groups/item/calendar/events/item/exception_occurrences/delta/delta_request_builder.py +++ b/msgraph_beta/generated/groups/item/calendar/events/item/exception_occurrences/delta/delta_request_builder.py @@ -31,7 +31,7 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def get(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> Optional[DeltaGetResponse]: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[DeltaGetResponse] Find more info here: https://learn.microsoft.com/graph/api/event-delta?view=graph-rest-beta @@ -52,7 +52,7 @@ async def get(self,request_configuration: Optional[RequestConfiguration[DeltaReq def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -74,7 +74,7 @@ def with_url(self,raw_url: str) -> DeltaRequestBuilder: @dataclass class DeltaRequestBuilderGetQueryParameters(): """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/groups/item/calendar/events/item/exception_occurrences/item/instances/delta/delta_request_builder.py b/msgraph_beta/generated/groups/item/calendar/events/item/exception_occurrences/item/instances/delta/delta_request_builder.py index 928ebbc4d97..e6941e03eaa 100644 --- a/msgraph_beta/generated/groups/item/calendar/events/item/exception_occurrences/item/instances/delta/delta_request_builder.py +++ b/msgraph_beta/generated/groups/item/calendar/events/item/exception_occurrences/item/instances/delta/delta_request_builder.py @@ -31,7 +31,7 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def get(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> Optional[DeltaGetResponse]: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[DeltaGetResponse] Find more info here: https://learn.microsoft.com/graph/api/event-delta?view=graph-rest-beta @@ -52,7 +52,7 @@ async def get(self,request_configuration: Optional[RequestConfiguration[DeltaReq def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -74,7 +74,7 @@ def with_url(self,raw_url: str) -> DeltaRequestBuilder: @dataclass class DeltaRequestBuilderGetQueryParameters(): """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/groups/item/calendar/events/item/instances/delta/delta_request_builder.py b/msgraph_beta/generated/groups/item/calendar/events/item/instances/delta/delta_request_builder.py index 668f3d711a2..f308d9d0d81 100644 --- a/msgraph_beta/generated/groups/item/calendar/events/item/instances/delta/delta_request_builder.py +++ b/msgraph_beta/generated/groups/item/calendar/events/item/instances/delta/delta_request_builder.py @@ -31,7 +31,7 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def get(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> Optional[DeltaGetResponse]: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[DeltaGetResponse] Find more info here: https://learn.microsoft.com/graph/api/event-delta?view=graph-rest-beta @@ -52,7 +52,7 @@ async def get(self,request_configuration: Optional[RequestConfiguration[DeltaReq def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -74,7 +74,7 @@ def with_url(self,raw_url: str) -> DeltaRequestBuilder: @dataclass class DeltaRequestBuilderGetQueryParameters(): """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/groups/item/calendar/events/item/instances/item/exception_occurrences/delta/delta_request_builder.py b/msgraph_beta/generated/groups/item/calendar/events/item/instances/item/exception_occurrences/delta/delta_request_builder.py index dc22f682021..09908c77c3a 100644 --- a/msgraph_beta/generated/groups/item/calendar/events/item/instances/item/exception_occurrences/delta/delta_request_builder.py +++ b/msgraph_beta/generated/groups/item/calendar/events/item/instances/item/exception_occurrences/delta/delta_request_builder.py @@ -31,7 +31,7 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def get(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> Optional[DeltaGetResponse]: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[DeltaGetResponse] Find more info here: https://learn.microsoft.com/graph/api/event-delta?view=graph-rest-beta @@ -52,7 +52,7 @@ async def get(self,request_configuration: Optional[RequestConfiguration[DeltaReq def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -74,7 +74,7 @@ def with_url(self,raw_url: str) -> DeltaRequestBuilder: @dataclass class DeltaRequestBuilderGetQueryParameters(): """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/groups/item/calendar_view/delta/delta_request_builder.py b/msgraph_beta/generated/groups/item/calendar_view/delta/delta_request_builder.py index cd0fe121fe8..8902416b6bd 100644 --- a/msgraph_beta/generated/groups/item/calendar_view/delta/delta_request_builder.py +++ b/msgraph_beta/generated/groups/item/calendar_view/delta/delta_request_builder.py @@ -31,7 +31,7 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def get(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> Optional[DeltaGetResponse]: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[DeltaGetResponse] Find more info here: https://learn.microsoft.com/graph/api/event-delta?view=graph-rest-beta @@ -52,7 +52,7 @@ async def get(self,request_configuration: Optional[RequestConfiguration[DeltaReq def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -74,7 +74,7 @@ def with_url(self,raw_url: str) -> DeltaRequestBuilder: @dataclass class DeltaRequestBuilderGetQueryParameters(): """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/groups/item/calendar_view/item/exception_occurrences/delta/delta_request_builder.py b/msgraph_beta/generated/groups/item/calendar_view/item/exception_occurrences/delta/delta_request_builder.py index 948ae1edaf3..1d64db9a826 100644 --- a/msgraph_beta/generated/groups/item/calendar_view/item/exception_occurrences/delta/delta_request_builder.py +++ b/msgraph_beta/generated/groups/item/calendar_view/item/exception_occurrences/delta/delta_request_builder.py @@ -31,7 +31,7 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def get(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> Optional[DeltaGetResponse]: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[DeltaGetResponse] Find more info here: https://learn.microsoft.com/graph/api/event-delta?view=graph-rest-beta @@ -52,7 +52,7 @@ async def get(self,request_configuration: Optional[RequestConfiguration[DeltaReq def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -74,7 +74,7 @@ def with_url(self,raw_url: str) -> DeltaRequestBuilder: @dataclass class DeltaRequestBuilderGetQueryParameters(): """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/groups/item/calendar_view/item/exception_occurrences/item/instances/delta/delta_request_builder.py b/msgraph_beta/generated/groups/item/calendar_view/item/exception_occurrences/item/instances/delta/delta_request_builder.py index 67bec167aad..cb3321bda36 100644 --- a/msgraph_beta/generated/groups/item/calendar_view/item/exception_occurrences/item/instances/delta/delta_request_builder.py +++ b/msgraph_beta/generated/groups/item/calendar_view/item/exception_occurrences/item/instances/delta/delta_request_builder.py @@ -31,7 +31,7 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def get(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> Optional[DeltaGetResponse]: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[DeltaGetResponse] Find more info here: https://learn.microsoft.com/graph/api/event-delta?view=graph-rest-beta @@ -52,7 +52,7 @@ async def get(self,request_configuration: Optional[RequestConfiguration[DeltaReq def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -74,7 +74,7 @@ def with_url(self,raw_url: str) -> DeltaRequestBuilder: @dataclass class DeltaRequestBuilderGetQueryParameters(): """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/groups/item/calendar_view/item/instances/delta/delta_request_builder.py b/msgraph_beta/generated/groups/item/calendar_view/item/instances/delta/delta_request_builder.py index 1bac53d0b11..d921b5b2b9c 100644 --- a/msgraph_beta/generated/groups/item/calendar_view/item/instances/delta/delta_request_builder.py +++ b/msgraph_beta/generated/groups/item/calendar_view/item/instances/delta/delta_request_builder.py @@ -31,7 +31,7 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def get(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> Optional[DeltaGetResponse]: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[DeltaGetResponse] Find more info here: https://learn.microsoft.com/graph/api/event-delta?view=graph-rest-beta @@ -52,7 +52,7 @@ async def get(self,request_configuration: Optional[RequestConfiguration[DeltaReq def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -74,7 +74,7 @@ def with_url(self,raw_url: str) -> DeltaRequestBuilder: @dataclass class DeltaRequestBuilderGetQueryParameters(): """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/groups/item/calendar_view/item/instances/item/exception_occurrences/delta/delta_request_builder.py b/msgraph_beta/generated/groups/item/calendar_view/item/instances/item/exception_occurrences/delta/delta_request_builder.py index 9cb9178dbd2..6dbc1e69a15 100644 --- a/msgraph_beta/generated/groups/item/calendar_view/item/instances/item/exception_occurrences/delta/delta_request_builder.py +++ b/msgraph_beta/generated/groups/item/calendar_view/item/instances/item/exception_occurrences/delta/delta_request_builder.py @@ -31,7 +31,7 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def get(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> Optional[DeltaGetResponse]: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[DeltaGetResponse] Find more info here: https://learn.microsoft.com/graph/api/event-delta?view=graph-rest-beta @@ -52,7 +52,7 @@ async def get(self,request_configuration: Optional[RequestConfiguration[DeltaReq def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -74,7 +74,7 @@ def with_url(self,raw_url: str) -> DeltaRequestBuilder: @dataclass class DeltaRequestBuilderGetQueryParameters(): """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/groups/item/conversations/conversations_request_builder.py b/msgraph_beta/generated/groups/item/conversations/conversations_request_builder.py index 26074af74ca..f37bccb374b 100644 --- a/msgraph_beta/generated/groups/item/conversations/conversations_request_builder.py +++ b/msgraph_beta/generated/groups/item/conversations/conversations_request_builder.py @@ -69,11 +69,11 @@ async def get(self,request_configuration: Optional[RequestConfiguration[Conversa async def post(self,body: Conversation, request_configuration: Optional[RequestConfiguration[QueryParameters]] = None) -> Optional[Conversation]: """ - Create a new conversation by including a thread and a post. Use reply thread or reply post to further post to that conversation. + Create an open extension (openTypeExtension object) and add custom properties in a new or existing instance of a resource. You can create an open extension in a resource instance and store custom data to it all in the same operation, except for specific resources. The table in the Permissions section lists the resources that support open extensions. param body: The request body param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[Conversation] - Find more info here: https://learn.microsoft.com/graph/api/group-post-conversations?view=graph-rest-beta + Find more info here: https://learn.microsoft.com/graph/api/opentypeextension-post-opentypeextension?view=graph-rest-beta """ if body is None: raise TypeError("body cannot be null.") @@ -104,7 +104,7 @@ def to_get_request_information(self,request_configuration: Optional[RequestConfi def to_post_request_information(self,body: Conversation, request_configuration: Optional[RequestConfiguration[QueryParameters]] = None) -> RequestInformation: """ - Create a new conversation by including a thread and a post. Use reply thread or reply post to further post to that conversation. + Create an open extension (openTypeExtension object) and add custom properties in a new or existing instance of a resource. You can create an open extension in a resource instance and store custom data to it all in the same operation, except for specific resources. The table in the Permissions section lists the resources that support open extensions. param body: The request body param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation diff --git a/msgraph_beta/generated/groups/item/conversations/item/conversation_item_request_builder.py b/msgraph_beta/generated/groups/item/conversations/item/conversation_item_request_builder.py index f9d2d8893b2..62cdaf43625 100644 --- a/msgraph_beta/generated/groups/item/conversations/item/conversation_item_request_builder.py +++ b/msgraph_beta/generated/groups/item/conversations/item/conversation_item_request_builder.py @@ -32,10 +32,10 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def delete(self,request_configuration: Optional[RequestConfiguration[QueryParameters]] = None) -> None: """ - Delete conversation. + Delete a group's conversation object. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: None - Find more info here: https://learn.microsoft.com/graph/api/conversation-delete?view=graph-rest-beta + Find more info here: https://learn.microsoft.com/graph/api/group-delete-conversation?view=graph-rest-beta """ request_info = self.to_delete_request_information( request_configuration @@ -51,10 +51,10 @@ async def delete(self,request_configuration: Optional[RequestConfiguration[Query async def get(self,request_configuration: Optional[RequestConfiguration[ConversationItemRequestBuilderGetQueryParameters]] = None) -> Optional[Conversation]: """ - Retrieve the properties and relationships of conversation object. + Get a group's conversation object. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[Conversation] - Find more info here: https://learn.microsoft.com/graph/api/conversation-get?view=graph-rest-beta + Find more info here: https://learn.microsoft.com/graph/api/group-get-conversation?view=graph-rest-beta """ request_info = self.to_get_request_information( request_configuration @@ -72,7 +72,7 @@ async def get(self,request_configuration: Optional[RequestConfiguration[Conversa def to_delete_request_information(self,request_configuration: Optional[RequestConfiguration[QueryParameters]] = None) -> RequestInformation: """ - Delete conversation. + Delete a group's conversation object. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -83,7 +83,7 @@ def to_delete_request_information(self,request_configuration: Optional[RequestCo def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[ConversationItemRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Retrieve the properties and relationships of conversation object. + Get a group's conversation object. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -121,7 +121,7 @@ class ConversationItemRequestBuilderDeleteRequestConfiguration(RequestConfigurat @dataclass class ConversationItemRequestBuilderGetQueryParameters(): """ - Retrieve the properties and relationships of conversation object. + Get a group's conversation object. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/groups/item/conversations/item/threads/item/reply/reply_request_builder.py b/msgraph_beta/generated/groups/item/conversations/item/threads/item/reply/reply_request_builder.py index 9b180f75026..1ffc0b08cbe 100644 --- a/msgraph_beta/generated/groups/item/conversations/item/threads/item/reply/reply_request_builder.py +++ b/msgraph_beta/generated/groups/item/conversations/item/threads/item/reply/reply_request_builder.py @@ -31,11 +31,11 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def post(self,body: ReplyPostRequestBody, request_configuration: Optional[RequestConfiguration[QueryParameters]] = None) -> None: """ - Create an open extension (openTypeExtension object) and add custom properties in a new or existing instance of a resource. You can create an open extension in a resource instance and store custom data to it all in the same operation, except for specific resources. The table in the Permissions section lists the resources that support open extensions. + Reply to a post and add a new post to the specified thread in a group conversation. You can specify both the parent conversation and thread in the request, or, you can specify just the parent thread without the parent conversation. param body: The request body param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: None - Find more info here: https://learn.microsoft.com/graph/api/opentypeextension-post-opentypeextension?view=graph-rest-beta + Find more info here: https://learn.microsoft.com/graph/api/post-reply?view=graph-rest-beta """ if body is None: raise TypeError("body cannot be null.") @@ -53,7 +53,7 @@ async def post(self,body: ReplyPostRequestBody, request_configuration: Optional[ def to_post_request_information(self,body: ReplyPostRequestBody, request_configuration: Optional[RequestConfiguration[QueryParameters]] = None) -> RequestInformation: """ - Create an open extension (openTypeExtension object) and add custom properties in a new or existing instance of a resource. You can create an open extension in a resource instance and store custom data to it all in the same operation, except for specific resources. The table in the Permissions section lists the resources that support open extensions. + Reply to a post and add a new post to the specified thread in a group conversation. You can specify both the parent conversation and thread in the request, or, you can specify just the parent thread without the parent conversation. param body: The request body param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation diff --git a/msgraph_beta/generated/groups/item/events/delta/delta_request_builder.py b/msgraph_beta/generated/groups/item/events/delta/delta_request_builder.py index 1c23f76b232..7c26396ea41 100644 --- a/msgraph_beta/generated/groups/item/events/delta/delta_request_builder.py +++ b/msgraph_beta/generated/groups/item/events/delta/delta_request_builder.py @@ -31,7 +31,7 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def get(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> Optional[DeltaGetResponse]: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[DeltaGetResponse] Find more info here: https://learn.microsoft.com/graph/api/event-delta?view=graph-rest-beta @@ -52,7 +52,7 @@ async def get(self,request_configuration: Optional[RequestConfiguration[DeltaReq def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -74,7 +74,7 @@ def with_url(self,raw_url: str) -> DeltaRequestBuilder: @dataclass class DeltaRequestBuilderGetQueryParameters(): """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/groups/item/events/item/exception_occurrences/delta/delta_request_builder.py b/msgraph_beta/generated/groups/item/events/item/exception_occurrences/delta/delta_request_builder.py index dc5d1d398e5..4584c9fe51f 100644 --- a/msgraph_beta/generated/groups/item/events/item/exception_occurrences/delta/delta_request_builder.py +++ b/msgraph_beta/generated/groups/item/events/item/exception_occurrences/delta/delta_request_builder.py @@ -31,7 +31,7 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def get(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> Optional[DeltaGetResponse]: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[DeltaGetResponse] Find more info here: https://learn.microsoft.com/graph/api/event-delta?view=graph-rest-beta @@ -52,7 +52,7 @@ async def get(self,request_configuration: Optional[RequestConfiguration[DeltaReq def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -74,7 +74,7 @@ def with_url(self,raw_url: str) -> DeltaRequestBuilder: @dataclass class DeltaRequestBuilderGetQueryParameters(): """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/groups/item/events/item/exception_occurrences/item/instances/delta/delta_request_builder.py b/msgraph_beta/generated/groups/item/events/item/exception_occurrences/item/instances/delta/delta_request_builder.py index 9ee4593639b..1ef178dcd53 100644 --- a/msgraph_beta/generated/groups/item/events/item/exception_occurrences/item/instances/delta/delta_request_builder.py +++ b/msgraph_beta/generated/groups/item/events/item/exception_occurrences/item/instances/delta/delta_request_builder.py @@ -31,7 +31,7 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def get(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> Optional[DeltaGetResponse]: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[DeltaGetResponse] Find more info here: https://learn.microsoft.com/graph/api/event-delta?view=graph-rest-beta @@ -52,7 +52,7 @@ async def get(self,request_configuration: Optional[RequestConfiguration[DeltaReq def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -74,7 +74,7 @@ def with_url(self,raw_url: str) -> DeltaRequestBuilder: @dataclass class DeltaRequestBuilderGetQueryParameters(): """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/groups/item/events/item/instances/delta/delta_request_builder.py b/msgraph_beta/generated/groups/item/events/item/instances/delta/delta_request_builder.py index 25fa730dfca..be096b2e5ab 100644 --- a/msgraph_beta/generated/groups/item/events/item/instances/delta/delta_request_builder.py +++ b/msgraph_beta/generated/groups/item/events/item/instances/delta/delta_request_builder.py @@ -31,7 +31,7 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def get(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> Optional[DeltaGetResponse]: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[DeltaGetResponse] Find more info here: https://learn.microsoft.com/graph/api/event-delta?view=graph-rest-beta @@ -52,7 +52,7 @@ async def get(self,request_configuration: Optional[RequestConfiguration[DeltaReq def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -74,7 +74,7 @@ def with_url(self,raw_url: str) -> DeltaRequestBuilder: @dataclass class DeltaRequestBuilderGetQueryParameters(): """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/groups/item/events/item/instances/item/exception_occurrences/delta/delta_request_builder.py b/msgraph_beta/generated/groups/item/events/item/instances/item/exception_occurrences/delta/delta_request_builder.py index 3afef646a38..73347d460a3 100644 --- a/msgraph_beta/generated/groups/item/events/item/instances/item/exception_occurrences/delta/delta_request_builder.py +++ b/msgraph_beta/generated/groups/item/events/item/instances/item/exception_occurrences/delta/delta_request_builder.py @@ -31,7 +31,7 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def get(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> Optional[DeltaGetResponse]: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[DeltaGetResponse] Find more info here: https://learn.microsoft.com/graph/api/event-delta?view=graph-rest-beta @@ -52,7 +52,7 @@ async def get(self,request_configuration: Optional[RequestConfiguration[DeltaReq def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -74,7 +74,7 @@ def with_url(self,raw_url: str) -> DeltaRequestBuilder: @dataclass class DeltaRequestBuilderGetQueryParameters(): """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/groups/item/onenote/notebooks/item/notebook_item_request_builder.py b/msgraph_beta/generated/groups/item/onenote/notebooks/item/notebook_item_request_builder.py index 6a879e867c8..474bd83b83a 100644 --- a/msgraph_beta/generated/groups/item/onenote/notebooks/item/notebook_item_request_builder.py +++ b/msgraph_beta/generated/groups/item/onenote/notebooks/item/notebook_item_request_builder.py @@ -52,7 +52,7 @@ async def delete(self,request_configuration: Optional[RequestConfiguration[Query async def get(self,request_configuration: Optional[RequestConfiguration[NotebookItemRequestBuilderGetQueryParameters]] = None) -> Optional[Notebook]: """ - The collection of OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The collection of OneNote notebooks that the user or group owns. Read-only. Nullable. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[Notebook] """ @@ -106,7 +106,7 @@ def to_delete_request_information(self,request_configuration: Optional[RequestCo def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[NotebookItemRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - The collection of OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The collection of OneNote notebooks that the user or group owns. Read-only. Nullable. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -177,7 +177,7 @@ class NotebookItemRequestBuilderDeleteRequestConfiguration(RequestConfiguration[ @dataclass class NotebookItemRequestBuilderGetQueryParameters(): """ - The collection of OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The collection of OneNote notebooks that the user or group owns. Read-only. Nullable. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/groups/item/onenote/notebooks/notebooks_request_builder.py b/msgraph_beta/generated/groups/item/onenote/notebooks/notebooks_request_builder.py index d240b8c8a09..ec8fecb9100 100644 --- a/msgraph_beta/generated/groups/item/onenote/notebooks/notebooks_request_builder.py +++ b/msgraph_beta/generated/groups/item/onenote/notebooks/notebooks_request_builder.py @@ -50,7 +50,7 @@ def by_notebook_id(self,notebook_id: str) -> NotebookItemRequestBuilder: async def get(self,request_configuration: Optional[RequestConfiguration[NotebooksRequestBuilderGetQueryParameters]] = None) -> Optional[NotebookCollectionResponse]: """ - The collection of OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The collection of OneNote notebooks that the user or group owns. Read-only. Nullable. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[NotebookCollectionResponse] """ @@ -105,7 +105,7 @@ async def post(self,body: Notebook, request_configuration: Optional[RequestConfi def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[NotebooksRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - The collection of OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The collection of OneNote notebooks that the user or group owns. Read-only. Nullable. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -160,7 +160,7 @@ def get_notebook_from_web_url(self) -> GetNotebookFromWebUrlRequestBuilder: @dataclass class NotebooksRequestBuilderGetQueryParameters(): """ - The collection of OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The collection of OneNote notebooks that the user or group owns. Read-only. Nullable. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/groups/item/onenote/pages/item/onenote_page_item_request_builder.py b/msgraph_beta/generated/groups/item/onenote/pages/item/onenote_page_item_request_builder.py index f958963ec6e..3dfdd0b3b48 100644 --- a/msgraph_beta/generated/groups/item/onenote/pages/item/onenote_page_item_request_builder.py +++ b/msgraph_beta/generated/groups/item/onenote/pages/item/onenote_page_item_request_builder.py @@ -55,7 +55,7 @@ async def delete(self,request_configuration: Optional[RequestConfiguration[Query async def get(self,request_configuration: Optional[RequestConfiguration[OnenotePageItemRequestBuilderGetQueryParameters]] = None) -> Optional[OnenotePage]: """ - The pages in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The pages in all OneNote notebooks that the user or group owns. Read-only. Nullable. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[OnenotePage] """ @@ -109,7 +109,7 @@ def to_delete_request_information(self,request_configuration: Optional[RequestCo def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[OnenotePageItemRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - The pages in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The pages in all OneNote notebooks that the user or group owns. Read-only. Nullable. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -207,7 +207,7 @@ class OnenotePageItemRequestBuilderDeleteRequestConfiguration(RequestConfigurati @dataclass class OnenotePageItemRequestBuilderGetQueryParameters(): """ - The pages in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The pages in all OneNote notebooks that the user or group owns. Read-only. Nullable. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/groups/item/onenote/pages/pages_request_builder.py b/msgraph_beta/generated/groups/item/onenote/pages/pages_request_builder.py index 613c073798a..958a915084e 100644 --- a/msgraph_beta/generated/groups/item/onenote/pages/pages_request_builder.py +++ b/msgraph_beta/generated/groups/item/onenote/pages/pages_request_builder.py @@ -48,7 +48,7 @@ def by_onenote_page_id(self,onenote_page_id: str) -> OnenotePageItemRequestBuild async def get(self,request_configuration: Optional[RequestConfiguration[PagesRequestBuilderGetQueryParameters]] = None) -> Optional[OnenotePageCollectionResponse]: """ - The pages in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The pages in all OneNote notebooks that the user or group owns. Read-only. Nullable. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[OnenotePageCollectionResponse] """ @@ -91,7 +91,7 @@ async def post(self,body: OnenotePage, request_configuration: Optional[RequestCo def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[PagesRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - The pages in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The pages in all OneNote notebooks that the user or group owns. Read-only. Nullable. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -137,7 +137,7 @@ def count(self) -> CountRequestBuilder: @dataclass class PagesRequestBuilderGetQueryParameters(): """ - The pages in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The pages in all OneNote notebooks that the user or group owns. Read-only. Nullable. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/groups/item/onenote/section_groups/item/section_group_item_request_builder.py b/msgraph_beta/generated/groups/item/onenote/section_groups/item/section_group_item_request_builder.py index 1e051383988..e9fda2298f1 100644 --- a/msgraph_beta/generated/groups/item/onenote/section_groups/item/section_group_item_request_builder.py +++ b/msgraph_beta/generated/groups/item/onenote/section_groups/item/section_group_item_request_builder.py @@ -53,7 +53,7 @@ async def delete(self,request_configuration: Optional[RequestConfiguration[Query async def get(self,request_configuration: Optional[RequestConfiguration[SectionGroupItemRequestBuilderGetQueryParameters]] = None) -> Optional[SectionGroup]: """ - The section groups in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The section groups in all OneNote notebooks that the user or group owns. Read-only. Nullable. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[SectionGroup] """ @@ -107,7 +107,7 @@ def to_delete_request_information(self,request_configuration: Optional[RequestCo def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[SectionGroupItemRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - The section groups in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The section groups in all OneNote notebooks that the user or group owns. Read-only. Nullable. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -187,7 +187,7 @@ class SectionGroupItemRequestBuilderDeleteRequestConfiguration(RequestConfigurat @dataclass class SectionGroupItemRequestBuilderGetQueryParameters(): """ - The section groups in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The section groups in all OneNote notebooks that the user or group owns. Read-only. Nullable. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/groups/item/onenote/section_groups/section_groups_request_builder.py b/msgraph_beta/generated/groups/item/onenote/section_groups/section_groups_request_builder.py index 5dfa1f5efd2..08742ed832f 100644 --- a/msgraph_beta/generated/groups/item/onenote/section_groups/section_groups_request_builder.py +++ b/msgraph_beta/generated/groups/item/onenote/section_groups/section_groups_request_builder.py @@ -48,7 +48,7 @@ def by_section_group_id(self,section_group_id: str) -> SectionGroupItemRequestBu async def get(self,request_configuration: Optional[RequestConfiguration[SectionGroupsRequestBuilderGetQueryParameters]] = None) -> Optional[SectionGroupCollectionResponse]: """ - The section groups in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The section groups in all OneNote notebooks that the user or group owns. Read-only. Nullable. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[SectionGroupCollectionResponse] """ @@ -91,7 +91,7 @@ async def post(self,body: SectionGroup, request_configuration: Optional[RequestC def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[SectionGroupsRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - The section groups in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The section groups in all OneNote notebooks that the user or group owns. Read-only. Nullable. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -137,7 +137,7 @@ def count(self) -> CountRequestBuilder: @dataclass class SectionGroupsRequestBuilderGetQueryParameters(): """ - The section groups in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The section groups in all OneNote notebooks that the user or group owns. Read-only. Nullable. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/groups/item/onenote/sections/item/onenote_section_item_request_builder.py b/msgraph_beta/generated/groups/item/onenote/sections/item/onenote_section_item_request_builder.py index dd59d59471b..7ce62d4e0ed 100644 --- a/msgraph_beta/generated/groups/item/onenote/sections/item/onenote_section_item_request_builder.py +++ b/msgraph_beta/generated/groups/item/onenote/sections/item/onenote_section_item_request_builder.py @@ -54,7 +54,7 @@ async def delete(self,request_configuration: Optional[RequestConfiguration[Query async def get(self,request_configuration: Optional[RequestConfiguration[OnenoteSectionItemRequestBuilderGetQueryParameters]] = None) -> Optional[OnenoteSection]: """ - The sections in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The sections in all OneNote notebooks that the user or group owns. Read-only. Nullable. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[OnenoteSection] """ @@ -108,7 +108,7 @@ def to_delete_request_information(self,request_configuration: Optional[RequestCo def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[OnenoteSectionItemRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - The sections in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The sections in all OneNote notebooks that the user or group owns. Read-only. Nullable. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -197,7 +197,7 @@ class OnenoteSectionItemRequestBuilderDeleteRequestConfiguration(RequestConfigur @dataclass class OnenoteSectionItemRequestBuilderGetQueryParameters(): """ - The sections in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The sections in all OneNote notebooks that the user or group owns. Read-only. Nullable. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/groups/item/onenote/sections/sections_request_builder.py b/msgraph_beta/generated/groups/item/onenote/sections/sections_request_builder.py index cbef70c834a..bdc5be4a0de 100644 --- a/msgraph_beta/generated/groups/item/onenote/sections/sections_request_builder.py +++ b/msgraph_beta/generated/groups/item/onenote/sections/sections_request_builder.py @@ -48,7 +48,7 @@ def by_onenote_section_id(self,onenote_section_id: str) -> OnenoteSectionItemReq async def get(self,request_configuration: Optional[RequestConfiguration[SectionsRequestBuilderGetQueryParameters]] = None) -> Optional[OnenoteSectionCollectionResponse]: """ - The sections in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The sections in all OneNote notebooks that the user or group owns. Read-only. Nullable. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[OnenoteSectionCollectionResponse] """ @@ -91,7 +91,7 @@ async def post(self,body: OnenoteSection, request_configuration: Optional[Reques def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[SectionsRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - The sections in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The sections in all OneNote notebooks that the user or group owns. Read-only. Nullable. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -137,7 +137,7 @@ def count(self) -> CountRequestBuilder: @dataclass class SectionsRequestBuilderGetQueryParameters(): """ - The sections in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The sections in all OneNote notebooks that the user or group owns. Read-only. Nullable. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/groups/item/sites/item/onenote/notebooks/item/notebook_item_request_builder.py b/msgraph_beta/generated/groups/item/sites/item/onenote/notebooks/item/notebook_item_request_builder.py index 11710c43e57..6fe66ce69ef 100644 --- a/msgraph_beta/generated/groups/item/sites/item/onenote/notebooks/item/notebook_item_request_builder.py +++ b/msgraph_beta/generated/groups/item/sites/item/onenote/notebooks/item/notebook_item_request_builder.py @@ -52,7 +52,7 @@ async def delete(self,request_configuration: Optional[RequestConfiguration[Query async def get(self,request_configuration: Optional[RequestConfiguration[NotebookItemRequestBuilderGetQueryParameters]] = None) -> Optional[Notebook]: """ - The collection of OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The collection of OneNote notebooks that the user or group owns. Read-only. Nullable. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[Notebook] """ @@ -106,7 +106,7 @@ def to_delete_request_information(self,request_configuration: Optional[RequestCo def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[NotebookItemRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - The collection of OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The collection of OneNote notebooks that the user or group owns. Read-only. Nullable. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -177,7 +177,7 @@ class NotebookItemRequestBuilderDeleteRequestConfiguration(RequestConfiguration[ @dataclass class NotebookItemRequestBuilderGetQueryParameters(): """ - The collection of OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The collection of OneNote notebooks that the user or group owns. Read-only. Nullable. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/groups/item/sites/item/onenote/notebooks/notebooks_request_builder.py b/msgraph_beta/generated/groups/item/sites/item/onenote/notebooks/notebooks_request_builder.py index 37fe877e196..ab4f63d8323 100644 --- a/msgraph_beta/generated/groups/item/sites/item/onenote/notebooks/notebooks_request_builder.py +++ b/msgraph_beta/generated/groups/item/sites/item/onenote/notebooks/notebooks_request_builder.py @@ -50,7 +50,7 @@ def by_notebook_id(self,notebook_id: str) -> NotebookItemRequestBuilder: async def get(self,request_configuration: Optional[RequestConfiguration[NotebooksRequestBuilderGetQueryParameters]] = None) -> Optional[NotebookCollectionResponse]: """ - The collection of OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The collection of OneNote notebooks that the user or group owns. Read-only. Nullable. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[NotebookCollectionResponse] """ @@ -105,7 +105,7 @@ async def post(self,body: Notebook, request_configuration: Optional[RequestConfi def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[NotebooksRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - The collection of OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The collection of OneNote notebooks that the user or group owns. Read-only. Nullable. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -160,7 +160,7 @@ def get_notebook_from_web_url(self) -> GetNotebookFromWebUrlRequestBuilder: @dataclass class NotebooksRequestBuilderGetQueryParameters(): """ - The collection of OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The collection of OneNote notebooks that the user or group owns. Read-only. Nullable. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/groups/item/sites/item/onenote/pages/item/onenote_page_item_request_builder.py b/msgraph_beta/generated/groups/item/sites/item/onenote/pages/item/onenote_page_item_request_builder.py index f3e4b273efb..cce088a4df2 100644 --- a/msgraph_beta/generated/groups/item/sites/item/onenote/pages/item/onenote_page_item_request_builder.py +++ b/msgraph_beta/generated/groups/item/sites/item/onenote/pages/item/onenote_page_item_request_builder.py @@ -55,7 +55,7 @@ async def delete(self,request_configuration: Optional[RequestConfiguration[Query async def get(self,request_configuration: Optional[RequestConfiguration[OnenotePageItemRequestBuilderGetQueryParameters]] = None) -> Optional[OnenotePage]: """ - The pages in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The pages in all OneNote notebooks that the user or group owns. Read-only. Nullable. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[OnenotePage] """ @@ -109,7 +109,7 @@ def to_delete_request_information(self,request_configuration: Optional[RequestCo def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[OnenotePageItemRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - The pages in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The pages in all OneNote notebooks that the user or group owns. Read-only. Nullable. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -207,7 +207,7 @@ class OnenotePageItemRequestBuilderDeleteRequestConfiguration(RequestConfigurati @dataclass class OnenotePageItemRequestBuilderGetQueryParameters(): """ - The pages in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The pages in all OneNote notebooks that the user or group owns. Read-only. Nullable. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/groups/item/sites/item/onenote/pages/pages_request_builder.py b/msgraph_beta/generated/groups/item/sites/item/onenote/pages/pages_request_builder.py index 4e04a4c8b0f..d24aee9a91d 100644 --- a/msgraph_beta/generated/groups/item/sites/item/onenote/pages/pages_request_builder.py +++ b/msgraph_beta/generated/groups/item/sites/item/onenote/pages/pages_request_builder.py @@ -48,7 +48,7 @@ def by_onenote_page_id(self,onenote_page_id: str) -> OnenotePageItemRequestBuild async def get(self,request_configuration: Optional[RequestConfiguration[PagesRequestBuilderGetQueryParameters]] = None) -> Optional[OnenotePageCollectionResponse]: """ - The pages in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The pages in all OneNote notebooks that the user or group owns. Read-only. Nullable. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[OnenotePageCollectionResponse] """ @@ -91,7 +91,7 @@ async def post(self,body: OnenotePage, request_configuration: Optional[RequestCo def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[PagesRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - The pages in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The pages in all OneNote notebooks that the user or group owns. Read-only. Nullable. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -137,7 +137,7 @@ def count(self) -> CountRequestBuilder: @dataclass class PagesRequestBuilderGetQueryParameters(): """ - The pages in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The pages in all OneNote notebooks that the user or group owns. Read-only. Nullable. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/groups/item/sites/item/onenote/section_groups/item/section_group_item_request_builder.py b/msgraph_beta/generated/groups/item/sites/item/onenote/section_groups/item/section_group_item_request_builder.py index 3c0b57bb0dd..5af463a9b49 100644 --- a/msgraph_beta/generated/groups/item/sites/item/onenote/section_groups/item/section_group_item_request_builder.py +++ b/msgraph_beta/generated/groups/item/sites/item/onenote/section_groups/item/section_group_item_request_builder.py @@ -53,7 +53,7 @@ async def delete(self,request_configuration: Optional[RequestConfiguration[Query async def get(self,request_configuration: Optional[RequestConfiguration[SectionGroupItemRequestBuilderGetQueryParameters]] = None) -> Optional[SectionGroup]: """ - The section groups in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The section groups in all OneNote notebooks that the user or group owns. Read-only. Nullable. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[SectionGroup] """ @@ -107,7 +107,7 @@ def to_delete_request_information(self,request_configuration: Optional[RequestCo def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[SectionGroupItemRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - The section groups in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The section groups in all OneNote notebooks that the user or group owns. Read-only. Nullable. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -187,7 +187,7 @@ class SectionGroupItemRequestBuilderDeleteRequestConfiguration(RequestConfigurat @dataclass class SectionGroupItemRequestBuilderGetQueryParameters(): """ - The section groups in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The section groups in all OneNote notebooks that the user or group owns. Read-only. Nullable. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/groups/item/sites/item/onenote/section_groups/section_groups_request_builder.py b/msgraph_beta/generated/groups/item/sites/item/onenote/section_groups/section_groups_request_builder.py index 69fdd9e8fb1..2d8ff2c194d 100644 --- a/msgraph_beta/generated/groups/item/sites/item/onenote/section_groups/section_groups_request_builder.py +++ b/msgraph_beta/generated/groups/item/sites/item/onenote/section_groups/section_groups_request_builder.py @@ -48,7 +48,7 @@ def by_section_group_id(self,section_group_id: str) -> SectionGroupItemRequestBu async def get(self,request_configuration: Optional[RequestConfiguration[SectionGroupsRequestBuilderGetQueryParameters]] = None) -> Optional[SectionGroupCollectionResponse]: """ - The section groups in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The section groups in all OneNote notebooks that the user or group owns. Read-only. Nullable. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[SectionGroupCollectionResponse] """ @@ -91,7 +91,7 @@ async def post(self,body: SectionGroup, request_configuration: Optional[RequestC def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[SectionGroupsRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - The section groups in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The section groups in all OneNote notebooks that the user or group owns. Read-only. Nullable. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -137,7 +137,7 @@ def count(self) -> CountRequestBuilder: @dataclass class SectionGroupsRequestBuilderGetQueryParameters(): """ - The section groups in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The section groups in all OneNote notebooks that the user or group owns. Read-only. Nullable. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/groups/item/sites/item/onenote/sections/item/onenote_section_item_request_builder.py b/msgraph_beta/generated/groups/item/sites/item/onenote/sections/item/onenote_section_item_request_builder.py index 83fc8b0ccab..564904128bf 100644 --- a/msgraph_beta/generated/groups/item/sites/item/onenote/sections/item/onenote_section_item_request_builder.py +++ b/msgraph_beta/generated/groups/item/sites/item/onenote/sections/item/onenote_section_item_request_builder.py @@ -54,7 +54,7 @@ async def delete(self,request_configuration: Optional[RequestConfiguration[Query async def get(self,request_configuration: Optional[RequestConfiguration[OnenoteSectionItemRequestBuilderGetQueryParameters]] = None) -> Optional[OnenoteSection]: """ - The sections in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The sections in all OneNote notebooks that the user or group owns. Read-only. Nullable. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[OnenoteSection] """ @@ -108,7 +108,7 @@ def to_delete_request_information(self,request_configuration: Optional[RequestCo def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[OnenoteSectionItemRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - The sections in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The sections in all OneNote notebooks that the user or group owns. Read-only. Nullable. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -197,7 +197,7 @@ class OnenoteSectionItemRequestBuilderDeleteRequestConfiguration(RequestConfigur @dataclass class OnenoteSectionItemRequestBuilderGetQueryParameters(): """ - The sections in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The sections in all OneNote notebooks that the user or group owns. Read-only. Nullable. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/groups/item/sites/item/onenote/sections/sections_request_builder.py b/msgraph_beta/generated/groups/item/sites/item/onenote/sections/sections_request_builder.py index e2757de6b96..e6f21b67524 100644 --- a/msgraph_beta/generated/groups/item/sites/item/onenote/sections/sections_request_builder.py +++ b/msgraph_beta/generated/groups/item/sites/item/onenote/sections/sections_request_builder.py @@ -48,7 +48,7 @@ def by_onenote_section_id(self,onenote_section_id: str) -> OnenoteSectionItemReq async def get(self,request_configuration: Optional[RequestConfiguration[SectionsRequestBuilderGetQueryParameters]] = None) -> Optional[OnenoteSectionCollectionResponse]: """ - The sections in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The sections in all OneNote notebooks that the user or group owns. Read-only. Nullable. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[OnenoteSectionCollectionResponse] """ @@ -91,7 +91,7 @@ async def post(self,body: OnenoteSection, request_configuration: Optional[Reques def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[SectionsRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - The sections in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The sections in all OneNote notebooks that the user or group owns. Read-only. Nullable. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -137,7 +137,7 @@ def count(self) -> CountRequestBuilder: @dataclass class SectionsRequestBuilderGetQueryParameters(): """ - The sections in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The sections in all OneNote notebooks that the user or group owns. Read-only. Nullable. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/groups/item/threads/item/reply/reply_request_builder.py b/msgraph_beta/generated/groups/item/threads/item/reply/reply_request_builder.py index 201affd5c05..5f4b4b464de 100644 --- a/msgraph_beta/generated/groups/item/threads/item/reply/reply_request_builder.py +++ b/msgraph_beta/generated/groups/item/threads/item/reply/reply_request_builder.py @@ -31,11 +31,11 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def post(self,body: ReplyPostRequestBody, request_configuration: Optional[RequestConfiguration[QueryParameters]] = None) -> None: """ - Create an open extension (openTypeExtension object) and add custom properties in a new or existing instance of a resource. You can create an open extension in a resource instance and store custom data to it all in the same operation, except for specific resources. The table in the Permissions section lists the resources that support open extensions. + Reply to a post and add a new post to the specified thread in a group conversation. You can specify both the parent conversation and thread in the request, or, you can specify just the parent thread without the parent conversation. param body: The request body param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: None - Find more info here: https://learn.microsoft.com/graph/api/opentypeextension-post-opentypeextension?view=graph-rest-beta + Find more info here: https://learn.microsoft.com/graph/api/post-reply?view=graph-rest-beta """ if body is None: raise TypeError("body cannot be null.") @@ -53,7 +53,7 @@ async def post(self,body: ReplyPostRequestBody, request_configuration: Optional[ def to_post_request_information(self,body: ReplyPostRequestBody, request_configuration: Optional[RequestConfiguration[QueryParameters]] = None) -> RequestInformation: """ - Create an open extension (openTypeExtension object) and add custom properties in a new or existing instance of a resource. You can create an open extension in a resource instance and store custom data to it all in the same operation, except for specific resources. The table in the Permissions section lists the resources that support open extensions. + Reply to a post and add a new post to the specified thread in a group conversation. You can specify both the parent conversation and thread in the request, or, you can specify just the parent thread without the parent conversation. param body: The request body param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation diff --git a/msgraph_beta/generated/identity/conditional_access/named_locations/item/named_location_item_request_builder.py b/msgraph_beta/generated/identity/conditional_access/named_locations/item/named_location_item_request_builder.py index 37c82ca8bed..cdc85b9e820 100644 --- a/msgraph_beta/generated/identity/conditional_access/named_locations/item/named_location_item_request_builder.py +++ b/msgraph_beta/generated/identity/conditional_access/named_locations/item/named_location_item_request_builder.py @@ -71,11 +71,11 @@ async def get(self,request_configuration: Optional[RequestConfiguration[NamedLoc async def patch(self,body: NamedLocation, request_configuration: Optional[RequestConfiguration[QueryParameters]] = None) -> Optional[NamedLocation]: """ - Update the properties of a countryNamedLocation object. + Update the properties of an ipNamedLocation object. param body: The request body param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[NamedLocation] - Find more info here: https://learn.microsoft.com/graph/api/countrynamedlocation-update?view=graph-rest-beta + Find more info here: https://learn.microsoft.com/graph/api/ipnamedlocation-update?view=graph-rest-beta """ if body is None: raise TypeError("body cannot be null.") @@ -117,7 +117,7 @@ def to_get_request_information(self,request_configuration: Optional[RequestConfi def to_patch_request_information(self,body: NamedLocation, request_configuration: Optional[RequestConfiguration[QueryParameters]] = None) -> RequestInformation: """ - Update the properties of a countryNamedLocation object. + Update the properties of an ipNamedLocation object. param body: The request body param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation diff --git a/msgraph_beta/generated/identity_governance/entitlement_management/access_package_catalogs/item/access_package_custom_workflow_extensions/item/custom_callout_extension_item_request_builder.py b/msgraph_beta/generated/identity_governance/entitlement_management/access_package_catalogs/item/access_package_custom_workflow_extensions/item/custom_callout_extension_item_request_builder.py index e61802d83af..f690b9978aa 100644 --- a/msgraph_beta/generated/identity_governance/entitlement_management/access_package_catalogs/item/access_package_custom_workflow_extensions/item/custom_callout_extension_item_request_builder.py +++ b/msgraph_beta/generated/identity_governance/entitlement_management/access_package_catalogs/item/access_package_custom_workflow_extensions/item/custom_callout_extension_item_request_builder.py @@ -50,10 +50,10 @@ async def delete(self,request_configuration: Optional[RequestConfiguration[Query async def get(self,request_configuration: Optional[RequestConfiguration[CustomCalloutExtensionItemRequestBuilderGetQueryParameters]] = None) -> Optional[CustomCalloutExtension]: """ - Read the properties and relationships of an accessPackageAssignmentWorkflowExtension object. + Read the properties and relationships of an accessPackageAssignmentRequestWorkflowExtension object. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[CustomCalloutExtension] - Find more info here: https://learn.microsoft.com/graph/api/accesspackageassignmentworkflowextension-get?view=graph-rest-beta + Find more info here: https://learn.microsoft.com/graph/api/accesspackageassignmentrequestworkflowextension-get?view=graph-rest-beta """ warn(" as of 2022-10/PrivatePreview:MicrosofEntitlementManagementCustomextensions", DeprecationWarning) request_info = self.to_get_request_information( @@ -109,7 +109,7 @@ def to_delete_request_information(self,request_configuration: Optional[RequestCo def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[CustomCalloutExtensionItemRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Read the properties and relationships of an accessPackageAssignmentWorkflowExtension object. + Read the properties and relationships of an accessPackageAssignmentRequestWorkflowExtension object. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -156,7 +156,7 @@ class CustomCalloutExtensionItemRequestBuilderDeleteRequestConfiguration(Request @dataclass class CustomCalloutExtensionItemRequestBuilderGetQueryParameters(): """ - Read the properties and relationships of an accessPackageAssignmentWorkflowExtension object. + Read the properties and relationships of an accessPackageAssignmentRequestWorkflowExtension object. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/identity_governance/entitlement_management/access_package_catalogs/item/custom_access_package_workflow_extensions/item/custom_access_package_workflow_extension_item_request_builder.py b/msgraph_beta/generated/identity_governance/entitlement_management/access_package_catalogs/item/custom_access_package_workflow_extensions/item/custom_access_package_workflow_extension_item_request_builder.py index 392f8a8a929..33443d53c32 100644 --- a/msgraph_beta/generated/identity_governance/entitlement_management/access_package_catalogs/item/custom_access_package_workflow_extensions/item/custom_access_package_workflow_extension_item_request_builder.py +++ b/msgraph_beta/generated/identity_governance/entitlement_management/access_package_catalogs/item/custom_access_package_workflow_extensions/item/custom_access_package_workflow_extension_item_request_builder.py @@ -31,10 +31,10 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def delete(self,request_configuration: Optional[RequestConfiguration[QueryParameters]] = None) -> None: """ - Delete an accessPackageAssignmentRequestWorkflowExtension object. The custom workflow extension must first be removed from any associated policies before it can be deleted. Follow these steps to remove the custom workflow extension from any associated policies:1. First retrieve the accessPackageCatalogId by calling the Get accessPackageAssignmentPolicies operation and appending ?$expand=accessPackage($expand=accessPackageCatalog) to the query. For example, https://graph.microsoft.com/beta/identityGovernance/entitlementManagement/accessPackageAssignmentPolicies?$expand=accessPackage($expand=accessPackageCatalog).2. Use the access package catalog ID and retrieve the ID of the accessPackageCustomWorkflowExtension object that you want to delete by running the List accessPackageCustomWorkflowExtensions operation.3. Call the Update accessPackageAssignmentPolicy operation to remove the custom workflow extension object from the policy. For an example, see Example 3: Remove the customExtensionStageSettings from a policy. + Delete a customAccessPackageWorkflowExtension object. The custom workflow extension must first be removed from any associated policies before it can be deleted. Follow these steps to remove the custom workflow extension from any associated policies:1. First retrieve the accessPackageCatalogId by calling the Get accessPackageAssignmentPolicies operation and appending ?$expand=accessPackage($expand=accessPackageCatalog) to the query. For example, https://graph.microsoft.com/beta/identityGovernance/entitlementManagement/accessPackageAssignmentPolicies?$expand=accessPackage($expand=accessPackageCatalog).2. Use the access package catalog ID and retrieve the ID of the customAccessPackageWorkflowExtension object that you want to delete by running the LIST customAccessPackageWorkflowExtensions operation.3. Call the Update accessPackageAssignmentPolicy operation to remove the custom workflow extension object from the policy. For an example, see Example 2: Remove the customExtensionHandlers and verifiableCredentialSettings from a policy. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: None - Find more info here: https://learn.microsoft.com/graph/api/accesspackageassignmentrequestworkflowextension-delete?view=graph-rest-beta + Find more info here: https://learn.microsoft.com/graph/api/customaccesspackageworkflowextension-delete?view=graph-rest-beta """ warn(" as of 2022-10/PrivatePreview:MicrosofEntitlementManagementCustomextensions", DeprecationWarning) request_info = self.to_delete_request_information( @@ -98,7 +98,7 @@ async def patch(self,body: CustomAccessPackageWorkflowExtension, request_configu def to_delete_request_information(self,request_configuration: Optional[RequestConfiguration[QueryParameters]] = None) -> RequestInformation: """ - Delete an accessPackageAssignmentRequestWorkflowExtension object. The custom workflow extension must first be removed from any associated policies before it can be deleted. Follow these steps to remove the custom workflow extension from any associated policies:1. First retrieve the accessPackageCatalogId by calling the Get accessPackageAssignmentPolicies operation and appending ?$expand=accessPackage($expand=accessPackageCatalog) to the query. For example, https://graph.microsoft.com/beta/identityGovernance/entitlementManagement/accessPackageAssignmentPolicies?$expand=accessPackage($expand=accessPackageCatalog).2. Use the access package catalog ID and retrieve the ID of the accessPackageCustomWorkflowExtension object that you want to delete by running the List accessPackageCustomWorkflowExtensions operation.3. Call the Update accessPackageAssignmentPolicy operation to remove the custom workflow extension object from the policy. For an example, see Example 3: Remove the customExtensionStageSettings from a policy. + Delete a customAccessPackageWorkflowExtension object. The custom workflow extension must first be removed from any associated policies before it can be deleted. Follow these steps to remove the custom workflow extension from any associated policies:1. First retrieve the accessPackageCatalogId by calling the Get accessPackageAssignmentPolicies operation and appending ?$expand=accessPackage($expand=accessPackageCatalog) to the query. For example, https://graph.microsoft.com/beta/identityGovernance/entitlementManagement/accessPackageAssignmentPolicies?$expand=accessPackage($expand=accessPackageCatalog).2. Use the access package catalog ID and retrieve the ID of the customAccessPackageWorkflowExtension object that you want to delete by running the LIST customAccessPackageWorkflowExtensions operation.3. Call the Update accessPackageAssignmentPolicy operation to remove the custom workflow extension object from the policy. For an example, see Example 2: Remove the customExtensionHandlers and verifiableCredentialSettings from a policy. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ diff --git a/msgraph_beta/generated/identity_governance/entitlement_management/access_packages/item/access_package_item_request_builder.py b/msgraph_beta/generated/identity_governance/entitlement_management/access_packages/item/access_package_item_request_builder.py index 0c3b23b1939..30d4b48f93c 100644 --- a/msgraph_beta/generated/identity_governance/entitlement_management/access_packages/item/access_package_item_request_builder.py +++ b/msgraph_beta/generated/identity_governance/entitlement_management/access_packages/item/access_package_item_request_builder.py @@ -71,10 +71,10 @@ async def delete(self,request_configuration: Optional[RequestConfiguration[Query async def get(self,request_configuration: Optional[RequestConfiguration[AccessPackageItemRequestBuilderGetQueryParameters]] = None) -> Optional[AccessPackage]: """ - Retrieve an access package with a list of accessPackageResourceRoleScope objects. These objects represent the resource roles that an access package assigns to each subject. Each object links to an accessPackageResourceRole and an accessPackageResourceScope. + Retrieve the properties and relationships of an accessPackage object. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[AccessPackage] - Find more info here: https://learn.microsoft.com/graph/api/accesspackage-list-accesspackageresourcerolescopes?view=graph-rest-beta + Find more info here: https://learn.microsoft.com/graph/api/accesspackage-get?view=graph-rest-beta """ request_info = self.to_get_request_information( request_configuration @@ -127,7 +127,7 @@ def to_delete_request_information(self,request_configuration: Optional[RequestCo def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[AccessPackageItemRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Retrieve an access package with a list of accessPackageResourceRoleScope objects. These objects represent the resource roles that an access package assigns to each subject. Each object links to an accessPackageResourceRole and an accessPackageResourceScope. + Retrieve the properties and relationships of an accessPackage object. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -243,7 +243,7 @@ class AccessPackageItemRequestBuilderDeleteRequestConfiguration(RequestConfigura @dataclass class AccessPackageItemRequestBuilderGetQueryParameters(): """ - Retrieve an access package with a list of accessPackageResourceRoleScope objects. These objects represent the resource roles that an access package assigns to each subject. Each object links to an accessPackageResourceRole and an accessPackageResourceScope. + Retrieve the properties and relationships of an accessPackage object. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/identity_governance/entitlement_management/access_packages_with_unique_name/access_packages_with_unique_name_request_builder.py b/msgraph_beta/generated/identity_governance/entitlement_management/access_packages_with_unique_name/access_packages_with_unique_name_request_builder.py index fcf5d129c02..6ee013c3d02 100644 --- a/msgraph_beta/generated/identity_governance/entitlement_management/access_packages_with_unique_name/access_packages_with_unique_name_request_builder.py +++ b/msgraph_beta/generated/identity_governance/entitlement_management/access_packages_with_unique_name/access_packages_with_unique_name_request_builder.py @@ -55,10 +55,10 @@ async def delete(self,request_configuration: Optional[RequestConfiguration[Query async def get(self,request_configuration: Optional[RequestConfiguration[AccessPackagesWithUniqueNameRequestBuilderGetQueryParameters]] = None) -> Optional[AccessPackage]: """ - Retrieve an access package with a list of accessPackageResourceRoleScope objects. These objects represent the resource roles that an access package assigns to each subject. Each object links to an accessPackageResourceRole and an accessPackageResourceScope. + Retrieve the properties and relationships of an accessPackage object. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[AccessPackage] - Find more info here: https://learn.microsoft.com/graph/api/accesspackage-list-accesspackageresourcerolescopes?view=graph-rest-beta + Find more info here: https://learn.microsoft.com/graph/api/accesspackage-get?view=graph-rest-beta """ request_info = self.to_get_request_information( request_configuration @@ -111,7 +111,7 @@ def to_delete_request_information(self,request_configuration: Optional[RequestCo def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[AccessPackagesWithUniqueNameRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Retrieve an access package with a list of accessPackageResourceRoleScope objects. These objects represent the resource roles that an access package assigns to each subject. Each object links to an accessPackageResourceRole and an accessPackageResourceScope. + Retrieve the properties and relationships of an accessPackage object. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -173,7 +173,7 @@ class AccessPackagesWithUniqueNameRequestBuilderDeleteRequestConfiguration(Reque @dataclass class AccessPackagesWithUniqueNameRequestBuilderGetQueryParameters(): """ - Retrieve an access package with a list of accessPackageResourceRoleScope objects. These objects represent the resource roles that an access package assigns to each subject. Each object links to an accessPackageResourceRole and an accessPackageResourceScope. + Retrieve the properties and relationships of an accessPackage object. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/identity_governance/terms_of_use/agreements/item/agreement_item_request_builder.py b/msgraph_beta/generated/identity_governance/terms_of_use/agreements/item/agreement_item_request_builder.py index 140c3a31e65..f070d73e940 100644 --- a/msgraph_beta/generated/identity_governance/terms_of_use/agreements/item/agreement_item_request_builder.py +++ b/msgraph_beta/generated/identity_governance/terms_of_use/agreements/item/agreement_item_request_builder.py @@ -53,10 +53,10 @@ async def delete(self,request_configuration: Optional[RequestConfiguration[Query async def get(self,request_configuration: Optional[RequestConfiguration[AgreementItemRequestBuilderGetQueryParameters]] = None) -> Optional[Agreement]: """ - Retrieve the properties and relationships of an agreement object. + Retrieve all files related to an agreement. This includes the default file and all localized files. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[Agreement] - Find more info here: https://learn.microsoft.com/graph/api/agreement-get?view=graph-rest-beta + Find more info here: https://learn.microsoft.com/graph/api/agreement-list-files?view=graph-rest-beta """ request_info = self.to_get_request_information( request_configuration @@ -109,7 +109,7 @@ def to_delete_request_information(self,request_configuration: Optional[RequestCo def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[AgreementItemRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Retrieve the properties and relationships of an agreement object. + Retrieve all files related to an agreement. This includes the default file and all localized files. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -180,7 +180,7 @@ class AgreementItemRequestBuilderDeleteRequestConfiguration(RequestConfiguration @dataclass class AgreementItemRequestBuilderGetQueryParameters(): """ - Retrieve the properties and relationships of an agreement object. + Retrieve all files related to an agreement. This includes the default file and all localized files. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/identity_protection/risk_detections/item/risk_detection_item_request_builder.py b/msgraph_beta/generated/identity_protection/risk_detections/item/risk_detection_item_request_builder.py index 49513b26780..d68fcfd92ab 100644 --- a/msgraph_beta/generated/identity_protection/risk_detections/item/risk_detection_item_request_builder.py +++ b/msgraph_beta/generated/identity_protection/risk_detections/item/risk_detection_item_request_builder.py @@ -49,10 +49,10 @@ async def delete(self,request_configuration: Optional[RequestConfiguration[Query async def get(self,request_configuration: Optional[RequestConfiguration[RiskDetectionItemRequestBuilderGetQueryParameters]] = None) -> Optional[RiskDetection]: """ - Retrieve the properties of a riskDetection object. + Retrieve the properties of a collection of riskDetection objects. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[RiskDetection] - Find more info here: https://learn.microsoft.com/graph/api/riskdetection-get?view=graph-rest-beta + Find more info here: https://learn.microsoft.com/graph/api/riskdetection-list?view=graph-rest-beta """ request_info = self.to_get_request_information( request_configuration @@ -104,7 +104,7 @@ def to_delete_request_information(self,request_configuration: Optional[RequestCo def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[RiskDetectionItemRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Retrieve the properties of a riskDetection object. + Retrieve the properties of a collection of riskDetection objects. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -148,7 +148,7 @@ class RiskDetectionItemRequestBuilderDeleteRequestConfiguration(RequestConfigura @dataclass class RiskDetectionItemRequestBuilderGetQueryParameters(): """ - Retrieve the properties of a riskDetection object. + Retrieve the properties of a collection of riskDetection objects. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/kiota-lock.json b/msgraph_beta/generated/kiota-lock.json index 65d5770b69f..d076e75ee81 100644 --- a/msgraph_beta/generated/kiota-lock.json +++ b/msgraph_beta/generated/kiota-lock.json @@ -1,8 +1,8 @@ { - "descriptionHash": "C77E5CC6680E71997C77D4B497647030E3B6D51B37B16200F42FA2DB4238160C5FD8825BB6575991A5173DBE083163A1607E39644BDC1AE10B0562F5C8E58B3A", + "descriptionHash": "77254B0BD52910D9C305EC3E0405E2EB4BED8A7AEB257E670B2B233A135FD5BE50E8EE45E035F226EF613845E0E2616DBF0B7526EE9B02CD6A66C0DBF1D0605C", "descriptionLocation": "../../msgraph-metadata/clean_beta_openapi/openapi.yaml", "lockFileVersion": "1.0.0", - "kiotaVersion": "1.21.0", + "kiotaVersion": "1.22.0", "clientClassName": "BaseGraphServiceClient", "typeAccessModifier": "Public", "clientNamespaceName": "msgraph_beta.generated", diff --git a/msgraph_beta/generated/models/android_managed_app_protection.py b/msgraph_beta/generated/models/android_managed_app_protection.py index c4ee15fe3db..f380effc692 100644 --- a/msgraph_beta/generated/models/android_managed_app_protection.py +++ b/msgraph_beta/generated/models/android_managed_app_protection.py @@ -56,9 +56,9 @@ class AndroidManagedAppProtection(TargetedManagedAppProtection, Parsable): block_after_company_portal_update_deferral_in_days: Optional[int] = None # Whether the app should connect to the configured VPN on launch. connect_to_vpn_on_launch: Optional[bool] = None - # Friendly name of the preferred custom browser to open weblink on Android. + # Friendly name of the preferred custom browser to open weblink on Android. When this property is configured, ManagedBrowserToOpenLinksRequired should be true. custom_browser_display_name: Optional[str] = None - # Unique identifier of a custom browser to open weblink on Android. + # Unique identifier of the preferred custom browser to open weblink on Android. When this property is configured, ManagedBrowserToOpenLinksRequired should be true. custom_browser_package_id: Optional[str] = None # Friendly name of a custom dialer app to click-to-open a phone number on Android. custom_dialer_app_display_name: Optional[str] = None diff --git a/msgraph_beta/generated/models/authentication.py b/msgraph_beta/generated/models/authentication.py index 492f7aea96c..fe5de7bf057 100644 --- a/msgraph_beta/generated/models/authentication.py +++ b/msgraph_beta/generated/models/authentication.py @@ -29,7 +29,7 @@ class Authentication(Entity, Parsable): email_methods: Optional[List[EmailAuthenticationMethod]] = None # Represents the FIDO2 security keys registered to a user for authentication. fido2_methods: Optional[List[Fido2AuthenticationMethod]] = None - # The hardwareOathMethods property + # The hardware OATH time-based one-time password (TOTP) devices assigned to a user for authentication. hardware_oath_methods: Optional[List[HardwareOathAuthenticationMethod]] = None # Represents all authentication methods registered to a user. methods: Optional[List[AuthenticationMethod]] = None diff --git a/msgraph_beta/generated/models/authentication_method_device.py b/msgraph_beta/generated/models/authentication_method_device.py index 96fb52dac25..4adfc4e3a8a 100644 --- a/msgraph_beta/generated/models/authentication_method_device.py +++ b/msgraph_beta/generated/models/authentication_method_device.py @@ -11,9 +11,9 @@ @dataclass class AuthenticationMethodDevice(Entity, Parsable): - # The displayName property + # Optional name given to the hardware OATH device. display_name: Optional[str] = None - # The hardwareOathDevices property + # Exposes the hardware OATH method in the directory. hardware_oath_devices: Optional[List[HardwareOathTokenAuthenticationMethodDevice]] = None # The OdataType property odata_type: Optional[str] = None diff --git a/msgraph_beta/generated/models/base_site_page.py b/msgraph_beta/generated/models/base_site_page.py index 7c782840ce7..6079f2571ec 100644 --- a/msgraph_beta/generated/models/base_site_page.py +++ b/msgraph_beta/generated/models/base_site_page.py @@ -18,7 +18,7 @@ class BaseSitePage(BaseItem, Parsable): # The OdataType property odata_type: Optional[str] = "#microsoft.graph.baseSitePage" - # The name of the page layout of the page. The possible values are: microsoftReserved, article, home, unknownFutureValue. + # The name of the page layout of the page. The possible values are: microsoftReserved, article, home, unknownFutureValue, newsLink. You must use the Prefer: include-unknown-enum-members request header to get the following value in this evolvable enum: newsLink. page_layout: Optional[PageLayoutType] = None # The publishing status and the MM.mm version of the page. publishing_state: Optional[PublicationFacet] = None diff --git a/msgraph_beta/generated/models/cloud_pc_cross_region_disaster_recovery_setting.py b/msgraph_beta/generated/models/cloud_pc_cross_region_disaster_recovery_setting.py index ac6a46e844d..37e6a640157 100644 --- a/msgraph_beta/generated/models/cloud_pc_cross_region_disaster_recovery_setting.py +++ b/msgraph_beta/generated/models/cloud_pc_cross_region_disaster_recovery_setting.py @@ -15,11 +15,11 @@ class CloudPcCrossRegionDisasterRecoverySetting(AdditionalDataHolder, BackedMode # Stores additional data not described in the OpenAPI description found when deserializing. Can be used for serialization as well. additional_data: Dict[str, Any] = field(default_factory=dict) - # True if an end user is allowed to set up cross-region disaster recovery for Cloud PC; otherwise, false. The default value is false. + # True if an end user is allowed to set up cross-region disaster recovery for Cloud PC; otherwise, false. The default value is false. This property is deprecated and will no longer be supported effective February 11, 2025. For scenarios where crossRegionDisasterRecoveryEnabled is true, set disasterRecoveryType to crossRegion. For scenarios where crossRegionDisasterRecoveryEnabled is false, set disasterRecoveryType to notconfigured. cross_region_disaster_recovery_enabled: Optional[bool] = None # Indicates the network settings of the Cloud PC during a cross-region disaster recovery operation. disaster_recovery_network_setting: Optional[CloudPcDisasterRecoveryNetworkSetting] = None - # The disasterRecoveryType property + # Indicates the type of disaster recovery to perform when a disaster occurs on the user's Cloud PC. The possible values are: notConfigured, crossRegion, premium, unknownFutureValue. The default value is notConfigured. disaster_recovery_type: Optional[CloudPcDisasterRecoveryType] = None # Indicates whether Windows 365 maintain the cross-region disaster recovery function generated restore points. If true, the Windows 365 stored restore points; false indicates that Windows 365 doesn't generate or keep the restore point from the original Cloud PC. If a disaster occurs, the new Cloud PC can only be provisioned using the initial image. This limitation can result in the loss of some user data on the original Cloud PC. The default value is false. maintain_cross_region_restore_point_enabled: Optional[bool] = None diff --git a/msgraph_beta/generated/models/device_compliance_policy.py b/msgraph_beta/generated/models/device_compliance_policy.py index 32c6324df4b..6d9e1d22d31 100644 --- a/msgraph_beta/generated/models/device_compliance_policy.py +++ b/msgraph_beta/generated/models/device_compliance_policy.py @@ -53,7 +53,7 @@ class DeviceCompliancePolicy(Entity, Parsable): odata_type: Optional[str] = None # List of Scope Tags for this Entity instance. role_scope_tag_ids: Optional[List[str]] = None - # The list of scheduled action for this rule + # The list of scheduled action per rule for this compliance policy. This is a required property when creating any individual per-platform compliance policies. scheduled_actions_for_rule: Optional[List[DeviceComplianceScheduledActionForRule]] = None # Device compliance users status overview user_status_overview: Optional[DeviceComplianceUserOverview] = None diff --git a/msgraph_beta/generated/models/device_management_configuration_choice_setting_definition.py b/msgraph_beta/generated/models/device_management_configuration_choice_setting_definition.py index cea390d1856..1b7ff824ede 100644 --- a/msgraph_beta/generated/models/device_management_configuration_choice_setting_definition.py +++ b/msgraph_beta/generated/models/device_management_configuration_choice_setting_definition.py @@ -12,11 +12,11 @@ @dataclass class DeviceManagementConfigurationChoiceSettingDefinition(DeviceManagementConfigurationSettingDefinition, Parsable): - # Default option for the choice setting. + # Default option for choice setting default_option_id: Optional[str] = None # The OdataType property odata_type: Optional[str] = None - # Options for the setting that can be selected. + # Options for the setting that can be selected options: Optional[List[DeviceManagementConfigurationOptionDefinition]] = None @staticmethod diff --git a/msgraph_beta/generated/models/device_management_configuration_referred_setting_information.py b/msgraph_beta/generated/models/device_management_configuration_referred_setting_information.py index ccba6748b68..f61c36ae50d 100644 --- a/msgraph_beta/generated/models/device_management_configuration_referred_setting_information.py +++ b/msgraph_beta/generated/models/device_management_configuration_referred_setting_information.py @@ -16,7 +16,7 @@ class DeviceManagementConfigurationReferredSettingInformation(AdditionalDataHold additional_data: Dict[str, Any] = field(default_factory=dict) # The OdataType property odata_type: Optional[str] = None - # Setting definition id that is being referred to a setting. Applicable for reusable setting. + # Setting definition id that is being referred to a setting. Applicable for reusable setting setting_definition_id: Optional[str] = None @staticmethod diff --git a/msgraph_beta/generated/models/device_management_configuration_setting_group_collection_definition.py b/msgraph_beta/generated/models/device_management_configuration_setting_group_collection_definition.py index 2638daf7189..63a54b8bcf8 100644 --- a/msgraph_beta/generated/models/device_management_configuration_setting_group_collection_definition.py +++ b/msgraph_beta/generated/models/device_management_configuration_setting_group_collection_definition.py @@ -10,9 +10,9 @@ @dataclass class DeviceManagementConfigurationSettingGroupCollectionDefinition(DeviceManagementConfigurationSettingGroupDefinition, Parsable): - # Maximum number of setting group count in the collection. Valid values 1 to 100 + # Maximum number of setting group count in the collection maximum_count: Optional[int] = None - # Minimum number of setting group count in the collection. Valid values 1 to 100 + # Minimum number of setting group count in the collection minimum_count: Optional[int] = None # The OdataType property odata_type: Optional[str] = None diff --git a/msgraph_beta/generated/models/device_management_configuration_setting_group_definition.py b/msgraph_beta/generated/models/device_management_configuration_setting_group_definition.py index 1a4c3729edd..24b5a6bf935 100644 --- a/msgraph_beta/generated/models/device_management_configuration_setting_group_definition.py +++ b/msgraph_beta/generated/models/device_management_configuration_setting_group_definition.py @@ -13,7 +13,7 @@ @dataclass class DeviceManagementConfigurationSettingGroupDefinition(DeviceManagementConfigurationSettingDefinition, Parsable): - # Dependent child settings to this group of settings + # Dependent child settings to this group of settings. child_ids: Optional[List[str]] = None # List of child settings that depend on this setting depended_on_by: Optional[List[DeviceManagementConfigurationSettingDependedOnBy]] = None diff --git a/msgraph_beta/generated/models/device_management_configuration_simple_setting_collection_definition.py b/msgraph_beta/generated/models/device_management_configuration_simple_setting_collection_definition.py index ea731f21149..1a7f27b2c3b 100644 --- a/msgraph_beta/generated/models/device_management_configuration_simple_setting_collection_definition.py +++ b/msgraph_beta/generated/models/device_management_configuration_simple_setting_collection_definition.py @@ -10,9 +10,9 @@ @dataclass class DeviceManagementConfigurationSimpleSettingCollectionDefinition(DeviceManagementConfigurationSimpleSettingDefinition, Parsable): - # Maximum number of simple settings in the collection + # Maximum number of simple settings in the collection. Valid values 1 to 100 maximum_count: Optional[int] = None - # Minimum number of simple settings in the collection + # Minimum number of simple settings in the collection. Valid values 1 to 100 minimum_count: Optional[int] = None # The OdataType property odata_type: Optional[str] = None diff --git a/msgraph_beta/generated/models/directory.py b/msgraph_beta/generated/models/directory.py index 91711f2004e..f90025a134a 100644 --- a/msgraph_beta/generated/models/directory.py +++ b/msgraph_beta/generated/models/directory.py @@ -33,7 +33,7 @@ class Directory(Entity, Parsable): administrative_units: Optional[List[AdministrativeUnit]] = None # Group of related custom security attribute definitions. attribute_sets: Optional[List[AttributeSet]] = None - # The authenticationMethodDevices property + # Exposes the hardware OATH method in the directory. authentication_method_devices: Optional[AuthenticationMethodDevice] = None # The certificateAuthorities property certificate_authorities: Optional[CertificateAuthorityPath] = None diff --git a/msgraph_beta/generated/models/educational_activity_detail.py b/msgraph_beta/generated/models/educational_activity_detail.py index 9fadf7a6403..f0e26461b43 100644 --- a/msgraph_beta/generated/models/educational_activity_detail.py +++ b/msgraph_beta/generated/models/educational_activity_detail.py @@ -19,13 +19,13 @@ class EducationalActivityDetail(AdditionalDataHolder, BackedModel, Parsable): awards: Optional[List[str]] = None # Short description of the program provided by the user. description: Optional[str] = None - # Long-form name of the program that the user has provided. + # Long-form name of the program that the user provided. display_name: Optional[str] = None # Majors and minors associated with the program. (if applicable) fields_of_study: Optional[List[str]] = None - # The final grade, class, GPA or score. + # The final grade, class, GPA, or score. grade: Optional[str] = None - # Additional notes the user has provided. + # More notes the user provided. notes: Optional[str] = None # The OdataType property odata_type: Optional[str] = None diff --git a/msgraph_beta/generated/models/expiration_pattern.py b/msgraph_beta/generated/models/expiration_pattern.py index 5a7aae85be7..d3c8bf0b011 100644 --- a/msgraph_beta/generated/models/expiration_pattern.py +++ b/msgraph_beta/generated/models/expiration_pattern.py @@ -15,9 +15,9 @@ class ExpirationPattern(AdditionalDataHolder, BackedModel, Parsable): # Stores additional data not described in the OpenAPI description found when deserializing. Can be used for serialization as well. additional_data: Dict[str, Any] = field(default_factory=dict) - # The requestor's desired duration of access represented in ISO 8601 format for durations. For example, PT3H refers to three hours. If specified in a request, endDateTime should not be present and the type property should be set to afterDuration. + # The requestor's desired duration of access represented in ISO 8601 format for durations. For example, PT3H refers to three hours. If specified in a request, endDateTime shouldn't be present and the type property should be set to afterDuration. duration: Optional[datetime.timedelta] = None - # Timestamp of date and time information using ISO 8601 format and is always in UTC time. For example, midnight UTC on Jan 1, 2014 is 2014-01-01T00:00:00Z. + # Timestamp of date and time information using ISO 8601 format and is always in UTC time. For example, midnight UTC on Jan 1, 2014, is 2014-01-01T00:00:00Z. end_date_time: Optional[datetime.datetime] = None # The OdataType property odata_type: Optional[str] = None diff --git a/msgraph_beta/generated/models/external_connectors/configuration.py b/msgraph_beta/generated/models/external_connectors/configuration.py index bd9c82c906a..8f6d4bf0441 100644 --- a/msgraph_beta/generated/models/external_connectors/configuration.py +++ b/msgraph_beta/generated/models/external_connectors/configuration.py @@ -11,7 +11,7 @@ class Configuration(AdditionalDataHolder, BackedModel, Parsable): # Stores additional data not described in the OpenAPI description found when deserializing. Can be used for serialization as well. additional_data: Dict[str, Any] = field(default_factory=dict) - # A collection of application IDs for registered Microsoft Entra apps that are allowed to manage the externalConnection and to index content in the externalConnection. + # A collection of application IDs for registered Microsoft Entra apps allowed to manage the externalConnection and index content in the externalConnection. authorized_app_ids: Optional[List[str]] = None # The OdataType property odata_type: Optional[str] = None diff --git a/msgraph_beta/generated/models/external_connectors/external.py b/msgraph_beta/generated/models/external_connectors/external.py index 8d7a3330daf..bcf3dc9fcf3 100644 --- a/msgraph_beta/generated/models/external_connectors/external.py +++ b/msgraph_beta/generated/models/external_connectors/external.py @@ -16,7 +16,7 @@ class External(AdditionalDataHolder, BackedModel, Parsable): # Stores additional data not described in the OpenAPI description found when deserializing. Can be used for serialization as well. additional_data: Dict[str, Any] = field(default_factory=dict) - # Represents an onboarded AWS account, Azure subscription, or GCP project that Microsoft Entra Permissions Management will collect and analyze permissions and actions on. + # Represents an onboarded Amazon Web Services (AWS) account, Azure subscription, or Google Cloud Platform (GCP) project that Microsoft Entra Permissions Management collects and analyzes permissions and actions on. authorization_systems: Optional[List[AuthorizationSystem]] = None # The connections property connections: Optional[List[ExternalConnection]] = None diff --git a/msgraph_beta/generated/models/hardware_oath_authentication_method.py b/msgraph_beta/generated/models/hardware_oath_authentication_method.py index ab558517451..58643886509 100644 --- a/msgraph_beta/generated/models/hardware_oath_authentication_method.py +++ b/msgraph_beta/generated/models/hardware_oath_authentication_method.py @@ -13,7 +13,7 @@ class HardwareOathAuthenticationMethod(AuthenticationMethod, Parsable): # The OdataType property odata_type: Optional[str] = "#microsoft.graph.hardwareOathAuthenticationMethod" - # The device property + # Exposes the hardware OATH method in the directory. device: Optional[HardwareOathTokenAuthenticationMethodDevice] = None @staticmethod diff --git a/msgraph_beta/generated/models/hardware_oath_token_authentication_method_device.py b/msgraph_beta/generated/models/hardware_oath_token_authentication_method_device.py index 03813b254df..f674f6fdd1c 100644 --- a/msgraph_beta/generated/models/hardware_oath_token_authentication_method_device.py +++ b/msgraph_beta/generated/models/hardware_oath_token_authentication_method_device.py @@ -16,23 +16,23 @@ class HardwareOathTokenAuthenticationMethodDevice(AuthenticationMethodDevice, Parsable): # The OdataType property odata_type: Optional[str] = "#microsoft.graph.hardwareOathTokenAuthenticationMethodDevice" - # The assignTo property + # Assign the hardware OATH token to a user. assign_to: Optional[User] = None - # The assignedTo property + # User the token is assigned to. Nullable. Supports $filter (eq). assigned_to: Optional[Identity] = None - # The hashFunction property + # Hash function of the hardrware token. The possible values are: hmacsha1 or hmacsha256. Default value is: hmacsha1. Supports $filter (eq). hash_function: Optional[HardwareOathTokenHashFunction] = None - # The manufacturer property + # Manufacturer name of the hardware token. Supports $filter (eq). manufacturer: Optional[str] = None - # The model property + # Model name of the hardware token. Supports $filter (eq). model: Optional[str] = None - # The secretKey property + # Secret key of the specific hardware token, provided by the vendor. secret_key: Optional[str] = None - # The serialNumber property + # Serial number of the specific hardware token, often found on the back of the device. Supports $select and $filter (eq). serial_number: Optional[str] = None - # The status property + # Status of the hardware OATH token.The possible values are: available, assigned, activated, failedActivation. Supports $filter(eq). status: Optional[HardwareOathTokenStatus] = None - # The timeIntervalInSeconds property + # Refresh interval of the 6-digit verification code, in seconds. The possible values are: 30 or 60. Supports $filter (eq). time_interval_in_seconds: Optional[int] = None @staticmethod diff --git a/msgraph_beta/generated/models/identity.py b/msgraph_beta/generated/models/identity.py index d567a18d7ef..4bc65e8482f 100644 --- a/msgraph_beta/generated/models/identity.py +++ b/msgraph_beta/generated/models/identity.py @@ -38,9 +38,9 @@ class Identity(AdditionalDataHolder, BackedModel, Parsable): # Stores additional data not described in the OpenAPI description found when deserializing. Can be used for serialization as well. additional_data: Dict[str, Any] = field(default_factory=dict) - # The display name of the identity. For drive items, the display name might not always be available or up to date. For example, if a user changes their display name the API might show the new value in a future response, but the items associated with the user don't show up as changed when using delta. + # The display name of the identity. This property is read-only. display_name: Optional[str] = None - # Unique identifier for the identity or actor. For example, in the access reviews decisions API, this property might record the id of the principal, that is, the group, user, or application that's subject to review. + # The identifier of the identity. This property is read-only. id: Optional[str] = None # The OdataType property odata_type: Optional[str] = None diff --git a/msgraph_beta/generated/models/identity_set.py b/msgraph_beta/generated/models/identity_set.py index 1f58cebdfa7..dc63fd8176a 100644 --- a/msgraph_beta/generated/models/identity_set.py +++ b/msgraph_beta/generated/models/identity_set.py @@ -20,13 +20,13 @@ class IdentitySet(AdditionalDataHolder, BackedModel, Parsable): # Stores additional data not described in the OpenAPI description found when deserializing. Can be used for serialization as well. additional_data: Dict[str, Any] = field(default_factory=dict) - # The Identity of the Application. This property is read-only. + # Optional. The application associated with this action. application: Optional[Identity] = None - # The Identity of the Device. This property is read-only. + # Optional. The device associated with this action. device: Optional[Identity] = None # The OdataType property odata_type: Optional[str] = None - # The Identity of the User. This property is read-only. + # Optional. The user associated with this action. user: Optional[Identity] = None @staticmethod diff --git a/msgraph_beta/generated/models/initiator.py b/msgraph_beta/generated/models/initiator.py index d9efadd13a6..36afe1b66cd 100644 --- a/msgraph_beta/generated/models/initiator.py +++ b/msgraph_beta/generated/models/initiator.py @@ -13,7 +13,7 @@ class Initiator(Identity, Parsable): # The OdataType property odata_type: Optional[str] = "#microsoft.graph.initiator" - # Type of initiator. Possible values are: user, application, system, unknownFutureValue. + # The type of the initiator. Possible values are: user, application, system, unknownFutureValue. initiator_type: Optional[InitiatorType] = None @staticmethod diff --git a/msgraph_beta/generated/models/item_attachment.py b/msgraph_beta/generated/models/item_attachment.py index 4a57f5513e5..f7a3ce19e6f 100644 --- a/msgraph_beta/generated/models/item_attachment.py +++ b/msgraph_beta/generated/models/item_attachment.py @@ -13,7 +13,7 @@ class ItemAttachment(Attachment, Parsable): # The OdataType property odata_type: Optional[str] = "#microsoft.graph.itemAttachment" - # The attached contact, message or event. Navigation property. + # The attached contact, message, or event. Navigation property. item: Optional[OutlookItem] = None @staticmethod diff --git a/msgraph_beta/generated/models/key_value_pair.py b/msgraph_beta/generated/models/key_value_pair.py index 88c24004fc3..3172df03ead 100644 --- a/msgraph_beta/generated/models/key_value_pair.py +++ b/msgraph_beta/generated/models/key_value_pair.py @@ -11,11 +11,11 @@ class KeyValuePair(AdditionalDataHolder, BackedModel, Parsable): # Stores additional data not described in the OpenAPI description found when deserializing. Can be used for serialization as well. additional_data: Dict[str, Any] = field(default_factory=dict) - # Name for this key-value pair. For more information about possible names for each resource type that uses this configuration, see keyValuePair names and values. + # Name for this key-value pair name: Optional[str] = None # The OdataType property odata_type: Optional[str] = None - # Value for this key-value pair. For more information about possible values for each resource type that uses this configuration, see keyValuePair names and values. + # Value for this key-value pair value: Optional[str] = None @staticmethod diff --git a/msgraph_beta/generated/models/mac_os_lob_app_assignment_settings.py b/msgraph_beta/generated/models/mac_os_lob_app_assignment_settings.py index 10a8f77f250..ed298b1ddd6 100644 --- a/msgraph_beta/generated/models/mac_os_lob_app_assignment_settings.py +++ b/msgraph_beta/generated/models/mac_os_lob_app_assignment_settings.py @@ -15,7 +15,7 @@ class MacOsLobAppAssignmentSettings(MobileAppAssignmentSettings, Parsable): """ # The OdataType property odata_type: Optional[str] = "#microsoft.graph.macOsLobAppAssignmentSettings" - # Whether or not to uninstall the app when device is removed from Intune. + # When TRUE, indicates that the app should be uninstalled when the device is removed from Intune. When FALSE, indicates that the app will not be uninstalled when the device is removed from Intune. uninstall_on_device_removal: Optional[bool] = None @staticmethod diff --git a/msgraph_beta/generated/models/mail_tips.py b/msgraph_beta/generated/models/mail_tips.py index d2be78f1837..82f1fb1b947 100644 --- a/msgraph_beta/generated/models/mail_tips.py +++ b/msgraph_beta/generated/models/mail_tips.py @@ -18,11 +18,11 @@ class MailTips(AdditionalDataHolder, BackedModel, Parsable): # Stores additional data not described in the OpenAPI description found when deserializing. Can be used for serialization as well. additional_data: Dict[str, Any] = field(default_factory=dict) - # Mail tips for automatic reply if it has been set up by the recipient. + # Mailtips for an automatic reply if set up by the recipient. automatic_replies: Optional[AutomaticRepliesMailTips] = None # A custom mail tip that can be set on the recipient's mailbox. custom_mail_tip: Optional[str] = None - # Whether the recipient's mailbox is restricted, for example, accepting messages from only a predefined list of senders, rejecting messages from a predefined list of senders, or accepting messages from only authenticated senders. + # Whether the recipient's mailbox is restricted. For example, accepting messages from only a predefined list of senders, rejecting messages from a predefined list of senders, or accepting messages from only authenticated senders. delivery_restricted: Optional[bool] = None # The email address of the recipient to get mailtips for. email_address: Optional[EmailAddress] = None @@ -30,15 +30,15 @@ class MailTips(AdditionalDataHolder, BackedModel, Parsable): error: Optional[MailTipsError] = None # The number of external members if the recipient is a distribution list. external_member_count: Optional[int] = None - # Whether sending messages to the recipient requires approval. For example, if the recipient is a large distribution list and a moderator has been set up to approve messages sent to that distribution list, or if sending messages to a recipient requires approval of the recipient's manager. + # Whether sending messages to the recipient requires approval. For example, if the recipient is a large distribution list and a moderator is set up to approve messages sent to that distribution list, or if sending messages to a recipient requires approval of the recipient's manager. is_moderated: Optional[bool] = None # The mailbox full status of the recipient. mailbox_full: Optional[bool] = None - # The maximum message size that has been configured for the recipient's organization or mailbox. + # The maximum message size configured for the recipient's organization or mailbox. max_message_size: Optional[int] = None # The OdataType property odata_type: Optional[str] = None - # The scope of the recipient. Possible values are: none, internal, external, externalPartner, externalNonParther. For example, an administrator can set another organization to be its 'partner'. The scope is useful if an administrator wants certain mailtips to be accessible to certain scopes. It's also useful to senders to inform them that their message may leave the organization, helping them make the correct decisions about wording, tone and content. + # The scope of the recipient. Possible values are: none, internal, external, externalPartner, externalNonParther. For example, an administrator can set another organization to be its 'partner'. The scope is useful if an administrator wants certain mailtips to be accessible to certain scopes. It's also useful to senders to inform them that their message may leave the organization, helping them make the correct decisions about wording, tone, and content. recipient_scope: Optional[RecipientScopeType] = None # Recipients suggested based on previous contexts where they appear in the same message. recipient_suggestions: Optional[List[Recipient]] = None diff --git a/msgraph_beta/generated/models/mailbox_restore_artifact.py b/msgraph_beta/generated/models/mailbox_restore_artifact.py index a21529e9870..96aa40249d7 100644 --- a/msgraph_beta/generated/models/mailbox_restore_artifact.py +++ b/msgraph_beta/generated/models/mailbox_restore_artifact.py @@ -13,11 +13,11 @@ class MailboxRestoreArtifact(RestoreArtifactBase, Parsable): # The OdataType property odata_type: Optional[str] = None - # The new restored folder identifier for the user. + # The newly restored folder identifier for the user. restored_folder_id: Optional[str] = None # The new restored folder name. restored_folder_name: Optional[str] = None - # The restoredItemCount property + # The number of items that are being restored in the folder. restored_item_count: Optional[int] = None @staticmethod diff --git a/msgraph_beta/generated/models/networkaccess/connectivity.py b/msgraph_beta/generated/models/networkaccess/connectivity.py index 1e6a65e7915..bc0cd07689c 100644 --- a/msgraph_beta/generated/models/networkaccess/connectivity.py +++ b/msgraph_beta/generated/models/networkaccess/connectivity.py @@ -13,11 +13,11 @@ @dataclass class Connectivity(Entity, Parsable): - # Branches represent locations for connectivity. DEPRECATED AND TO BE RETIRED SOON. Use the remoteNetwork relationship and its associated APIs instead. + # The locations for connectivity. DEPRECATED AND TO BE RETIRED SOON. Use the remoteNetwork relationship and its associated APIs instead. branches: Optional[List[BranchSite]] = None # The OdataType property odata_type: Optional[str] = None - # Represent locations, such as branches, that are connected to Global Secure Access services through an IPsec tunnel. + # The locations, such as branches, that are connected to Global Secure Access services through an IPsec tunnel. remote_networks: Optional[List[RemoteNetwork]] = None # The webCategories property web_categories: Optional[List[WebCategory]] = None diff --git a/msgraph_beta/generated/models/networkaccess/profile.py b/msgraph_beta/generated/models/networkaccess/profile.py index beeaa1b7363..73aceecef2c 100644 --- a/msgraph_beta/generated/models/networkaccess/profile.py +++ b/msgraph_beta/generated/models/networkaccess/profile.py @@ -17,13 +17,13 @@ class Profile(Entity, Parsable): # Description. description: Optional[str] = None - # Profile last modified time. + # The date and time when the profile was last modified. last_modified_date_time: Optional[datetime.datetime] = None - # Profile name. + # The name of the profile. name: Optional[str] = None # The OdataType property odata_type: Optional[str] = None - # Traffic forwarding policies associated with this profile. + # The traffic forwarding policies associated with this profile. policies: Optional[List[PolicyLink]] = None # The state property state: Optional[Status] = None diff --git a/msgraph_beta/generated/models/news_link_page.py b/msgraph_beta/generated/models/news_link_page.py index 6cd0e73e9fb..417e331784c 100644 --- a/msgraph_beta/generated/models/news_link_page.py +++ b/msgraph_beta/generated/models/news_link_page.py @@ -11,11 +11,11 @@ @dataclass class NewsLinkPage(BaseSitePage, Parsable): - # The bannerImageWebUrl property + # A link to the banner image for the newsLinkPage. banner_image_web_url: Optional[str] = None - # The newsSharepointIds property + # The SharePoint IDs of the referenced news article if it's recognized as a SharePoint resource. Read-only. news_sharepoint_ids: Optional[SharepointIds] = None - # The newsWebUrl property + # The URL of the news article referenced by the newsLinkPage. It can be an external link. news_web_url: Optional[str] = None # The OdataType property odata_type: Optional[str] = None diff --git a/msgraph_beta/generated/models/on_attribute_collection_external_users_self_service_sign_up.py b/msgraph_beta/generated/models/on_attribute_collection_external_users_self_service_sign_up.py index db08b655085..93c2056944f 100644 --- a/msgraph_beta/generated/models/on_attribute_collection_external_users_self_service_sign_up.py +++ b/msgraph_beta/generated/models/on_attribute_collection_external_users_self_service_sign_up.py @@ -14,7 +14,7 @@ class OnAttributeCollectionExternalUsersSelfServiceSignUp(OnAttributeCollectionHandler, Parsable): # The OdataType property odata_type: Optional[str] = "#microsoft.graph.onAttributeCollectionExternalUsersSelfServiceSignUp" - # Required. The configuration for how attributes are displayed in the sign up experience defined by a user flow, like the externalUsersSelfServiceSignupEventsFlow, specifically on the attribute collection page. + # Required. The configuration for how attributes are displayed in the sign-up experience defined by a user flow, like the externalUsersSelfServiceSignupEventsFlow, specifically on the attribute collection page. attribute_collection_page: Optional[AuthenticationAttributeCollectionPage] = None # The attributes property attributes: Optional[List[IdentityUserFlowAttribute]] = None diff --git a/msgraph_beta/generated/models/on_interactive_auth_flow_start_listener.py b/msgraph_beta/generated/models/on_interactive_auth_flow_start_listener.py index b7477b8a867..4b185d549c1 100644 --- a/msgraph_beta/generated/models/on_interactive_auth_flow_start_listener.py +++ b/msgraph_beta/generated/models/on_interactive_auth_flow_start_listener.py @@ -13,7 +13,7 @@ class OnInteractiveAuthFlowStartListener(AuthenticationEventListener, Parsable): # The OdataType property odata_type: Optional[str] = "#microsoft.graph.onInteractiveAuthFlowStartListener" - # Required. Configuration for what to invoke if the event resolves to this listener. This lets us define potential handler configurations per-event. + # Required. Configuration for what to invoke if the event resolves to this listener. You can use this handler to define potential handler configurations for specific events. handler: Optional[OnInteractiveAuthFlowStartHandler] = None @staticmethod diff --git a/msgraph_beta/generated/models/one_drive_for_business_protection_policy.py b/msgraph_beta/generated/models/one_drive_for_business_protection_policy.py index 3a772badf8d..a2701654687 100644 --- a/msgraph_beta/generated/models/one_drive_for_business_protection_policy.py +++ b/msgraph_beta/generated/models/one_drive_for_business_protection_policy.py @@ -15,9 +15,9 @@ class OneDriveForBusinessProtectionPolicy(ProtectionPolicyBase, Parsable): # The OdataType property odata_type: Optional[str] = "#microsoft.graph.oneDriveForBusinessProtectionPolicy" - # Contains the details of the Onedrive for Business protection rule. + # Contains the details of the OneDrive for Work or School protection rule. drive_inclusion_rules: Optional[List[DriveProtectionRule]] = None - # Contains the protection units associated with a OneDrive for Business protection policy. + # Contains the protection units associated with a OneDrive for Work or School protection policy. drive_protection_units: Optional[List[DriveProtectionUnit]] = None # The driveProtectionUnitsBulkAdditionJobs property drive_protection_units_bulk_addition_jobs: Optional[List[DriveProtectionUnitsBulkAdditionJob]] = None diff --git a/msgraph_beta/generated/models/one_drive_for_business_restore_session.py b/msgraph_beta/generated/models/one_drive_for_business_restore_session.py index 23f80ce9190..ac64b134179 100644 --- a/msgraph_beta/generated/models/one_drive_for_business_restore_session.py +++ b/msgraph_beta/generated/models/one_drive_for_business_restore_session.py @@ -14,7 +14,7 @@ class OneDriveForBusinessRestoreSession(RestoreSessionBase, Parsable): # The OdataType property odata_type: Optional[str] = "#microsoft.graph.oneDriveForBusinessRestoreSession" - # A collection of restore points and destination details that can be used to restore a OneDrive for Business drive. + # A collection of restore points and destination details that can be used to restore a OneDrive for Work or School drive. drive_restore_artifacts: Optional[List[DriveRestoreArtifact]] = None # The driveRestoreArtifactsBulkAdditionRequests property drive_restore_artifacts_bulk_addition_requests: Optional[List[DriveRestoreArtifactsBulkAdditionRequest]] = None diff --git a/msgraph_beta/generated/models/onenote.py b/msgraph_beta/generated/models/onenote.py index 005ecbf5940..a250f0e305a 100644 --- a/msgraph_beta/generated/models/onenote.py +++ b/msgraph_beta/generated/models/onenote.py @@ -16,19 +16,19 @@ @dataclass class Onenote(Entity, Parsable): - # The collection of OneNote notebooks that are owned by the user or group. Read-only. Nullable. + # The collection of OneNote notebooks that the user or group owns. Read-only. Nullable. notebooks: Optional[List[Notebook]] = None # The OdataType property odata_type: Optional[str] = None # The status of OneNote operations. Getting an operations collection isn't supported, but you can get the status of long-running operations if the Operation-Location header is returned in the response. Read-only. Nullable. operations: Optional[List[OnenoteOperation]] = None - # The pages in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + # The pages in all OneNote notebooks that the user or group owns. Read-only. Nullable. pages: Optional[List[OnenotePage]] = None # The image and other file resources in OneNote pages. Getting a resources collection isn't supported, but you can get the binary content of a specific resource. Read-only. Nullable. resources: Optional[List[OnenoteResource]] = None - # The section groups in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + # The section groups in all OneNote notebooks that the user or group owns. Read-only. Nullable. section_groups: Optional[List[SectionGroup]] = None - # The sections in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + # The sections in all OneNote notebooks that the user or group owns. Read-only. Nullable. sections: Optional[List[OnenoteSection]] = None @staticmethod diff --git a/msgraph_beta/generated/models/restore_session_artifact_count.py b/msgraph_beta/generated/models/restore_session_artifact_count.py index e607e8bf5a2..37a2349d1e6 100644 --- a/msgraph_beta/generated/models/restore_session_artifact_count.py +++ b/msgraph_beta/generated/models/restore_session_artifact_count.py @@ -11,15 +11,15 @@ class RestoreSessionArtifactCount(AdditionalDataHolder, BackedModel, Parsable): # Stores additional data not described in the OpenAPI description found when deserializing. Can be used for serialization as well. additional_data: Dict[str, Any] = field(default_factory=dict) - # The completed property + # The number of artifacts whose restoration completed. completed: Optional[int] = None - # The failed property + # The number of artifacts whose restoration failed. failed: Optional[int] = None - # The inProgress property + # The number of artifacts whose restoration is in progress. in_progress: Optional[int] = None # The OdataType property odata_type: Optional[str] = None - # The total property + # The number of artifacts present in the restore session. total: Optional[int] = None @staticmethod diff --git a/msgraph_beta/generated/models/restore_session_base.py b/msgraph_beta/generated/models/restore_session_base.py index ec8d6d3b4c1..f4bcca30122 100644 --- a/msgraph_beta/generated/models/restore_session_base.py +++ b/msgraph_beta/generated/models/restore_session_base.py @@ -33,9 +33,9 @@ class RestoreSessionBase(Entity, Parsable): last_modified_date_time: Optional[datetime.datetime] = None # The OdataType property odata_type: Optional[str] = None - # The restoreJobType property + # Indicates whether the restore session was created normally or by a bulk job. restore_job_type: Optional[RestoreJobType] = None - # The restoreSessionArtifactCount property + # The number of metadata artifacts that belong to this restore session. restore_session_artifact_count: Optional[RestoreSessionArtifactCount] = None # Status of the restore session. The value is an aggregated status of the restored artifacts. The possible values are: draft, activating, active, completedWithError, completed, unknownFutureValue, failed. You must use the Prefer: include-unknown-enum-members request header to get the following value in this evolvable enum: failed. status: Optional[RestoreSessionStatus] = None diff --git a/msgraph_beta/generated/models/windows_domain_join_configuration.py b/msgraph_beta/generated/models/windows_domain_join_configuration.py index bee85f0b8df..f3c1bf08e60 100644 --- a/msgraph_beta/generated/models/windows_domain_join_configuration.py +++ b/msgraph_beta/generated/models/windows_domain_join_configuration.py @@ -21,7 +21,7 @@ class WindowsDomainJoinConfiguration(DeviceConfiguration, Parsable): computer_name_static_prefix: Optional[str] = None # Dynamically generated characters used as suffix for computer name. Valid values 3 to 14 computer_name_suffix_random_char_count: Optional[int] = None - # Reference to device configurations required for network connectivity + # Reference to device configurations required for network connectivity. This collection can contain a maximum of 2 elements. network_access_configurations: Optional[List[DeviceConfiguration]] = None # Organizational unit (OU) where the computer account will be created. If this parameter is NULL, the well known computer object container will be used as published in the domain. organizational_unit: Optional[str] = None diff --git a/msgraph_beta/generated/models/windows_universal_app_x_app_assignment_settings.py b/msgraph_beta/generated/models/windows_universal_app_x_app_assignment_settings.py index 226930a62ff..7ffe51c997b 100644 --- a/msgraph_beta/generated/models/windows_universal_app_x_app_assignment_settings.py +++ b/msgraph_beta/generated/models/windows_universal_app_x_app_assignment_settings.py @@ -15,7 +15,7 @@ class WindowsUniversalAppXAppAssignmentSettings(MobileAppAssignmentSettings, Par """ # The OdataType property odata_type: Optional[str] = "#microsoft.graph.windowsUniversalAppXAppAssignmentSettings" - # Whether or not to use device execution context for Windows Universal AppX mobile app. + # If true, uses device execution context for Windows Universal AppX mobile app. Device-context install is not allowed when this type of app is targeted with Available intent. Defaults to false. use_device_context: Optional[bool] = None @staticmethod diff --git a/msgraph_beta/generated/network_access/connectivity/branches/item/forwarding_profiles/item/policies/item/policy_link_item_request_builder.py b/msgraph_beta/generated/network_access/connectivity/branches/item/forwarding_profiles/item/policies/item/policy_link_item_request_builder.py index fdeeddfe55c..20dda829765 100644 --- a/msgraph_beta/generated/network_access/connectivity/branches/item/forwarding_profiles/item/policies/item/policy_link_item_request_builder.py +++ b/msgraph_beta/generated/network_access/connectivity/branches/item/forwarding_profiles/item/policies/item/policy_link_item_request_builder.py @@ -51,7 +51,7 @@ async def delete(self,request_configuration: Optional[RequestConfiguration[Query async def get(self,request_configuration: Optional[RequestConfiguration[PolicyLinkItemRequestBuilderGetQueryParameters]] = None) -> Optional[PolicyLink]: """ - Traffic forwarding policies associated with this profile. + The traffic forwarding policies associated with this profile. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[PolicyLink] """ @@ -108,7 +108,7 @@ def to_delete_request_information(self,request_configuration: Optional[RequestCo def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[PolicyLinkItemRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Traffic forwarding policies associated with this profile. + The traffic forwarding policies associated with this profile. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -164,7 +164,7 @@ class PolicyLinkItemRequestBuilderDeleteRequestConfiguration(RequestConfiguratio @dataclass class PolicyLinkItemRequestBuilderGetQueryParameters(): """ - Traffic forwarding policies associated with this profile. + The traffic forwarding policies associated with this profile. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/network_access/connectivity/branches/item/forwarding_profiles/item/policies/policies_request_builder.py b/msgraph_beta/generated/network_access/connectivity/branches/item/forwarding_profiles/item/policies/policies_request_builder.py index 9f7b48e6404..cb4957ca139 100644 --- a/msgraph_beta/generated/network_access/connectivity/branches/item/forwarding_profiles/item/policies/policies_request_builder.py +++ b/msgraph_beta/generated/network_access/connectivity/branches/item/forwarding_profiles/item/policies/policies_request_builder.py @@ -49,7 +49,7 @@ def by_policy_link_id(self,policy_link_id: str) -> PolicyLinkItemRequestBuilder: async def get(self,request_configuration: Optional[RequestConfiguration[PoliciesRequestBuilderGetQueryParameters]] = None) -> Optional[PolicyLinkCollectionResponse]: """ - Traffic forwarding policies associated with this profile. + The traffic forwarding policies associated with this profile. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[PolicyLinkCollectionResponse] """ @@ -94,7 +94,7 @@ async def post(self,body: PolicyLink, request_configuration: Optional[RequestCon def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[PoliciesRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Traffic forwarding policies associated with this profile. + The traffic forwarding policies associated with this profile. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -143,7 +143,7 @@ def count(self) -> CountRequestBuilder: @dataclass class PoliciesRequestBuilderGetQueryParameters(): """ - Traffic forwarding policies associated with this profile. + The traffic forwarding policies associated with this profile. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/network_access/connectivity/remote_networks/item/forwarding_profiles/item/policies/item/policy_link_item_request_builder.py b/msgraph_beta/generated/network_access/connectivity/remote_networks/item/forwarding_profiles/item/policies/item/policy_link_item_request_builder.py index 904211ab7c6..20254aaf6fb 100644 --- a/msgraph_beta/generated/network_access/connectivity/remote_networks/item/forwarding_profiles/item/policies/item/policy_link_item_request_builder.py +++ b/msgraph_beta/generated/network_access/connectivity/remote_networks/item/forwarding_profiles/item/policies/item/policy_link_item_request_builder.py @@ -50,7 +50,7 @@ async def delete(self,request_configuration: Optional[RequestConfiguration[Query async def get(self,request_configuration: Optional[RequestConfiguration[PolicyLinkItemRequestBuilderGetQueryParameters]] = None) -> Optional[PolicyLink]: """ - Traffic forwarding policies associated with this profile. + The traffic forwarding policies associated with this profile. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[PolicyLink] """ @@ -104,7 +104,7 @@ def to_delete_request_information(self,request_configuration: Optional[RequestCo def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[PolicyLinkItemRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Traffic forwarding policies associated with this profile. + The traffic forwarding policies associated with this profile. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -157,7 +157,7 @@ class PolicyLinkItemRequestBuilderDeleteRequestConfiguration(RequestConfiguratio @dataclass class PolicyLinkItemRequestBuilderGetQueryParameters(): """ - Traffic forwarding policies associated with this profile. + The traffic forwarding policies associated with this profile. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/network_access/connectivity/remote_networks/item/forwarding_profiles/item/policies/policies_request_builder.py b/msgraph_beta/generated/network_access/connectivity/remote_networks/item/forwarding_profiles/item/policies/policies_request_builder.py index f0231406125..d3744de6e13 100644 --- a/msgraph_beta/generated/network_access/connectivity/remote_networks/item/forwarding_profiles/item/policies/policies_request_builder.py +++ b/msgraph_beta/generated/network_access/connectivity/remote_networks/item/forwarding_profiles/item/policies/policies_request_builder.py @@ -48,7 +48,7 @@ def by_policy_link_id(self,policy_link_id: str) -> PolicyLinkItemRequestBuilder: async def get(self,request_configuration: Optional[RequestConfiguration[PoliciesRequestBuilderGetQueryParameters]] = None) -> Optional[PolicyLinkCollectionResponse]: """ - Traffic forwarding policies associated with this profile. + The traffic forwarding policies associated with this profile. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[PolicyLinkCollectionResponse] """ @@ -91,7 +91,7 @@ async def post(self,body: PolicyLink, request_configuration: Optional[RequestCon def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[PoliciesRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Traffic forwarding policies associated with this profile. + The traffic forwarding policies associated with this profile. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -137,7 +137,7 @@ def count(self) -> CountRequestBuilder: @dataclass class PoliciesRequestBuilderGetQueryParameters(): """ - Traffic forwarding policies associated with this profile. + The traffic forwarding policies associated with this profile. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/network_access/connectivity/remote_networks/item/remote_network_item_request_builder.py b/msgraph_beta/generated/network_access/connectivity/remote_networks/item/remote_network_item_request_builder.py index c4265dec32c..b1e47d42090 100644 --- a/msgraph_beta/generated/network_access/connectivity/remote_networks/item/remote_network_item_request_builder.py +++ b/msgraph_beta/generated/network_access/connectivity/remote_networks/item/remote_network_item_request_builder.py @@ -52,7 +52,7 @@ async def delete(self,request_configuration: Optional[RequestConfiguration[Query async def get(self,request_configuration: Optional[RequestConfiguration[RemoteNetworkItemRequestBuilderGetQueryParameters]] = None) -> Optional[RemoteNetwork]: """ - Represent locations, such as branches, that are connected to Global Secure Access services through an IPsec tunnel. + The locations, such as branches, that are connected to Global Secure Access services through an IPsec tunnel. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[RemoteNetwork] """ @@ -106,7 +106,7 @@ def to_delete_request_information(self,request_configuration: Optional[RequestCo def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[RemoteNetworkItemRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Represent locations, such as branches, that are connected to Global Secure Access services through an IPsec tunnel. + The locations, such as branches, that are connected to Global Secure Access services through an IPsec tunnel. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -177,7 +177,7 @@ class RemoteNetworkItemRequestBuilderDeleteRequestConfiguration(RequestConfigura @dataclass class RemoteNetworkItemRequestBuilderGetQueryParameters(): """ - Represent locations, such as branches, that are connected to Global Secure Access services through an IPsec tunnel. + The locations, such as branches, that are connected to Global Secure Access services through an IPsec tunnel. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/network_access/connectivity/remote_networks/remote_networks_request_builder.py b/msgraph_beta/generated/network_access/connectivity/remote_networks/remote_networks_request_builder.py index 7543b575821..e2bcf0db4ee 100644 --- a/msgraph_beta/generated/network_access/connectivity/remote_networks/remote_networks_request_builder.py +++ b/msgraph_beta/generated/network_access/connectivity/remote_networks/remote_networks_request_builder.py @@ -48,7 +48,7 @@ def by_remote_network_id(self,remote_network_id: str) -> RemoteNetworkItemReques async def get(self,request_configuration: Optional[RequestConfiguration[RemoteNetworksRequestBuilderGetQueryParameters]] = None) -> Optional[RemoteNetworkCollectionResponse]: """ - Represent locations, such as branches, that are connected to Global Secure Access services through an IPsec tunnel. + The locations, such as branches, that are connected to Global Secure Access services through an IPsec tunnel. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[RemoteNetworkCollectionResponse] """ @@ -92,7 +92,7 @@ async def post(self,body: RemoteNetwork, request_configuration: Optional[Request def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[RemoteNetworksRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Represent locations, such as branches, that are connected to Global Secure Access services through an IPsec tunnel. + The locations, such as branches, that are connected to Global Secure Access services through an IPsec tunnel. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -138,7 +138,7 @@ def count(self) -> CountRequestBuilder: @dataclass class RemoteNetworksRequestBuilderGetQueryParameters(): """ - Represent locations, such as branches, that are connected to Global Secure Access services through an IPsec tunnel. + The locations, such as branches, that are connected to Global Secure Access services through an IPsec tunnel. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/network_access/filtering_profiles/item/policies/item/policy_link_item_request_builder.py b/msgraph_beta/generated/network_access/filtering_profiles/item/policies/item/policy_link_item_request_builder.py index 9e0c4e762ab..bf2e73ab854 100644 --- a/msgraph_beta/generated/network_access/filtering_profiles/item/policies/item/policy_link_item_request_builder.py +++ b/msgraph_beta/generated/network_access/filtering_profiles/item/policies/item/policy_link_item_request_builder.py @@ -50,7 +50,7 @@ async def delete(self,request_configuration: Optional[RequestConfiguration[Query async def get(self,request_configuration: Optional[RequestConfiguration[PolicyLinkItemRequestBuilderGetQueryParameters]] = None) -> Optional[PolicyLink]: """ - Traffic forwarding policies associated with this profile. + The traffic forwarding policies associated with this profile. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[PolicyLink] """ @@ -104,7 +104,7 @@ def to_delete_request_information(self,request_configuration: Optional[RequestCo def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[PolicyLinkItemRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Traffic forwarding policies associated with this profile. + The traffic forwarding policies associated with this profile. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -157,7 +157,7 @@ class PolicyLinkItemRequestBuilderDeleteRequestConfiguration(RequestConfiguratio @dataclass class PolicyLinkItemRequestBuilderGetQueryParameters(): """ - Traffic forwarding policies associated with this profile. + The traffic forwarding policies associated with this profile. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/network_access/filtering_profiles/item/policies/policies_request_builder.py b/msgraph_beta/generated/network_access/filtering_profiles/item/policies/policies_request_builder.py index 513ef8580bc..c31dbada50a 100644 --- a/msgraph_beta/generated/network_access/filtering_profiles/item/policies/policies_request_builder.py +++ b/msgraph_beta/generated/network_access/filtering_profiles/item/policies/policies_request_builder.py @@ -48,7 +48,7 @@ def by_policy_link_id(self,policy_link_id: str) -> PolicyLinkItemRequestBuilder: async def get(self,request_configuration: Optional[RequestConfiguration[PoliciesRequestBuilderGetQueryParameters]] = None) -> Optional[PolicyLinkCollectionResponse]: """ - Traffic forwarding policies associated with this profile. + The traffic forwarding policies associated with this profile. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[PolicyLinkCollectionResponse] """ @@ -91,7 +91,7 @@ async def post(self,body: PolicyLink, request_configuration: Optional[RequestCon def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[PoliciesRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Traffic forwarding policies associated with this profile. + The traffic forwarding policies associated with this profile. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -137,7 +137,7 @@ def count(self) -> CountRequestBuilder: @dataclass class PoliciesRequestBuilderGetQueryParameters(): """ - Traffic forwarding policies associated with this profile. + The traffic forwarding policies associated with this profile. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/policies/cross_tenant_access_policy/partners/item/identity_synchronization/identity_synchronization_request_builder.py b/msgraph_beta/generated/policies/cross_tenant_access_policy/partners/item/identity_synchronization/identity_synchronization_request_builder.py index 37bf987051e..471fedcbf05 100644 --- a/msgraph_beta/generated/policies/cross_tenant_access_policy/partners/item/identity_synchronization/identity_synchronization_request_builder.py +++ b/msgraph_beta/generated/policies/cross_tenant_access_policy/partners/item/identity_synchronization/identity_synchronization_request_builder.py @@ -71,11 +71,11 @@ async def get(self,request_configuration: Optional[RequestConfiguration[Identity async def put(self,body: CrossTenantIdentitySyncPolicyPartner, request_configuration: Optional[RequestConfiguration[QueryParameters]] = None) -> Optional[CrossTenantIdentitySyncPolicyPartner]: """ - Create a cross-tenant user synchronization policy for a partner-specific configuration. + Update the user synchronization policy of a partner-specific configuration. param body: The request body param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[CrossTenantIdentitySyncPolicyPartner] - Find more info here: https://learn.microsoft.com/graph/api/crosstenantaccesspolicyconfigurationpartner-put-identitysynchronization?view=graph-rest-beta + Find more info here: https://learn.microsoft.com/graph/api/crosstenantidentitysyncpolicypartner-update?view=graph-rest-beta """ if body is None: raise TypeError("body cannot be null.") @@ -117,7 +117,7 @@ def to_get_request_information(self,request_configuration: Optional[RequestConfi def to_put_request_information(self,body: CrossTenantIdentitySyncPolicyPartner, request_configuration: Optional[RequestConfiguration[QueryParameters]] = None) -> RequestInformation: """ - Create a cross-tenant user synchronization policy for a partner-specific configuration. + Update the user synchronization policy of a partner-specific configuration. param body: The request body param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation diff --git a/msgraph_beta/generated/policies/federated_token_validation_policy/federated_token_validation_policy_request_builder.py b/msgraph_beta/generated/policies/federated_token_validation_policy/federated_token_validation_policy_request_builder.py index 151bd7a8a9d..a536656f835 100644 --- a/msgraph_beta/generated/policies/federated_token_validation_policy/federated_token_validation_policy_request_builder.py +++ b/msgraph_beta/generated/policies/federated_token_validation_policy/federated_token_validation_policy_request_builder.py @@ -49,10 +49,10 @@ async def delete(self,request_configuration: Optional[RequestConfiguration[Query async def get(self,request_configuration: Optional[RequestConfiguration[FederatedTokenValidationPolicyRequestBuilderGetQueryParameters]] = None) -> Optional[FederatedTokenValidationPolicy]: """ - Get a list of the federatedTokenValidationPolicy objects and their properties. + Read the properties and relationships of a federatedTokenValidationPolicy object. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[FederatedTokenValidationPolicy] - Find more info here: https://learn.microsoft.com/graph/api/policyroot-list-federatedtokenvalidationpolicy?view=graph-rest-beta + Find more info here: https://learn.microsoft.com/graph/api/federatedtokenvalidationpolicy-get?view=graph-rest-beta """ request_info = self.to_get_request_information( request_configuration @@ -105,7 +105,7 @@ def to_delete_request_information(self,request_configuration: Optional[RequestCo def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[FederatedTokenValidationPolicyRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Get a list of the federatedTokenValidationPolicy objects and their properties. + Read the properties and relationships of a federatedTokenValidationPolicy object. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -149,7 +149,7 @@ class FederatedTokenValidationPolicyRequestBuilderDeleteRequestConfiguration(Req @dataclass class FederatedTokenValidationPolicyRequestBuilderGetQueryParameters(): """ - Get a list of the federatedTokenValidationPolicy objects and their properties. + Read the properties and relationships of a federatedTokenValidationPolicy object. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/risk_detections/risk_detections_request_builder.py b/msgraph_beta/generated/risk_detections/risk_detections_request_builder.py index 4466cafff48..883bac77d83 100644 --- a/msgraph_beta/generated/risk_detections/risk_detections_request_builder.py +++ b/msgraph_beta/generated/risk_detections/risk_detections_request_builder.py @@ -47,10 +47,10 @@ def by_risk_detection_id(self,risk_detection_id: str) -> RiskDetectionItemReques async def get(self,request_configuration: Optional[RequestConfiguration[RiskDetectionsRequestBuilderGetQueryParameters]] = None) -> Optional[RiskDetectionCollectionResponse]: """ - Retrieve the properties of a riskDetection object. + Retrieve the properties of a collection of riskDetection objects. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[RiskDetectionCollectionResponse] - Find more info here: https://learn.microsoft.com/graph/api/riskdetection-get?view=graph-rest-beta + Find more info here: https://learn.microsoft.com/graph/api/riskdetection-list?view=graph-rest-beta """ request_info = self.to_get_request_information( request_configuration @@ -91,7 +91,7 @@ async def post(self,body: RiskDetection, request_configuration: Optional[Request def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[RiskDetectionsRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Retrieve the properties of a riskDetection object. + Retrieve the properties of a collection of riskDetection objects. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -128,7 +128,7 @@ def with_url(self,raw_url: str) -> RiskDetectionsRequestBuilder: @dataclass class RiskDetectionsRequestBuilderGetQueryParameters(): """ - Retrieve the properties of a riskDetection object. + Retrieve the properties of a collection of riskDetection objects. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/service_principals/item/claims_policy/claims_policy_request_builder.py b/msgraph_beta/generated/service_principals/item/claims_policy/claims_policy_request_builder.py index f49b628e551..1b136ab2ed1 100644 --- a/msgraph_beta/generated/service_principals/item/claims_policy/claims_policy_request_builder.py +++ b/msgraph_beta/generated/service_principals/item/claims_policy/claims_policy_request_builder.py @@ -52,11 +52,11 @@ async def get(self,request_configuration: Optional[RequestConfiguration[ClaimsPo async def patch(self,body: CustomClaimsPolicy, request_configuration: Optional[RequestConfiguration[QueryParameters]] = None) -> Optional[CustomClaimsPolicy]: """ - Create a new customClaimsPolicy object if it doesn't exist, or replace an existing one. + Update a customClaimsPolicy object. param body: The request body param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[CustomClaimsPolicy] - Find more info here: https://learn.microsoft.com/graph/api/serviceprincipal-put-claimspolicy?view=graph-rest-beta + Find more info here: https://learn.microsoft.com/graph/api/customclaimspolicy-update?view=graph-rest-beta """ if body is None: raise TypeError("body cannot be null.") @@ -76,11 +76,11 @@ async def patch(self,body: CustomClaimsPolicy, request_configuration: Optional[R async def put(self,body: CustomClaimsPolicy, request_configuration: Optional[RequestConfiguration[QueryParameters]] = None) -> Optional[CustomClaimsPolicy]: """ - Create a new customClaimsPolicy object if it doesn't exist, or replace an existing one. + Update a customClaimsPolicy object. param body: The request body param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[CustomClaimsPolicy] - Find more info here: https://learn.microsoft.com/graph/api/serviceprincipal-put-claimspolicy?view=graph-rest-beta + Find more info here: https://learn.microsoft.com/graph/api/customclaimspolicy-update?view=graph-rest-beta """ if body is None: raise TypeError("body cannot be null.") @@ -111,7 +111,7 @@ def to_get_request_information(self,request_configuration: Optional[RequestConfi def to_patch_request_information(self,body: CustomClaimsPolicy, request_configuration: Optional[RequestConfiguration[QueryParameters]] = None) -> RequestInformation: """ - Create a new customClaimsPolicy object if it doesn't exist, or replace an existing one. + Update a customClaimsPolicy object. param body: The request body param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation @@ -126,7 +126,7 @@ def to_patch_request_information(self,body: CustomClaimsPolicy, request_configur def to_put_request_information(self,body: CustomClaimsPolicy, request_configuration: Optional[RequestConfiguration[QueryParameters]] = None) -> RequestInformation: """ - Create a new customClaimsPolicy object if it doesn't exist, or replace an existing one. + Update a customClaimsPolicy object. param body: The request body param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation diff --git a/msgraph_beta/generated/sites/item/onenote/notebooks/item/notebook_item_request_builder.py b/msgraph_beta/generated/sites/item/onenote/notebooks/item/notebook_item_request_builder.py index 2899abe41f0..b0c7c387669 100644 --- a/msgraph_beta/generated/sites/item/onenote/notebooks/item/notebook_item_request_builder.py +++ b/msgraph_beta/generated/sites/item/onenote/notebooks/item/notebook_item_request_builder.py @@ -52,7 +52,7 @@ async def delete(self,request_configuration: Optional[RequestConfiguration[Query async def get(self,request_configuration: Optional[RequestConfiguration[NotebookItemRequestBuilderGetQueryParameters]] = None) -> Optional[Notebook]: """ - The collection of OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The collection of OneNote notebooks that the user or group owns. Read-only. Nullable. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[Notebook] """ @@ -106,7 +106,7 @@ def to_delete_request_information(self,request_configuration: Optional[RequestCo def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[NotebookItemRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - The collection of OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The collection of OneNote notebooks that the user or group owns. Read-only. Nullable. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -177,7 +177,7 @@ class NotebookItemRequestBuilderDeleteRequestConfiguration(RequestConfiguration[ @dataclass class NotebookItemRequestBuilderGetQueryParameters(): """ - The collection of OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The collection of OneNote notebooks that the user or group owns. Read-only. Nullable. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/sites/item/onenote/notebooks/notebooks_request_builder.py b/msgraph_beta/generated/sites/item/onenote/notebooks/notebooks_request_builder.py index 573e825e5c4..94e05742f2f 100644 --- a/msgraph_beta/generated/sites/item/onenote/notebooks/notebooks_request_builder.py +++ b/msgraph_beta/generated/sites/item/onenote/notebooks/notebooks_request_builder.py @@ -50,7 +50,7 @@ def by_notebook_id(self,notebook_id: str) -> NotebookItemRequestBuilder: async def get(self,request_configuration: Optional[RequestConfiguration[NotebooksRequestBuilderGetQueryParameters]] = None) -> Optional[NotebookCollectionResponse]: """ - The collection of OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The collection of OneNote notebooks that the user or group owns. Read-only. Nullable. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[NotebookCollectionResponse] """ @@ -105,7 +105,7 @@ async def post(self,body: Notebook, request_configuration: Optional[RequestConfi def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[NotebooksRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - The collection of OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The collection of OneNote notebooks that the user or group owns. Read-only. Nullable. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -160,7 +160,7 @@ def get_notebook_from_web_url(self) -> GetNotebookFromWebUrlRequestBuilder: @dataclass class NotebooksRequestBuilderGetQueryParameters(): """ - The collection of OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The collection of OneNote notebooks that the user or group owns. Read-only. Nullable. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/sites/item/onenote/pages/item/onenote_page_item_request_builder.py b/msgraph_beta/generated/sites/item/onenote/pages/item/onenote_page_item_request_builder.py index 92a1c91794f..33074ffa537 100644 --- a/msgraph_beta/generated/sites/item/onenote/pages/item/onenote_page_item_request_builder.py +++ b/msgraph_beta/generated/sites/item/onenote/pages/item/onenote_page_item_request_builder.py @@ -55,7 +55,7 @@ async def delete(self,request_configuration: Optional[RequestConfiguration[Query async def get(self,request_configuration: Optional[RequestConfiguration[OnenotePageItemRequestBuilderGetQueryParameters]] = None) -> Optional[OnenotePage]: """ - The pages in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The pages in all OneNote notebooks that the user or group owns. Read-only. Nullable. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[OnenotePage] """ @@ -109,7 +109,7 @@ def to_delete_request_information(self,request_configuration: Optional[RequestCo def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[OnenotePageItemRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - The pages in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The pages in all OneNote notebooks that the user or group owns. Read-only. Nullable. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -207,7 +207,7 @@ class OnenotePageItemRequestBuilderDeleteRequestConfiguration(RequestConfigurati @dataclass class OnenotePageItemRequestBuilderGetQueryParameters(): """ - The pages in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The pages in all OneNote notebooks that the user or group owns. Read-only. Nullable. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/sites/item/onenote/pages/pages_request_builder.py b/msgraph_beta/generated/sites/item/onenote/pages/pages_request_builder.py index 917b990b26b..3f58d53bd71 100644 --- a/msgraph_beta/generated/sites/item/onenote/pages/pages_request_builder.py +++ b/msgraph_beta/generated/sites/item/onenote/pages/pages_request_builder.py @@ -48,7 +48,7 @@ def by_onenote_page_id(self,onenote_page_id: str) -> OnenotePageItemRequestBuild async def get(self,request_configuration: Optional[RequestConfiguration[PagesRequestBuilderGetQueryParameters]] = None) -> Optional[OnenotePageCollectionResponse]: """ - The pages in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The pages in all OneNote notebooks that the user or group owns. Read-only. Nullable. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[OnenotePageCollectionResponse] """ @@ -91,7 +91,7 @@ async def post(self,body: OnenotePage, request_configuration: Optional[RequestCo def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[PagesRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - The pages in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The pages in all OneNote notebooks that the user or group owns. Read-only. Nullable. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -137,7 +137,7 @@ def count(self) -> CountRequestBuilder: @dataclass class PagesRequestBuilderGetQueryParameters(): """ - The pages in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The pages in all OneNote notebooks that the user or group owns. Read-only. Nullable. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/sites/item/onenote/section_groups/item/section_group_item_request_builder.py b/msgraph_beta/generated/sites/item/onenote/section_groups/item/section_group_item_request_builder.py index 8ea2cec370e..ee1fa84fbf9 100644 --- a/msgraph_beta/generated/sites/item/onenote/section_groups/item/section_group_item_request_builder.py +++ b/msgraph_beta/generated/sites/item/onenote/section_groups/item/section_group_item_request_builder.py @@ -53,7 +53,7 @@ async def delete(self,request_configuration: Optional[RequestConfiguration[Query async def get(self,request_configuration: Optional[RequestConfiguration[SectionGroupItemRequestBuilderGetQueryParameters]] = None) -> Optional[SectionGroup]: """ - The section groups in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The section groups in all OneNote notebooks that the user or group owns. Read-only. Nullable. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[SectionGroup] """ @@ -107,7 +107,7 @@ def to_delete_request_information(self,request_configuration: Optional[RequestCo def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[SectionGroupItemRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - The section groups in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The section groups in all OneNote notebooks that the user or group owns. Read-only. Nullable. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -187,7 +187,7 @@ class SectionGroupItemRequestBuilderDeleteRequestConfiguration(RequestConfigurat @dataclass class SectionGroupItemRequestBuilderGetQueryParameters(): """ - The section groups in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The section groups in all OneNote notebooks that the user or group owns. Read-only. Nullable. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/sites/item/onenote/section_groups/section_groups_request_builder.py b/msgraph_beta/generated/sites/item/onenote/section_groups/section_groups_request_builder.py index dd6ec31ec1a..802413fe716 100644 --- a/msgraph_beta/generated/sites/item/onenote/section_groups/section_groups_request_builder.py +++ b/msgraph_beta/generated/sites/item/onenote/section_groups/section_groups_request_builder.py @@ -48,7 +48,7 @@ def by_section_group_id(self,section_group_id: str) -> SectionGroupItemRequestBu async def get(self,request_configuration: Optional[RequestConfiguration[SectionGroupsRequestBuilderGetQueryParameters]] = None) -> Optional[SectionGroupCollectionResponse]: """ - The section groups in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The section groups in all OneNote notebooks that the user or group owns. Read-only. Nullable. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[SectionGroupCollectionResponse] """ @@ -91,7 +91,7 @@ async def post(self,body: SectionGroup, request_configuration: Optional[RequestC def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[SectionGroupsRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - The section groups in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The section groups in all OneNote notebooks that the user or group owns. Read-only. Nullable. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -137,7 +137,7 @@ def count(self) -> CountRequestBuilder: @dataclass class SectionGroupsRequestBuilderGetQueryParameters(): """ - The section groups in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The section groups in all OneNote notebooks that the user or group owns. Read-only. Nullable. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/sites/item/onenote/sections/item/onenote_section_item_request_builder.py b/msgraph_beta/generated/sites/item/onenote/sections/item/onenote_section_item_request_builder.py index dedbbb9caef..731f6a97e9a 100644 --- a/msgraph_beta/generated/sites/item/onenote/sections/item/onenote_section_item_request_builder.py +++ b/msgraph_beta/generated/sites/item/onenote/sections/item/onenote_section_item_request_builder.py @@ -54,7 +54,7 @@ async def delete(self,request_configuration: Optional[RequestConfiguration[Query async def get(self,request_configuration: Optional[RequestConfiguration[OnenoteSectionItemRequestBuilderGetQueryParameters]] = None) -> Optional[OnenoteSection]: """ - The sections in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The sections in all OneNote notebooks that the user or group owns. Read-only. Nullable. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[OnenoteSection] """ @@ -108,7 +108,7 @@ def to_delete_request_information(self,request_configuration: Optional[RequestCo def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[OnenoteSectionItemRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - The sections in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The sections in all OneNote notebooks that the user or group owns. Read-only. Nullable. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -197,7 +197,7 @@ class OnenoteSectionItemRequestBuilderDeleteRequestConfiguration(RequestConfigur @dataclass class OnenoteSectionItemRequestBuilderGetQueryParameters(): """ - The sections in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The sections in all OneNote notebooks that the user or group owns. Read-only. Nullable. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/sites/item/onenote/sections/sections_request_builder.py b/msgraph_beta/generated/sites/item/onenote/sections/sections_request_builder.py index ccaf6124a3e..fea686c967d 100644 --- a/msgraph_beta/generated/sites/item/onenote/sections/sections_request_builder.py +++ b/msgraph_beta/generated/sites/item/onenote/sections/sections_request_builder.py @@ -48,7 +48,7 @@ def by_onenote_section_id(self,onenote_section_id: str) -> OnenoteSectionItemReq async def get(self,request_configuration: Optional[RequestConfiguration[SectionsRequestBuilderGetQueryParameters]] = None) -> Optional[OnenoteSectionCollectionResponse]: """ - The sections in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The sections in all OneNote notebooks that the user or group owns. Read-only. Nullable. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[OnenoteSectionCollectionResponse] """ @@ -91,7 +91,7 @@ async def post(self,body: OnenoteSection, request_configuration: Optional[Reques def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[SectionsRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - The sections in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The sections in all OneNote notebooks that the user or group owns. Read-only. Nullable. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -137,7 +137,7 @@ def count(self) -> CountRequestBuilder: @dataclass class SectionsRequestBuilderGetQueryParameters(): """ - The sections in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The sections in all OneNote notebooks that the user or group owns. Read-only. Nullable. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/sites/item/pages/pages_request_builder.py b/msgraph_beta/generated/sites/item/pages/pages_request_builder.py index df5e6594f31..5054b7bc18f 100644 --- a/msgraph_beta/generated/sites/item/pages/pages_request_builder.py +++ b/msgraph_beta/generated/sites/item/pages/pages_request_builder.py @@ -70,11 +70,11 @@ async def get(self,request_configuration: Optional[RequestConfiguration[PagesReq async def post(self,body: BaseSitePage, request_configuration: Optional[RequestConfiguration[QueryParameters]] = None) -> Optional[BaseSitePage]: """ - Create a new sitePage in the site pages list in a site. + Create a new newsLinkPage in the site pages list of a site. param body: The request body param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[BaseSitePage] - Find more info here: https://learn.microsoft.com/graph/api/sitepage-create?view=graph-rest-beta + Find more info here: https://learn.microsoft.com/graph/api/newslinkpage-create?view=graph-rest-beta """ if body is None: raise TypeError("body cannot be null.") @@ -105,7 +105,7 @@ def to_get_request_information(self,request_configuration: Optional[RequestConfi def to_post_request_information(self,body: BaseSitePage, request_configuration: Optional[RequestConfiguration[QueryParameters]] = None) -> RequestInformation: """ - Create a new sitePage in the site pages list in a site. + Create a new newsLinkPage in the site pages list of a site. param body: The request body param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation diff --git a/msgraph_beta/generated/solutions/backup_restore/one_drive_for_business_protection_policies/item/drive_protection_units/item/drive_protection_unit_item_request_builder.py b/msgraph_beta/generated/solutions/backup_restore/one_drive_for_business_protection_policies/item/drive_protection_units/item/drive_protection_unit_item_request_builder.py index 0b5e742cb2e..9ad98c67d1c 100644 --- a/msgraph_beta/generated/solutions/backup_restore/one_drive_for_business_protection_policies/item/drive_protection_units/item/drive_protection_unit_item_request_builder.py +++ b/msgraph_beta/generated/solutions/backup_restore/one_drive_for_business_protection_policies/item/drive_protection_units/item/drive_protection_unit_item_request_builder.py @@ -31,7 +31,7 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def get(self,request_configuration: Optional[RequestConfiguration[DriveProtectionUnitItemRequestBuilderGetQueryParameters]] = None) -> Optional[DriveProtectionUnit]: """ - Contains the protection units associated with a OneDrive for Business protection policy. + Contains the protection units associated with a OneDrive for Work or School protection policy. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[DriveProtectionUnit] """ @@ -51,7 +51,7 @@ async def get(self,request_configuration: Optional[RequestConfiguration[DrivePro def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[DriveProtectionUnitItemRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Contains the protection units associated with a OneDrive for Business protection policy. + Contains the protection units associated with a OneDrive for Work or School protection policy. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -73,7 +73,7 @@ def with_url(self,raw_url: str) -> DriveProtectionUnitItemRequestBuilder: @dataclass class DriveProtectionUnitItemRequestBuilderGetQueryParameters(): """ - Contains the protection units associated with a OneDrive for Business protection policy. + Contains the protection units associated with a OneDrive for Work or School protection policy. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/solutions/backup_restore/one_drive_for_business_restore_sessions/item/drive_restore_artifacts/item/drive_restore_artifact_item_request_builder.py b/msgraph_beta/generated/solutions/backup_restore/one_drive_for_business_restore_sessions/item/drive_restore_artifacts/item/drive_restore_artifact_item_request_builder.py index bd04b568d23..436f1c7f9a9 100644 --- a/msgraph_beta/generated/solutions/backup_restore/one_drive_for_business_restore_sessions/item/drive_restore_artifacts/item/drive_restore_artifact_item_request_builder.py +++ b/msgraph_beta/generated/solutions/backup_restore/one_drive_for_business_restore_sessions/item/drive_restore_artifacts/item/drive_restore_artifact_item_request_builder.py @@ -50,7 +50,7 @@ async def delete(self,request_configuration: Optional[RequestConfiguration[Query async def get(self,request_configuration: Optional[RequestConfiguration[DriveRestoreArtifactItemRequestBuilderGetQueryParameters]] = None) -> Optional[DriveRestoreArtifact]: """ - A collection of restore points and destination details that can be used to restore a OneDrive for Business drive. + A collection of restore points and destination details that can be used to restore a OneDrive for Work or School drive. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[DriveRestoreArtifact] """ @@ -104,7 +104,7 @@ def to_delete_request_information(self,request_configuration: Optional[RequestCo def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[DriveRestoreArtifactItemRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - A collection of restore points and destination details that can be used to restore a OneDrive for Business drive. + A collection of restore points and destination details that can be used to restore a OneDrive for Work or School drive. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -157,7 +157,7 @@ class DriveRestoreArtifactItemRequestBuilderDeleteRequestConfiguration(RequestCo @dataclass class DriveRestoreArtifactItemRequestBuilderGetQueryParameters(): """ - A collection of restore points and destination details that can be used to restore a OneDrive for Business drive. + A collection of restore points and destination details that can be used to restore a OneDrive for Work or School drive. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/teams/item/channels/item/messages/messages_request_builder.py b/msgraph_beta/generated/teams/item/channels/item/messages/messages_request_builder.py index 2efe674e56c..c4358f72b8b 100644 --- a/msgraph_beta/generated/teams/item/channels/item/messages/messages_request_builder.py +++ b/msgraph_beta/generated/teams/item/channels/item/messages/messages_request_builder.py @@ -70,11 +70,11 @@ async def get(self,request_configuration: Optional[RequestConfiguration[Messages async def post(self,body: ChatMessage, request_configuration: Optional[RequestConfiguration[QueryParameters]] = None) -> Optional[ChatMessage]: """ - Send a new chatMessage in the specified channel. + Send a new chatMessage in the specified channel or a chat. param body: The request body param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[ChatMessage] - Find more info here: https://learn.microsoft.com/graph/api/channel-post-messages?view=graph-rest-beta + Find more info here: https://learn.microsoft.com/graph/api/chatmessage-post?view=graph-rest-beta """ if body is None: raise TypeError("body cannot be null.") @@ -105,7 +105,7 @@ def to_get_request_information(self,request_configuration: Optional[RequestConfi def to_post_request_information(self,body: ChatMessage, request_configuration: Optional[RequestConfiguration[QueryParameters]] = None) -> RequestInformation: """ - Send a new chatMessage in the specified channel. + Send a new chatMessage in the specified channel or a chat. param body: The request body param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation diff --git a/msgraph_beta/generated/teams/item/schedule/open_shifts/open_shifts_request_builder.py b/msgraph_beta/generated/teams/item/schedule/open_shifts/open_shifts_request_builder.py index f25e67e97d5..f09ca40a973 100644 --- a/msgraph_beta/generated/teams/item/schedule/open_shifts/open_shifts_request_builder.py +++ b/msgraph_beta/generated/teams/item/schedule/open_shifts/open_shifts_request_builder.py @@ -69,7 +69,7 @@ async def get(self,request_configuration: Optional[RequestConfiguration[OpenShif async def post(self,body: OpenShift, request_configuration: Optional[RequestConfiguration[QueryParameters]] = None) -> Optional[OpenShift]: """ - Create an instance of an openshift object. + Create an instance of an openShift object. param body: The request body param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[OpenShift] @@ -104,7 +104,7 @@ def to_get_request_information(self,request_configuration: Optional[RequestConfi def to_post_request_information(self,body: OpenShift, request_configuration: Optional[RequestConfiguration[QueryParameters]] = None) -> RequestInformation: """ - Create an instance of an openshift object. + Create an instance of an openShift object. param body: The request body param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation diff --git a/msgraph_beta/generated/tenant_relationships/managed_tenants/management_actions/item/microsoft_graph_managed_tenants_apply/microsoft_graph_managed_tenants_apply_request_builder.py b/msgraph_beta/generated/tenant_relationships/managed_tenants/management_actions/item/microsoft_graph_managed_tenants_apply/microsoft_graph_managed_tenants_apply_request_builder.py index fb97bb40af0..a511a5a7b11 100644 --- a/msgraph_beta/generated/tenant_relationships/managed_tenants/management_actions/item/microsoft_graph_managed_tenants_apply/microsoft_graph_managed_tenants_apply_request_builder.py +++ b/msgraph_beta/generated/tenant_relationships/managed_tenants/management_actions/item/microsoft_graph_managed_tenants_apply/microsoft_graph_managed_tenants_apply_request_builder.py @@ -32,7 +32,7 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def post(self,body: ApplyPostRequestBody, request_configuration: Optional[RequestConfiguration[QueryParameters]] = None) -> Optional[ManagementActionDeploymentStatus]: """ - Applies a management action against a specific managed tenant. By performing this operation the appropriate configurations will be made and policies created. As example when applying the require multifactor authentication for admins management action creates a Microsoft Entra Conditional Access policy that requires multifactor authentication for all users that have been assigned an administrative directory role. + Applies a management action against a specific managed tenant. Performing this operation makes the appropriate configurations and creates the appropriate policies. For example, when applying the required multifactor authentication for admins, management action creates a Microsoft Entra Conditional Access policy that requires multifactor authentication for all users that are assigned an administrative directory role. param body: The request body param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[ManagementActionDeploymentStatus] @@ -56,7 +56,7 @@ async def post(self,body: ApplyPostRequestBody, request_configuration: Optional[ def to_post_request_information(self,body: ApplyPostRequestBody, request_configuration: Optional[RequestConfiguration[QueryParameters]] = None) -> RequestInformation: """ - Applies a management action against a specific managed tenant. By performing this operation the appropriate configurations will be made and policies created. As example when applying the require multifactor authentication for admins management action creates a Microsoft Entra Conditional Access policy that requires multifactor authentication for all users that have been assigned an administrative directory role. + Applies a management action against a specific managed tenant. Performing this operation makes the appropriate configurations and creates the appropriate policies. For example, when applying the required multifactor authentication for admins, management action creates a Microsoft Entra Conditional Access policy that requires multifactor authentication for all users that are assigned an administrative directory role. param body: The request body param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation diff --git a/msgraph_beta/generated/tenant_relationships/multi_tenant_organization/join_request/join_request_request_builder.py b/msgraph_beta/generated/tenant_relationships/multi_tenant_organization/join_request/join_request_request_builder.py index ca4caad6050..cbad355430c 100644 --- a/msgraph_beta/generated/tenant_relationships/multi_tenant_organization/join_request/join_request_request_builder.py +++ b/msgraph_beta/generated/tenant_relationships/multi_tenant_organization/join_request/join_request_request_builder.py @@ -52,7 +52,7 @@ async def get(self,request_configuration: Optional[RequestConfiguration[JoinRequ async def patch(self,body: MultiTenantOrganizationJoinRequestRecord, request_configuration: Optional[RequestConfiguration[QueryParameters]] = None) -> Optional[MultiTenantOrganizationJoinRequestRecord]: """ - Join a multi-tenant organization, after the owner of the multi-tenant organization has added your tenant to the multi-tenant organization as pending. Before a tenant added to a multi-tenant organization can participate in the multi-tenant organization, the administrator of the joining tenant must submit a join request. To allow for asynchronous processing, you must wait a minimum of 2 hours between creation and joining a multi-tenant organization. Furthermore, to allow for asynchronous processing, you must wait up to 4 hours before joining a multi-tenant organization is completed. + Join a multi-tenant organization, after the owner of the multi-tenant organization adds your tenant to the multi-tenant organization as pending. Before a tenant added to a multi-tenant organization can participate in the multi-tenant organization, the administrator of the joining tenant must submit a join request. To allow for asynchronous processing, you must wait a minimum of 2 hours between creation and joining a multi-tenant organization. Furthermore, to allow for asynchronous processing, you must wait up to 4 hours before joining a multi-tenant organization is completed. param body: The request body param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[MultiTenantOrganizationJoinRequestRecord] @@ -87,7 +87,7 @@ def to_get_request_information(self,request_configuration: Optional[RequestConfi def to_patch_request_information(self,body: MultiTenantOrganizationJoinRequestRecord, request_configuration: Optional[RequestConfiguration[QueryParameters]] = None) -> RequestInformation: """ - Join a multi-tenant organization, after the owner of the multi-tenant organization has added your tenant to the multi-tenant organization as pending. Before a tenant added to a multi-tenant organization can participate in the multi-tenant organization, the administrator of the joining tenant must submit a join request. To allow for asynchronous processing, you must wait a minimum of 2 hours between creation and joining a multi-tenant organization. Furthermore, to allow for asynchronous processing, you must wait up to 4 hours before joining a multi-tenant organization is completed. + Join a multi-tenant organization, after the owner of the multi-tenant organization adds your tenant to the multi-tenant organization as pending. Before a tenant added to a multi-tenant organization can participate in the multi-tenant organization, the administrator of the joining tenant must submit a join request. To allow for asynchronous processing, you must wait a minimum of 2 hours between creation and joining a multi-tenant organization. Furthermore, to allow for asynchronous processing, you must wait up to 4 hours before joining a multi-tenant organization is completed. param body: The request body param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation diff --git a/msgraph_beta/generated/tenant_relationships/multi_tenant_organization/multi_tenant_organization_request_builder.py b/msgraph_beta/generated/tenant_relationships/multi_tenant_organization/multi_tenant_organization_request_builder.py index 960f06f36b2..ccb1517cfdf 100644 --- a/msgraph_beta/generated/tenant_relationships/multi_tenant_organization/multi_tenant_organization_request_builder.py +++ b/msgraph_beta/generated/tenant_relationships/multi_tenant_organization/multi_tenant_organization_request_builder.py @@ -54,11 +54,11 @@ async def get(self,request_configuration: Optional[RequestConfiguration[MultiTen async def patch(self,body: MultiTenantOrganization, request_configuration: Optional[RequestConfiguration[QueryParameters]] = None) -> Optional[MultiTenantOrganization]: """ - Update the properties of a multi-tenant organization. + Create a new multi-tenant organization. By default, the creator tenant becomes an owner tenant upon successful creation. Only owner tenants can manage a multi-tenant organization. To allow for asynchronous processing, you must wait a minimum of 2 hours between creation and joining a multi-tenant organization. param body: The request body param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[MultiTenantOrganization] - Find more info here: https://learn.microsoft.com/graph/api/multitenantorganization-update?view=graph-rest-beta + Find more info here: https://learn.microsoft.com/graph/api/tenantrelationship-put-multitenantorganization?view=graph-rest-beta """ if body is None: raise TypeError("body cannot be null.") @@ -89,7 +89,7 @@ def to_get_request_information(self,request_configuration: Optional[RequestConfi def to_patch_request_information(self,body: MultiTenantOrganization, request_configuration: Optional[RequestConfiguration[QueryParameters]] = None) -> RequestInformation: """ - Update the properties of a multi-tenant organization. + Create a new multi-tenant organization. By default, the creator tenant becomes an owner tenant upon successful creation. Only owner tenants can manage a multi-tenant organization. To allow for asynchronous processing, you must wait a minimum of 2 hours between creation and joining a multi-tenant organization. param body: The request body param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation diff --git a/msgraph_beta/generated/users/item/authentication/hardware_oath_methods/assign_and_activate/assign_and_activate_request_builder.py b/msgraph_beta/generated/users/item/authentication/hardware_oath_methods/assign_and_activate/assign_and_activate_request_builder.py index c811276acc8..f6e432c0ea8 100644 --- a/msgraph_beta/generated/users/item/authentication/hardware_oath_methods/assign_and_activate/assign_and_activate_request_builder.py +++ b/msgraph_beta/generated/users/item/authentication/hardware_oath_methods/assign_and_activate/assign_and_activate_request_builder.py @@ -31,10 +31,11 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def post(self,body: AssignAndActivatePostRequestBody, request_configuration: Optional[RequestConfiguration[QueryParameters]] = None) -> None: """ - Invoke action assignAndActivate + Assign and activate a hardware token at the same time. This operation requires the device ID to activate it. param body: The request body param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: None + Find more info here: https://learn.microsoft.com/graph/api/hardwareoathauthenticationmethod-assignandactivate?view=graph-rest-beta """ if body is None: raise TypeError("body cannot be null.") @@ -52,7 +53,7 @@ async def post(self,body: AssignAndActivatePostRequestBody, request_configuratio def to_post_request_information(self,body: AssignAndActivatePostRequestBody, request_configuration: Optional[RequestConfiguration[QueryParameters]] = None) -> RequestInformation: """ - Invoke action assignAndActivate + Assign and activate a hardware token at the same time. This operation requires the device ID to activate it. param body: The request body param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation diff --git a/msgraph_beta/generated/users/item/authentication/hardware_oath_methods/assign_and_activate_by_serial_number/assign_and_activate_by_serial_number_request_builder.py b/msgraph_beta/generated/users/item/authentication/hardware_oath_methods/assign_and_activate_by_serial_number/assign_and_activate_by_serial_number_request_builder.py index ffae26cc441..040830d6323 100644 --- a/msgraph_beta/generated/users/item/authentication/hardware_oath_methods/assign_and_activate_by_serial_number/assign_and_activate_by_serial_number_request_builder.py +++ b/msgraph_beta/generated/users/item/authentication/hardware_oath_methods/assign_and_activate_by_serial_number/assign_and_activate_by_serial_number_request_builder.py @@ -31,10 +31,11 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def post(self,body: AssignAndActivateBySerialNumberPostRequestBody, request_configuration: Optional[RequestConfiguration[QueryParameters]] = None) -> None: """ - Invoke action assignAndActivateBySerialNumber + Assign and activate a hardware token at the same time by hardware token serial number. param body: The request body param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: None + Find more info here: https://learn.microsoft.com/graph/api/hardwareoathauthenticationmethod-assignandactivatebyserialnumber?view=graph-rest-beta """ if body is None: raise TypeError("body cannot be null.") @@ -52,7 +53,7 @@ async def post(self,body: AssignAndActivateBySerialNumberPostRequestBody, reques def to_post_request_information(self,body: AssignAndActivateBySerialNumberPostRequestBody, request_configuration: Optional[RequestConfiguration[QueryParameters]] = None) -> RequestInformation: """ - Invoke action assignAndActivateBySerialNumber + Assign and activate a hardware token at the same time by hardware token serial number. param body: The request body param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation diff --git a/msgraph_beta/generated/users/item/authentication/hardware_oath_methods/hardware_oath_methods_request_builder.py b/msgraph_beta/generated/users/item/authentication/hardware_oath_methods/hardware_oath_methods_request_builder.py index 744352cdbca..be5fd8437d8 100644 --- a/msgraph_beta/generated/users/item/authentication/hardware_oath_methods/hardware_oath_methods_request_builder.py +++ b/msgraph_beta/generated/users/item/authentication/hardware_oath_methods/hardware_oath_methods_request_builder.py @@ -50,7 +50,7 @@ def by_hardware_oath_authentication_method_id(self,hardware_oath_authentication_ async def get(self,request_configuration: Optional[RequestConfiguration[HardwareOathMethodsRequestBuilderGetQueryParameters]] = None) -> Optional[HardwareOathAuthenticationMethodCollectionResponse]: """ - Get hardwareOathMethods from users + The hardware OATH time-based one-time password (TOTP) devices assigned to a user for authentication. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[HardwareOathAuthenticationMethodCollectionResponse] """ @@ -93,7 +93,7 @@ async def post(self,body: HardwareOathAuthenticationMethod, request_configuratio def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[HardwareOathMethodsRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Get hardwareOathMethods from users + The hardware OATH time-based one-time password (TOTP) devices assigned to a user for authentication. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -157,7 +157,7 @@ def count(self) -> CountRequestBuilder: @dataclass class HardwareOathMethodsRequestBuilderGetQueryParameters(): """ - Get hardwareOathMethods from users + The hardware OATH time-based one-time password (TOTP) devices assigned to a user for authentication. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/users/item/authentication/hardware_oath_methods/item/activate/activate_request_builder.py b/msgraph_beta/generated/users/item/authentication/hardware_oath_methods/item/activate/activate_request_builder.py index 7fef4096c65..cd68802499c 100644 --- a/msgraph_beta/generated/users/item/authentication/hardware_oath_methods/item/activate/activate_request_builder.py +++ b/msgraph_beta/generated/users/item/authentication/hardware_oath_methods/item/activate/activate_request_builder.py @@ -31,10 +31,11 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def post(self,body: ActivatePostRequestBody, request_configuration: Optional[RequestConfiguration[QueryParameters]] = None) -> None: """ - Invoke action activate + Activate a hardware OATH token that is already assigned to a user. A user can self-activate their token or an admin can activate for a user. param body: The request body param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: None + Find more info here: https://learn.microsoft.com/graph/api/hardwareoathauthenticationmethod-activate?view=graph-rest-beta """ if body is None: raise TypeError("body cannot be null.") @@ -52,7 +53,7 @@ async def post(self,body: ActivatePostRequestBody, request_configuration: Option def to_post_request_information(self,body: ActivatePostRequestBody, request_configuration: Optional[RequestConfiguration[QueryParameters]] = None) -> RequestInformation: """ - Invoke action activate + Activate a hardware OATH token that is already assigned to a user. A user can self-activate their token or an admin can activate for a user. param body: The request body param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation diff --git a/msgraph_beta/generated/users/item/authentication/hardware_oath_methods/item/deactivate/deactivate_request_builder.py b/msgraph_beta/generated/users/item/authentication/hardware_oath_methods/item/deactivate/deactivate_request_builder.py index 971858709af..5a9715f6928 100644 --- a/msgraph_beta/generated/users/item/authentication/hardware_oath_methods/item/deactivate/deactivate_request_builder.py +++ b/msgraph_beta/generated/users/item/authentication/hardware_oath_methods/item/deactivate/deactivate_request_builder.py @@ -30,9 +30,10 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def post(self,request_configuration: Optional[RequestConfiguration[QueryParameters]] = None) -> None: """ - Invoke action deactivate + Deactive a hardware OATH token. It remains assigned to a user. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: None + Find more info here: https://learn.microsoft.com/graph/api/hardwareoathauthenticationmethod-deactivate?view=graph-rest-beta """ request_info = self.to_post_request_information( request_configuration @@ -48,7 +49,7 @@ async def post(self,request_configuration: Optional[RequestConfiguration[QueryPa def to_post_request_information(self,request_configuration: Optional[RequestConfiguration[QueryParameters]] = None) -> RequestInformation: """ - Invoke action deactivate + Deactive a hardware OATH token. It remains assigned to a user. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ diff --git a/msgraph_beta/generated/users/item/authentication/hardware_oath_methods/item/device/assign_to/assign_to_request_builder.py b/msgraph_beta/generated/users/item/authentication/hardware_oath_methods/item/device/assign_to/assign_to_request_builder.py index 9ef75b39f03..f73d129bb4b 100644 --- a/msgraph_beta/generated/users/item/authentication/hardware_oath_methods/item/device/assign_to/assign_to_request_builder.py +++ b/msgraph_beta/generated/users/item/authentication/hardware_oath_methods/item/device/assign_to/assign_to_request_builder.py @@ -33,7 +33,7 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def get(self,request_configuration: Optional[RequestConfiguration[AssignToRequestBuilderGetQueryParameters]] = None) -> Optional[User]: """ - Get assignTo from users + Assign the hardware OATH token to a user. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[User] """ @@ -53,7 +53,7 @@ async def get(self,request_configuration: Optional[RequestConfiguration[AssignTo def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[AssignToRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Get assignTo from users + Assign the hardware OATH token to a user. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -93,7 +93,7 @@ def service_provisioning_errors(self) -> ServiceProvisioningErrorsRequestBuilder @dataclass class AssignToRequestBuilderGetQueryParameters(): """ - Get assignTo from users + Assign the hardware OATH token to a user. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/users/item/authentication/hardware_oath_methods/item/device/device_request_builder.py b/msgraph_beta/generated/users/item/authentication/hardware_oath_methods/item/device/device_request_builder.py index 81f53dbd6d3..78f4f3f8e44 100644 --- a/msgraph_beta/generated/users/item/authentication/hardware_oath_methods/item/device/device_request_builder.py +++ b/msgraph_beta/generated/users/item/authentication/hardware_oath_methods/item/device/device_request_builder.py @@ -51,7 +51,7 @@ async def delete(self,request_configuration: Optional[RequestConfiguration[Query async def get(self,request_configuration: Optional[RequestConfiguration[DeviceRequestBuilderGetQueryParameters]] = None) -> Optional[HardwareOathTokenAuthenticationMethodDevice]: """ - Get device from users + Exposes the hardware OATH method in the directory. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[HardwareOathTokenAuthenticationMethodDevice] """ @@ -105,7 +105,7 @@ def to_delete_request_information(self,request_configuration: Optional[RequestCo def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[DeviceRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Get device from users + Exposes the hardware OATH method in the directory. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -167,7 +167,7 @@ class DeviceRequestBuilderDeleteRequestConfiguration(RequestConfiguration[QueryP @dataclass class DeviceRequestBuilderGetQueryParameters(): """ - Get device from users + Exposes the hardware OATH method in the directory. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/users/item/authentication/hardware_oath_methods/item/device/hardware_oath_devices/hardware_oath_devices_request_builder.py b/msgraph_beta/generated/users/item/authentication/hardware_oath_methods/item/device/hardware_oath_devices/hardware_oath_devices_request_builder.py index f5894f881d9..0a2fd383ef3 100644 --- a/msgraph_beta/generated/users/item/authentication/hardware_oath_methods/item/device/hardware_oath_devices/hardware_oath_devices_request_builder.py +++ b/msgraph_beta/generated/users/item/authentication/hardware_oath_methods/item/device/hardware_oath_devices/hardware_oath_devices_request_builder.py @@ -48,7 +48,7 @@ def by_hardware_oath_token_authentication_method_device_id(self,hardware_oath_to async def get(self,request_configuration: Optional[RequestConfiguration[HardwareOathDevicesRequestBuilderGetQueryParameters]] = None) -> Optional[HardwareOathTokenAuthenticationMethodDeviceCollectionResponse]: """ - Get hardwareOathDevices from users + Exposes the hardware OATH method in the directory. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[HardwareOathTokenAuthenticationMethodDeviceCollectionResponse] """ @@ -91,7 +91,7 @@ async def post(self,body: HardwareOathTokenAuthenticationMethodDevice, request_c def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[HardwareOathDevicesRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Get hardwareOathDevices from users + Exposes the hardware OATH method in the directory. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -137,7 +137,7 @@ def count(self) -> CountRequestBuilder: @dataclass class HardwareOathDevicesRequestBuilderGetQueryParameters(): """ - Get hardwareOathDevices from users + Exposes the hardware OATH method in the directory. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/users/item/authentication/hardware_oath_methods/item/device/hardware_oath_devices/item/assign_to/assign_to_request_builder.py b/msgraph_beta/generated/users/item/authentication/hardware_oath_methods/item/device/hardware_oath_devices/item/assign_to/assign_to_request_builder.py index 3b8b2eefa50..c44810036de 100644 --- a/msgraph_beta/generated/users/item/authentication/hardware_oath_methods/item/device/hardware_oath_devices/item/assign_to/assign_to_request_builder.py +++ b/msgraph_beta/generated/users/item/authentication/hardware_oath_methods/item/device/hardware_oath_devices/item/assign_to/assign_to_request_builder.py @@ -33,7 +33,7 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def get(self,request_configuration: Optional[RequestConfiguration[AssignToRequestBuilderGetQueryParameters]] = None) -> Optional[User]: """ - Get assignTo from users + Assign the hardware OATH token to a user. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[User] """ @@ -53,7 +53,7 @@ async def get(self,request_configuration: Optional[RequestConfiguration[AssignTo def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[AssignToRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Get assignTo from users + Assign the hardware OATH token to a user. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -93,7 +93,7 @@ def service_provisioning_errors(self) -> ServiceProvisioningErrorsRequestBuilder @dataclass class AssignToRequestBuilderGetQueryParameters(): """ - Get assignTo from users + Assign the hardware OATH token to a user. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/users/item/authentication/hardware_oath_methods/item/device/hardware_oath_devices/item/hardware_oath_token_authentication_method_device_item_request_builder.py b/msgraph_beta/generated/users/item/authentication/hardware_oath_methods/item/device/hardware_oath_devices/item/hardware_oath_token_authentication_method_device_item_request_builder.py index 4e38459fe1c..10d0b6e3905 100644 --- a/msgraph_beta/generated/users/item/authentication/hardware_oath_methods/item/device/hardware_oath_devices/item/hardware_oath_token_authentication_method_device_item_request_builder.py +++ b/msgraph_beta/generated/users/item/authentication/hardware_oath_methods/item/device/hardware_oath_devices/item/hardware_oath_token_authentication_method_device_item_request_builder.py @@ -50,7 +50,7 @@ async def delete(self,request_configuration: Optional[RequestConfiguration[Query async def get(self,request_configuration: Optional[RequestConfiguration[HardwareOathTokenAuthenticationMethodDeviceItemRequestBuilderGetQueryParameters]] = None) -> Optional[HardwareOathTokenAuthenticationMethodDevice]: """ - Get hardwareOathDevices from users + Exposes the hardware OATH method in the directory. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[HardwareOathTokenAuthenticationMethodDevice] """ @@ -104,7 +104,7 @@ def to_delete_request_information(self,request_configuration: Optional[RequestCo def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[HardwareOathTokenAuthenticationMethodDeviceItemRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Get hardwareOathDevices from users + Exposes the hardware OATH method in the directory. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -157,7 +157,7 @@ class HardwareOathTokenAuthenticationMethodDeviceItemRequestBuilderDeleteRequest @dataclass class HardwareOathTokenAuthenticationMethodDeviceItemRequestBuilderGetQueryParameters(): """ - Get hardwareOathDevices from users + Exposes the hardware OATH method in the directory. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/users/item/authentication/hardware_oath_methods/item/hardware_oath_authentication_method_item_request_builder.py b/msgraph_beta/generated/users/item/authentication/hardware_oath_methods/item/hardware_oath_authentication_method_item_request_builder.py index c5340202d71..391f8da1eb4 100644 --- a/msgraph_beta/generated/users/item/authentication/hardware_oath_methods/item/hardware_oath_authentication_method_item_request_builder.py +++ b/msgraph_beta/generated/users/item/authentication/hardware_oath_methods/item/hardware_oath_authentication_method_item_request_builder.py @@ -52,7 +52,7 @@ async def delete(self,request_configuration: Optional[RequestConfiguration[Query async def get(self,request_configuration: Optional[RequestConfiguration[HardwareOathAuthenticationMethodItemRequestBuilderGetQueryParameters]] = None) -> Optional[HardwareOathAuthenticationMethod]: """ - Get hardwareOathMethods from users + The hardware OATH time-based one-time password (TOTP) devices assigned to a user for authentication. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[HardwareOathAuthenticationMethod] """ @@ -83,7 +83,7 @@ def to_delete_request_information(self,request_configuration: Optional[RequestCo def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[HardwareOathAuthenticationMethodItemRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Get hardwareOathMethods from users + The hardware OATH time-based one-time password (TOTP) devices assigned to a user for authentication. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -139,7 +139,7 @@ class HardwareOathAuthenticationMethodItemRequestBuilderDeleteRequestConfigurati @dataclass class HardwareOathAuthenticationMethodItemRequestBuilderGetQueryParameters(): """ - Get hardwareOathMethods from users + The hardware OATH time-based one-time password (TOTP) devices assigned to a user for authentication. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/users/item/calendar/calendar_view/delta/delta_request_builder.py b/msgraph_beta/generated/users/item/calendar/calendar_view/delta/delta_request_builder.py index bf3d6bacdb7..2b3d679f5cc 100644 --- a/msgraph_beta/generated/users/item/calendar/calendar_view/delta/delta_request_builder.py +++ b/msgraph_beta/generated/users/item/calendar/calendar_view/delta/delta_request_builder.py @@ -31,7 +31,7 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def get(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> Optional[DeltaGetResponse]: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[DeltaGetResponse] Find more info here: https://learn.microsoft.com/graph/api/event-delta?view=graph-rest-beta @@ -52,7 +52,7 @@ async def get(self,request_configuration: Optional[RequestConfiguration[DeltaReq def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -74,7 +74,7 @@ def with_url(self,raw_url: str) -> DeltaRequestBuilder: @dataclass class DeltaRequestBuilderGetQueryParameters(): """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/users/item/calendar/calendar_view/item/exception_occurrences/delta/delta_request_builder.py b/msgraph_beta/generated/users/item/calendar/calendar_view/item/exception_occurrences/delta/delta_request_builder.py index e2819f20427..9ff05efc949 100644 --- a/msgraph_beta/generated/users/item/calendar/calendar_view/item/exception_occurrences/delta/delta_request_builder.py +++ b/msgraph_beta/generated/users/item/calendar/calendar_view/item/exception_occurrences/delta/delta_request_builder.py @@ -31,7 +31,7 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def get(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> Optional[DeltaGetResponse]: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[DeltaGetResponse] Find more info here: https://learn.microsoft.com/graph/api/event-delta?view=graph-rest-beta @@ -52,7 +52,7 @@ async def get(self,request_configuration: Optional[RequestConfiguration[DeltaReq def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -74,7 +74,7 @@ def with_url(self,raw_url: str) -> DeltaRequestBuilder: @dataclass class DeltaRequestBuilderGetQueryParameters(): """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/users/item/calendar/calendar_view/item/exception_occurrences/item/instances/delta/delta_request_builder.py b/msgraph_beta/generated/users/item/calendar/calendar_view/item/exception_occurrences/item/instances/delta/delta_request_builder.py index 3a866f78cad..1ed3264b0a5 100644 --- a/msgraph_beta/generated/users/item/calendar/calendar_view/item/exception_occurrences/item/instances/delta/delta_request_builder.py +++ b/msgraph_beta/generated/users/item/calendar/calendar_view/item/exception_occurrences/item/instances/delta/delta_request_builder.py @@ -31,7 +31,7 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def get(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> Optional[DeltaGetResponse]: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[DeltaGetResponse] Find more info here: https://learn.microsoft.com/graph/api/event-delta?view=graph-rest-beta @@ -52,7 +52,7 @@ async def get(self,request_configuration: Optional[RequestConfiguration[DeltaReq def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -74,7 +74,7 @@ def with_url(self,raw_url: str) -> DeltaRequestBuilder: @dataclass class DeltaRequestBuilderGetQueryParameters(): """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/users/item/calendar/calendar_view/item/instances/delta/delta_request_builder.py b/msgraph_beta/generated/users/item/calendar/calendar_view/item/instances/delta/delta_request_builder.py index 947d44a0632..75c9dfe7d96 100644 --- a/msgraph_beta/generated/users/item/calendar/calendar_view/item/instances/delta/delta_request_builder.py +++ b/msgraph_beta/generated/users/item/calendar/calendar_view/item/instances/delta/delta_request_builder.py @@ -31,7 +31,7 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def get(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> Optional[DeltaGetResponse]: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[DeltaGetResponse] Find more info here: https://learn.microsoft.com/graph/api/event-delta?view=graph-rest-beta @@ -52,7 +52,7 @@ async def get(self,request_configuration: Optional[RequestConfiguration[DeltaReq def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -74,7 +74,7 @@ def with_url(self,raw_url: str) -> DeltaRequestBuilder: @dataclass class DeltaRequestBuilderGetQueryParameters(): """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/users/item/calendar/calendar_view/item/instances/item/exception_occurrences/delta/delta_request_builder.py b/msgraph_beta/generated/users/item/calendar/calendar_view/item/instances/item/exception_occurrences/delta/delta_request_builder.py index 39827f6e0ca..3307f757a17 100644 --- a/msgraph_beta/generated/users/item/calendar/calendar_view/item/instances/item/exception_occurrences/delta/delta_request_builder.py +++ b/msgraph_beta/generated/users/item/calendar/calendar_view/item/instances/item/exception_occurrences/delta/delta_request_builder.py @@ -31,7 +31,7 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def get(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> Optional[DeltaGetResponse]: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[DeltaGetResponse] Find more info here: https://learn.microsoft.com/graph/api/event-delta?view=graph-rest-beta @@ -52,7 +52,7 @@ async def get(self,request_configuration: Optional[RequestConfiguration[DeltaReq def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -74,7 +74,7 @@ def with_url(self,raw_url: str) -> DeltaRequestBuilder: @dataclass class DeltaRequestBuilderGetQueryParameters(): """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/users/item/calendar/events/delta/delta_request_builder.py b/msgraph_beta/generated/users/item/calendar/events/delta/delta_request_builder.py index 0b67686d017..fcfcde6ef7f 100644 --- a/msgraph_beta/generated/users/item/calendar/events/delta/delta_request_builder.py +++ b/msgraph_beta/generated/users/item/calendar/events/delta/delta_request_builder.py @@ -31,7 +31,7 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def get(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> Optional[DeltaGetResponse]: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[DeltaGetResponse] Find more info here: https://learn.microsoft.com/graph/api/event-delta?view=graph-rest-beta @@ -52,7 +52,7 @@ async def get(self,request_configuration: Optional[RequestConfiguration[DeltaReq def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -74,7 +74,7 @@ def with_url(self,raw_url: str) -> DeltaRequestBuilder: @dataclass class DeltaRequestBuilderGetQueryParameters(): """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/users/item/calendar/events/item/exception_occurrences/delta/delta_request_builder.py b/msgraph_beta/generated/users/item/calendar/events/item/exception_occurrences/delta/delta_request_builder.py index 702a51a89fc..cec62d88fcb 100644 --- a/msgraph_beta/generated/users/item/calendar/events/item/exception_occurrences/delta/delta_request_builder.py +++ b/msgraph_beta/generated/users/item/calendar/events/item/exception_occurrences/delta/delta_request_builder.py @@ -31,7 +31,7 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def get(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> Optional[DeltaGetResponse]: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[DeltaGetResponse] Find more info here: https://learn.microsoft.com/graph/api/event-delta?view=graph-rest-beta @@ -52,7 +52,7 @@ async def get(self,request_configuration: Optional[RequestConfiguration[DeltaReq def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -74,7 +74,7 @@ def with_url(self,raw_url: str) -> DeltaRequestBuilder: @dataclass class DeltaRequestBuilderGetQueryParameters(): """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/users/item/calendar/events/item/exception_occurrences/item/instances/delta/delta_request_builder.py b/msgraph_beta/generated/users/item/calendar/events/item/exception_occurrences/item/instances/delta/delta_request_builder.py index 02e6040e481..cbdeb0b0290 100644 --- a/msgraph_beta/generated/users/item/calendar/events/item/exception_occurrences/item/instances/delta/delta_request_builder.py +++ b/msgraph_beta/generated/users/item/calendar/events/item/exception_occurrences/item/instances/delta/delta_request_builder.py @@ -31,7 +31,7 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def get(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> Optional[DeltaGetResponse]: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[DeltaGetResponse] Find more info here: https://learn.microsoft.com/graph/api/event-delta?view=graph-rest-beta @@ -52,7 +52,7 @@ async def get(self,request_configuration: Optional[RequestConfiguration[DeltaReq def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -74,7 +74,7 @@ def with_url(self,raw_url: str) -> DeltaRequestBuilder: @dataclass class DeltaRequestBuilderGetQueryParameters(): """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/users/item/calendar/events/item/instances/delta/delta_request_builder.py b/msgraph_beta/generated/users/item/calendar/events/item/instances/delta/delta_request_builder.py index a518ab6780e..236e5896835 100644 --- a/msgraph_beta/generated/users/item/calendar/events/item/instances/delta/delta_request_builder.py +++ b/msgraph_beta/generated/users/item/calendar/events/item/instances/delta/delta_request_builder.py @@ -31,7 +31,7 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def get(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> Optional[DeltaGetResponse]: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[DeltaGetResponse] Find more info here: https://learn.microsoft.com/graph/api/event-delta?view=graph-rest-beta @@ -52,7 +52,7 @@ async def get(self,request_configuration: Optional[RequestConfiguration[DeltaReq def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -74,7 +74,7 @@ def with_url(self,raw_url: str) -> DeltaRequestBuilder: @dataclass class DeltaRequestBuilderGetQueryParameters(): """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/users/item/calendar/events/item/instances/item/exception_occurrences/delta/delta_request_builder.py b/msgraph_beta/generated/users/item/calendar/events/item/instances/item/exception_occurrences/delta/delta_request_builder.py index 4440fc4cc70..a9f7bc77cec 100644 --- a/msgraph_beta/generated/users/item/calendar/events/item/instances/item/exception_occurrences/delta/delta_request_builder.py +++ b/msgraph_beta/generated/users/item/calendar/events/item/instances/item/exception_occurrences/delta/delta_request_builder.py @@ -31,7 +31,7 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def get(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> Optional[DeltaGetResponse]: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[DeltaGetResponse] Find more info here: https://learn.microsoft.com/graph/api/event-delta?view=graph-rest-beta @@ -52,7 +52,7 @@ async def get(self,request_configuration: Optional[RequestConfiguration[DeltaReq def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -74,7 +74,7 @@ def with_url(self,raw_url: str) -> DeltaRequestBuilder: @dataclass class DeltaRequestBuilderGetQueryParameters(): """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/users/item/calendar_groups/item/calendars/item/calendar_view/delta/delta_request_builder.py b/msgraph_beta/generated/users/item/calendar_groups/item/calendars/item/calendar_view/delta/delta_request_builder.py index 9868140a213..50886fbb92c 100644 --- a/msgraph_beta/generated/users/item/calendar_groups/item/calendars/item/calendar_view/delta/delta_request_builder.py +++ b/msgraph_beta/generated/users/item/calendar_groups/item/calendars/item/calendar_view/delta/delta_request_builder.py @@ -31,7 +31,7 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def get(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> Optional[DeltaGetResponse]: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[DeltaGetResponse] Find more info here: https://learn.microsoft.com/graph/api/event-delta?view=graph-rest-beta @@ -52,7 +52,7 @@ async def get(self,request_configuration: Optional[RequestConfiguration[DeltaReq def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -74,7 +74,7 @@ def with_url(self,raw_url: str) -> DeltaRequestBuilder: @dataclass class DeltaRequestBuilderGetQueryParameters(): """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/users/item/calendar_groups/item/calendars/item/calendar_view/item/exception_occurrences/delta/delta_request_builder.py b/msgraph_beta/generated/users/item/calendar_groups/item/calendars/item/calendar_view/item/exception_occurrences/delta/delta_request_builder.py index 45498f99c32..748bb865333 100644 --- a/msgraph_beta/generated/users/item/calendar_groups/item/calendars/item/calendar_view/item/exception_occurrences/delta/delta_request_builder.py +++ b/msgraph_beta/generated/users/item/calendar_groups/item/calendars/item/calendar_view/item/exception_occurrences/delta/delta_request_builder.py @@ -31,7 +31,7 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def get(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> Optional[DeltaGetResponse]: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[DeltaGetResponse] Find more info here: https://learn.microsoft.com/graph/api/event-delta?view=graph-rest-beta @@ -52,7 +52,7 @@ async def get(self,request_configuration: Optional[RequestConfiguration[DeltaReq def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -74,7 +74,7 @@ def with_url(self,raw_url: str) -> DeltaRequestBuilder: @dataclass class DeltaRequestBuilderGetQueryParameters(): """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/users/item/calendar_groups/item/calendars/item/calendar_view/item/exception_occurrences/item/instances/delta/delta_request_builder.py b/msgraph_beta/generated/users/item/calendar_groups/item/calendars/item/calendar_view/item/exception_occurrences/item/instances/delta/delta_request_builder.py index 24e8921b39a..b0e036d1753 100644 --- a/msgraph_beta/generated/users/item/calendar_groups/item/calendars/item/calendar_view/item/exception_occurrences/item/instances/delta/delta_request_builder.py +++ b/msgraph_beta/generated/users/item/calendar_groups/item/calendars/item/calendar_view/item/exception_occurrences/item/instances/delta/delta_request_builder.py @@ -31,7 +31,7 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def get(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> Optional[DeltaGetResponse]: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[DeltaGetResponse] Find more info here: https://learn.microsoft.com/graph/api/event-delta?view=graph-rest-beta @@ -52,7 +52,7 @@ async def get(self,request_configuration: Optional[RequestConfiguration[DeltaReq def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -74,7 +74,7 @@ def with_url(self,raw_url: str) -> DeltaRequestBuilder: @dataclass class DeltaRequestBuilderGetQueryParameters(): """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/users/item/calendar_groups/item/calendars/item/calendar_view/item/instances/delta/delta_request_builder.py b/msgraph_beta/generated/users/item/calendar_groups/item/calendars/item/calendar_view/item/instances/delta/delta_request_builder.py index 3b26eb565a2..89634a8a8f7 100644 --- a/msgraph_beta/generated/users/item/calendar_groups/item/calendars/item/calendar_view/item/instances/delta/delta_request_builder.py +++ b/msgraph_beta/generated/users/item/calendar_groups/item/calendars/item/calendar_view/item/instances/delta/delta_request_builder.py @@ -31,7 +31,7 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def get(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> Optional[DeltaGetResponse]: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[DeltaGetResponse] Find more info here: https://learn.microsoft.com/graph/api/event-delta?view=graph-rest-beta @@ -52,7 +52,7 @@ async def get(self,request_configuration: Optional[RequestConfiguration[DeltaReq def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -74,7 +74,7 @@ def with_url(self,raw_url: str) -> DeltaRequestBuilder: @dataclass class DeltaRequestBuilderGetQueryParameters(): """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/users/item/calendar_groups/item/calendars/item/calendar_view/item/instances/item/exception_occurrences/delta/delta_request_builder.py b/msgraph_beta/generated/users/item/calendar_groups/item/calendars/item/calendar_view/item/instances/item/exception_occurrences/delta/delta_request_builder.py index 59589b49d9e..09e2654a705 100644 --- a/msgraph_beta/generated/users/item/calendar_groups/item/calendars/item/calendar_view/item/instances/item/exception_occurrences/delta/delta_request_builder.py +++ b/msgraph_beta/generated/users/item/calendar_groups/item/calendars/item/calendar_view/item/instances/item/exception_occurrences/delta/delta_request_builder.py @@ -31,7 +31,7 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def get(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> Optional[DeltaGetResponse]: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[DeltaGetResponse] Find more info here: https://learn.microsoft.com/graph/api/event-delta?view=graph-rest-beta @@ -52,7 +52,7 @@ async def get(self,request_configuration: Optional[RequestConfiguration[DeltaReq def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -74,7 +74,7 @@ def with_url(self,raw_url: str) -> DeltaRequestBuilder: @dataclass class DeltaRequestBuilderGetQueryParameters(): """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/users/item/calendar_groups/item/calendars/item/events/delta/delta_request_builder.py b/msgraph_beta/generated/users/item/calendar_groups/item/calendars/item/events/delta/delta_request_builder.py index e5ecf7b34dc..7ca900cb0e6 100644 --- a/msgraph_beta/generated/users/item/calendar_groups/item/calendars/item/events/delta/delta_request_builder.py +++ b/msgraph_beta/generated/users/item/calendar_groups/item/calendars/item/events/delta/delta_request_builder.py @@ -31,7 +31,7 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def get(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> Optional[DeltaGetResponse]: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[DeltaGetResponse] Find more info here: https://learn.microsoft.com/graph/api/event-delta?view=graph-rest-beta @@ -52,7 +52,7 @@ async def get(self,request_configuration: Optional[RequestConfiguration[DeltaReq def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -74,7 +74,7 @@ def with_url(self,raw_url: str) -> DeltaRequestBuilder: @dataclass class DeltaRequestBuilderGetQueryParameters(): """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/users/item/calendar_groups/item/calendars/item/events/item/exception_occurrences/delta/delta_request_builder.py b/msgraph_beta/generated/users/item/calendar_groups/item/calendars/item/events/item/exception_occurrences/delta/delta_request_builder.py index 6722b56efe5..d48b91332cc 100644 --- a/msgraph_beta/generated/users/item/calendar_groups/item/calendars/item/events/item/exception_occurrences/delta/delta_request_builder.py +++ b/msgraph_beta/generated/users/item/calendar_groups/item/calendars/item/events/item/exception_occurrences/delta/delta_request_builder.py @@ -31,7 +31,7 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def get(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> Optional[DeltaGetResponse]: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[DeltaGetResponse] Find more info here: https://learn.microsoft.com/graph/api/event-delta?view=graph-rest-beta @@ -52,7 +52,7 @@ async def get(self,request_configuration: Optional[RequestConfiguration[DeltaReq def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -74,7 +74,7 @@ def with_url(self,raw_url: str) -> DeltaRequestBuilder: @dataclass class DeltaRequestBuilderGetQueryParameters(): """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/users/item/calendar_groups/item/calendars/item/events/item/exception_occurrences/item/instances/delta/delta_request_builder.py b/msgraph_beta/generated/users/item/calendar_groups/item/calendars/item/events/item/exception_occurrences/item/instances/delta/delta_request_builder.py index c14b94ddde3..fac09da17fd 100644 --- a/msgraph_beta/generated/users/item/calendar_groups/item/calendars/item/events/item/exception_occurrences/item/instances/delta/delta_request_builder.py +++ b/msgraph_beta/generated/users/item/calendar_groups/item/calendars/item/events/item/exception_occurrences/item/instances/delta/delta_request_builder.py @@ -31,7 +31,7 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def get(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> Optional[DeltaGetResponse]: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[DeltaGetResponse] Find more info here: https://learn.microsoft.com/graph/api/event-delta?view=graph-rest-beta @@ -52,7 +52,7 @@ async def get(self,request_configuration: Optional[RequestConfiguration[DeltaReq def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -74,7 +74,7 @@ def with_url(self,raw_url: str) -> DeltaRequestBuilder: @dataclass class DeltaRequestBuilderGetQueryParameters(): """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/users/item/calendar_groups/item/calendars/item/events/item/instances/delta/delta_request_builder.py b/msgraph_beta/generated/users/item/calendar_groups/item/calendars/item/events/item/instances/delta/delta_request_builder.py index 2e91c4ad7a0..d62909a9ef8 100644 --- a/msgraph_beta/generated/users/item/calendar_groups/item/calendars/item/events/item/instances/delta/delta_request_builder.py +++ b/msgraph_beta/generated/users/item/calendar_groups/item/calendars/item/events/item/instances/delta/delta_request_builder.py @@ -31,7 +31,7 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def get(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> Optional[DeltaGetResponse]: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[DeltaGetResponse] Find more info here: https://learn.microsoft.com/graph/api/event-delta?view=graph-rest-beta @@ -52,7 +52,7 @@ async def get(self,request_configuration: Optional[RequestConfiguration[DeltaReq def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -74,7 +74,7 @@ def with_url(self,raw_url: str) -> DeltaRequestBuilder: @dataclass class DeltaRequestBuilderGetQueryParameters(): """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/users/item/calendar_groups/item/calendars/item/events/item/instances/item/exception_occurrences/delta/delta_request_builder.py b/msgraph_beta/generated/users/item/calendar_groups/item/calendars/item/events/item/instances/item/exception_occurrences/delta/delta_request_builder.py index 74f77a99880..b986d00b062 100644 --- a/msgraph_beta/generated/users/item/calendar_groups/item/calendars/item/events/item/instances/item/exception_occurrences/delta/delta_request_builder.py +++ b/msgraph_beta/generated/users/item/calendar_groups/item/calendars/item/events/item/instances/item/exception_occurrences/delta/delta_request_builder.py @@ -31,7 +31,7 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def get(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> Optional[DeltaGetResponse]: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[DeltaGetResponse] Find more info here: https://learn.microsoft.com/graph/api/event-delta?view=graph-rest-beta @@ -52,7 +52,7 @@ async def get(self,request_configuration: Optional[RequestConfiguration[DeltaReq def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -74,7 +74,7 @@ def with_url(self,raw_url: str) -> DeltaRequestBuilder: @dataclass class DeltaRequestBuilderGetQueryParameters(): """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/users/item/calendar_view/delta/delta_request_builder.py b/msgraph_beta/generated/users/item/calendar_view/delta/delta_request_builder.py index 810524ee535..31980350835 100644 --- a/msgraph_beta/generated/users/item/calendar_view/delta/delta_request_builder.py +++ b/msgraph_beta/generated/users/item/calendar_view/delta/delta_request_builder.py @@ -31,7 +31,7 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def get(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> Optional[DeltaGetResponse]: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[DeltaGetResponse] Find more info here: https://learn.microsoft.com/graph/api/event-delta?view=graph-rest-beta @@ -52,7 +52,7 @@ async def get(self,request_configuration: Optional[RequestConfiguration[DeltaReq def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -74,7 +74,7 @@ def with_url(self,raw_url: str) -> DeltaRequestBuilder: @dataclass class DeltaRequestBuilderGetQueryParameters(): """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/users/item/calendar_view/item/exception_occurrences/delta/delta_request_builder.py b/msgraph_beta/generated/users/item/calendar_view/item/exception_occurrences/delta/delta_request_builder.py index 084b716d5f5..67888a051e3 100644 --- a/msgraph_beta/generated/users/item/calendar_view/item/exception_occurrences/delta/delta_request_builder.py +++ b/msgraph_beta/generated/users/item/calendar_view/item/exception_occurrences/delta/delta_request_builder.py @@ -31,7 +31,7 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def get(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> Optional[DeltaGetResponse]: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[DeltaGetResponse] Find more info here: https://learn.microsoft.com/graph/api/event-delta?view=graph-rest-beta @@ -52,7 +52,7 @@ async def get(self,request_configuration: Optional[RequestConfiguration[DeltaReq def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -74,7 +74,7 @@ def with_url(self,raw_url: str) -> DeltaRequestBuilder: @dataclass class DeltaRequestBuilderGetQueryParameters(): """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/users/item/calendar_view/item/exception_occurrences/item/instances/delta/delta_request_builder.py b/msgraph_beta/generated/users/item/calendar_view/item/exception_occurrences/item/instances/delta/delta_request_builder.py index c21783eb887..c0b06b40407 100644 --- a/msgraph_beta/generated/users/item/calendar_view/item/exception_occurrences/item/instances/delta/delta_request_builder.py +++ b/msgraph_beta/generated/users/item/calendar_view/item/exception_occurrences/item/instances/delta/delta_request_builder.py @@ -31,7 +31,7 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def get(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> Optional[DeltaGetResponse]: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[DeltaGetResponse] Find more info here: https://learn.microsoft.com/graph/api/event-delta?view=graph-rest-beta @@ -52,7 +52,7 @@ async def get(self,request_configuration: Optional[RequestConfiguration[DeltaReq def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -74,7 +74,7 @@ def with_url(self,raw_url: str) -> DeltaRequestBuilder: @dataclass class DeltaRequestBuilderGetQueryParameters(): """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/users/item/calendar_view/item/instances/delta/delta_request_builder.py b/msgraph_beta/generated/users/item/calendar_view/item/instances/delta/delta_request_builder.py index 0f7862ff09d..71a44a12a95 100644 --- a/msgraph_beta/generated/users/item/calendar_view/item/instances/delta/delta_request_builder.py +++ b/msgraph_beta/generated/users/item/calendar_view/item/instances/delta/delta_request_builder.py @@ -31,7 +31,7 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def get(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> Optional[DeltaGetResponse]: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[DeltaGetResponse] Find more info here: https://learn.microsoft.com/graph/api/event-delta?view=graph-rest-beta @@ -52,7 +52,7 @@ async def get(self,request_configuration: Optional[RequestConfiguration[DeltaReq def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -74,7 +74,7 @@ def with_url(self,raw_url: str) -> DeltaRequestBuilder: @dataclass class DeltaRequestBuilderGetQueryParameters(): """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/users/item/calendar_view/item/instances/item/exception_occurrences/delta/delta_request_builder.py b/msgraph_beta/generated/users/item/calendar_view/item/instances/item/exception_occurrences/delta/delta_request_builder.py index 1e0a9e5eb2f..852a6e2e2eb 100644 --- a/msgraph_beta/generated/users/item/calendar_view/item/instances/item/exception_occurrences/delta/delta_request_builder.py +++ b/msgraph_beta/generated/users/item/calendar_view/item/instances/item/exception_occurrences/delta/delta_request_builder.py @@ -31,7 +31,7 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def get(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> Optional[DeltaGetResponse]: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[DeltaGetResponse] Find more info here: https://learn.microsoft.com/graph/api/event-delta?view=graph-rest-beta @@ -52,7 +52,7 @@ async def get(self,request_configuration: Optional[RequestConfiguration[DeltaReq def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -74,7 +74,7 @@ def with_url(self,raw_url: str) -> DeltaRequestBuilder: @dataclass class DeltaRequestBuilderGetQueryParameters(): """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/users/item/calendars/item/calendar_view/delta/delta_request_builder.py b/msgraph_beta/generated/users/item/calendars/item/calendar_view/delta/delta_request_builder.py index d4c9c25b2ba..b7430360d46 100644 --- a/msgraph_beta/generated/users/item/calendars/item/calendar_view/delta/delta_request_builder.py +++ b/msgraph_beta/generated/users/item/calendars/item/calendar_view/delta/delta_request_builder.py @@ -31,7 +31,7 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def get(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> Optional[DeltaGetResponse]: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[DeltaGetResponse] Find more info here: https://learn.microsoft.com/graph/api/event-delta?view=graph-rest-beta @@ -52,7 +52,7 @@ async def get(self,request_configuration: Optional[RequestConfiguration[DeltaReq def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -74,7 +74,7 @@ def with_url(self,raw_url: str) -> DeltaRequestBuilder: @dataclass class DeltaRequestBuilderGetQueryParameters(): """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/users/item/calendars/item/calendar_view/item/exception_occurrences/delta/delta_request_builder.py b/msgraph_beta/generated/users/item/calendars/item/calendar_view/item/exception_occurrences/delta/delta_request_builder.py index 07e8ab0d6f8..4316028151a 100644 --- a/msgraph_beta/generated/users/item/calendars/item/calendar_view/item/exception_occurrences/delta/delta_request_builder.py +++ b/msgraph_beta/generated/users/item/calendars/item/calendar_view/item/exception_occurrences/delta/delta_request_builder.py @@ -31,7 +31,7 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def get(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> Optional[DeltaGetResponse]: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[DeltaGetResponse] Find more info here: https://learn.microsoft.com/graph/api/event-delta?view=graph-rest-beta @@ -52,7 +52,7 @@ async def get(self,request_configuration: Optional[RequestConfiguration[DeltaReq def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -74,7 +74,7 @@ def with_url(self,raw_url: str) -> DeltaRequestBuilder: @dataclass class DeltaRequestBuilderGetQueryParameters(): """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/users/item/calendars/item/calendar_view/item/exception_occurrences/item/instances/delta/delta_request_builder.py b/msgraph_beta/generated/users/item/calendars/item/calendar_view/item/exception_occurrences/item/instances/delta/delta_request_builder.py index 76bd9bbda5c..67d84bd8ced 100644 --- a/msgraph_beta/generated/users/item/calendars/item/calendar_view/item/exception_occurrences/item/instances/delta/delta_request_builder.py +++ b/msgraph_beta/generated/users/item/calendars/item/calendar_view/item/exception_occurrences/item/instances/delta/delta_request_builder.py @@ -31,7 +31,7 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def get(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> Optional[DeltaGetResponse]: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[DeltaGetResponse] Find more info here: https://learn.microsoft.com/graph/api/event-delta?view=graph-rest-beta @@ -52,7 +52,7 @@ async def get(self,request_configuration: Optional[RequestConfiguration[DeltaReq def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -74,7 +74,7 @@ def with_url(self,raw_url: str) -> DeltaRequestBuilder: @dataclass class DeltaRequestBuilderGetQueryParameters(): """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/users/item/calendars/item/calendar_view/item/instances/delta/delta_request_builder.py b/msgraph_beta/generated/users/item/calendars/item/calendar_view/item/instances/delta/delta_request_builder.py index f3b736c69fc..b87ed65c378 100644 --- a/msgraph_beta/generated/users/item/calendars/item/calendar_view/item/instances/delta/delta_request_builder.py +++ b/msgraph_beta/generated/users/item/calendars/item/calendar_view/item/instances/delta/delta_request_builder.py @@ -31,7 +31,7 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def get(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> Optional[DeltaGetResponse]: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[DeltaGetResponse] Find more info here: https://learn.microsoft.com/graph/api/event-delta?view=graph-rest-beta @@ -52,7 +52,7 @@ async def get(self,request_configuration: Optional[RequestConfiguration[DeltaReq def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -74,7 +74,7 @@ def with_url(self,raw_url: str) -> DeltaRequestBuilder: @dataclass class DeltaRequestBuilderGetQueryParameters(): """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/users/item/calendars/item/calendar_view/item/instances/item/exception_occurrences/delta/delta_request_builder.py b/msgraph_beta/generated/users/item/calendars/item/calendar_view/item/instances/item/exception_occurrences/delta/delta_request_builder.py index 26b158446ab..814ff2b84ba 100644 --- a/msgraph_beta/generated/users/item/calendars/item/calendar_view/item/instances/item/exception_occurrences/delta/delta_request_builder.py +++ b/msgraph_beta/generated/users/item/calendars/item/calendar_view/item/instances/item/exception_occurrences/delta/delta_request_builder.py @@ -31,7 +31,7 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def get(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> Optional[DeltaGetResponse]: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[DeltaGetResponse] Find more info here: https://learn.microsoft.com/graph/api/event-delta?view=graph-rest-beta @@ -52,7 +52,7 @@ async def get(self,request_configuration: Optional[RequestConfiguration[DeltaReq def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -74,7 +74,7 @@ def with_url(self,raw_url: str) -> DeltaRequestBuilder: @dataclass class DeltaRequestBuilderGetQueryParameters(): """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/users/item/calendars/item/events/delta/delta_request_builder.py b/msgraph_beta/generated/users/item/calendars/item/events/delta/delta_request_builder.py index 0e10d8df6d3..e8608fa7451 100644 --- a/msgraph_beta/generated/users/item/calendars/item/events/delta/delta_request_builder.py +++ b/msgraph_beta/generated/users/item/calendars/item/events/delta/delta_request_builder.py @@ -31,7 +31,7 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def get(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> Optional[DeltaGetResponse]: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[DeltaGetResponse] Find more info here: https://learn.microsoft.com/graph/api/event-delta?view=graph-rest-beta @@ -52,7 +52,7 @@ async def get(self,request_configuration: Optional[RequestConfiguration[DeltaReq def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -74,7 +74,7 @@ def with_url(self,raw_url: str) -> DeltaRequestBuilder: @dataclass class DeltaRequestBuilderGetQueryParameters(): """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/users/item/calendars/item/events/item/exception_occurrences/delta/delta_request_builder.py b/msgraph_beta/generated/users/item/calendars/item/events/item/exception_occurrences/delta/delta_request_builder.py index 36c0da48e58..c412728b36a 100644 --- a/msgraph_beta/generated/users/item/calendars/item/events/item/exception_occurrences/delta/delta_request_builder.py +++ b/msgraph_beta/generated/users/item/calendars/item/events/item/exception_occurrences/delta/delta_request_builder.py @@ -31,7 +31,7 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def get(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> Optional[DeltaGetResponse]: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[DeltaGetResponse] Find more info here: https://learn.microsoft.com/graph/api/event-delta?view=graph-rest-beta @@ -52,7 +52,7 @@ async def get(self,request_configuration: Optional[RequestConfiguration[DeltaReq def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -74,7 +74,7 @@ def with_url(self,raw_url: str) -> DeltaRequestBuilder: @dataclass class DeltaRequestBuilderGetQueryParameters(): """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/users/item/calendars/item/events/item/exception_occurrences/item/instances/delta/delta_request_builder.py b/msgraph_beta/generated/users/item/calendars/item/events/item/exception_occurrences/item/instances/delta/delta_request_builder.py index e3d3c0d75d1..b64480f0e05 100644 --- a/msgraph_beta/generated/users/item/calendars/item/events/item/exception_occurrences/item/instances/delta/delta_request_builder.py +++ b/msgraph_beta/generated/users/item/calendars/item/events/item/exception_occurrences/item/instances/delta/delta_request_builder.py @@ -31,7 +31,7 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def get(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> Optional[DeltaGetResponse]: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[DeltaGetResponse] Find more info here: https://learn.microsoft.com/graph/api/event-delta?view=graph-rest-beta @@ -52,7 +52,7 @@ async def get(self,request_configuration: Optional[RequestConfiguration[DeltaReq def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -74,7 +74,7 @@ def with_url(self,raw_url: str) -> DeltaRequestBuilder: @dataclass class DeltaRequestBuilderGetQueryParameters(): """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/users/item/calendars/item/events/item/instances/delta/delta_request_builder.py b/msgraph_beta/generated/users/item/calendars/item/events/item/instances/delta/delta_request_builder.py index c1798015820..2b7b7cadffb 100644 --- a/msgraph_beta/generated/users/item/calendars/item/events/item/instances/delta/delta_request_builder.py +++ b/msgraph_beta/generated/users/item/calendars/item/events/item/instances/delta/delta_request_builder.py @@ -31,7 +31,7 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def get(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> Optional[DeltaGetResponse]: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[DeltaGetResponse] Find more info here: https://learn.microsoft.com/graph/api/event-delta?view=graph-rest-beta @@ -52,7 +52,7 @@ async def get(self,request_configuration: Optional[RequestConfiguration[DeltaReq def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -74,7 +74,7 @@ def with_url(self,raw_url: str) -> DeltaRequestBuilder: @dataclass class DeltaRequestBuilderGetQueryParameters(): """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/users/item/calendars/item/events/item/instances/item/exception_occurrences/delta/delta_request_builder.py b/msgraph_beta/generated/users/item/calendars/item/events/item/instances/item/exception_occurrences/delta/delta_request_builder.py index 34b48c3ca91..f878d6705e7 100644 --- a/msgraph_beta/generated/users/item/calendars/item/events/item/instances/item/exception_occurrences/delta/delta_request_builder.py +++ b/msgraph_beta/generated/users/item/calendars/item/events/item/instances/item/exception_occurrences/delta/delta_request_builder.py @@ -31,7 +31,7 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def get(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> Optional[DeltaGetResponse]: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[DeltaGetResponse] Find more info here: https://learn.microsoft.com/graph/api/event-delta?view=graph-rest-beta @@ -52,7 +52,7 @@ async def get(self,request_configuration: Optional[RequestConfiguration[DeltaReq def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -74,7 +74,7 @@ def with_url(self,raw_url: str) -> DeltaRequestBuilder: @dataclass class DeltaRequestBuilderGetQueryParameters(): """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/users/item/cloud_p_cs/item/retrieve_review_status/retrieve_review_status_request_builder.py b/msgraph_beta/generated/users/item/cloud_p_cs/item/retrieve_review_status/retrieve_review_status_request_builder.py index f7b37411b91..53d2e62e212 100644 --- a/msgraph_beta/generated/users/item/cloud_p_cs/item/retrieve_review_status/retrieve_review_status_request_builder.py +++ b/msgraph_beta/generated/users/item/cloud_p_cs/item/retrieve_review_status/retrieve_review_status_request_builder.py @@ -31,9 +31,10 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def get(self,request_configuration: Optional[RequestConfiguration[QueryParameters]] = None) -> Optional[CloudPcReviewStatus]: """ - Invoke function retrieveReviewStatus + Get the review status of a Cloud PC. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[CloudPcReviewStatus] + Find more info here: https://learn.microsoft.com/graph/api/cloudpc-retrievereviewstatus?view=graph-rest-beta """ request_info = self.to_get_request_information( request_configuration @@ -51,7 +52,7 @@ async def get(self,request_configuration: Optional[RequestConfiguration[QueryPar def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[QueryParameters]] = None) -> RequestInformation: """ - Invoke function retrieveReviewStatus + Get the review status of a Cloud PC. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ diff --git a/msgraph_beta/generated/users/item/cloud_p_cs/item/retrieve_snapshots/retrieve_snapshots_request_builder.py b/msgraph_beta/generated/users/item/cloud_p_cs/item/retrieve_snapshots/retrieve_snapshots_request_builder.py index 17b51b6b66d..ca1509bcc18 100644 --- a/msgraph_beta/generated/users/item/cloud_p_cs/item/retrieve_snapshots/retrieve_snapshots_request_builder.py +++ b/msgraph_beta/generated/users/item/cloud_p_cs/item/retrieve_snapshots/retrieve_snapshots_request_builder.py @@ -31,9 +31,10 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def get(self,request_configuration: Optional[RequestConfiguration[RetrieveSnapshotsRequestBuilderGetQueryParameters]] = None) -> Optional[RetrieveSnapshotsGetResponse]: """ - Invoke function retrieveSnapshots + List all cloudPcSnapshot resources for a Cloud PC. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[RetrieveSnapshotsGetResponse] + Find more info here: https://learn.microsoft.com/graph/api/cloudpc-retrievesnapshots?view=graph-rest-beta """ request_info = self.to_get_request_information( request_configuration @@ -51,7 +52,7 @@ async def get(self,request_configuration: Optional[RequestConfiguration[Retrieve def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[RetrieveSnapshotsRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Invoke function retrieveSnapshots + List all cloudPcSnapshot resources for a Cloud PC. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -73,7 +74,7 @@ def with_url(self,raw_url: str) -> RetrieveSnapshotsRequestBuilder: @dataclass class RetrieveSnapshotsRequestBuilderGetQueryParameters(): """ - Invoke function retrieveSnapshots + List all cloudPcSnapshot resources for a Cloud PC. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/users/item/cloud_p_cs/item/set_review_status/set_review_status_request_builder.py b/msgraph_beta/generated/users/item/cloud_p_cs/item/set_review_status/set_review_status_request_builder.py index dd5dc7dc83a..242f5c93b59 100644 --- a/msgraph_beta/generated/users/item/cloud_p_cs/item/set_review_status/set_review_status_request_builder.py +++ b/msgraph_beta/generated/users/item/cloud_p_cs/item/set_review_status/set_review_status_request_builder.py @@ -31,10 +31,11 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def post(self,body: SetReviewStatusPostRequestBody, request_configuration: Optional[RequestConfiguration[QueryParameters]] = None) -> None: """ - Invoke action setReviewStatus + Set the review status of a specific Cloud PC device using the Cloud PC ID. Use this API to set the review status of a Cloud PC to in review if you consider a Cloud PC suspicious. After the review is completed, use this API again to set the Cloud PC back to a normal state. param body: The request body param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: None + Find more info here: https://learn.microsoft.com/graph/api/cloudpc-setreviewstatus?view=graph-rest-beta """ if body is None: raise TypeError("body cannot be null.") @@ -52,7 +53,7 @@ async def post(self,body: SetReviewStatusPostRequestBody, request_configuration: def to_post_request_information(self,body: SetReviewStatusPostRequestBody, request_configuration: Optional[RequestConfiguration[QueryParameters]] = None) -> RequestInformation: """ - Invoke action setReviewStatus + Set the review status of a specific Cloud PC device using the Cloud PC ID. Use this API to set the review status of a Cloud PC to in review if you consider a Cloud PC suspicious. After the review is completed, use this API again to set the Cloud PC back to a normal state. param body: The request body param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation diff --git a/msgraph_beta/generated/users/item/events/delta/delta_request_builder.py b/msgraph_beta/generated/users/item/events/delta/delta_request_builder.py index 80e9deb953d..0f882270e24 100644 --- a/msgraph_beta/generated/users/item/events/delta/delta_request_builder.py +++ b/msgraph_beta/generated/users/item/events/delta/delta_request_builder.py @@ -31,7 +31,7 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def get(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> Optional[DeltaGetResponse]: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[DeltaGetResponse] Find more info here: https://learn.microsoft.com/graph/api/event-delta?view=graph-rest-beta @@ -52,7 +52,7 @@ async def get(self,request_configuration: Optional[RequestConfiguration[DeltaReq def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -74,7 +74,7 @@ def with_url(self,raw_url: str) -> DeltaRequestBuilder: @dataclass class DeltaRequestBuilderGetQueryParameters(): """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/users/item/events/item/exception_occurrences/delta/delta_request_builder.py b/msgraph_beta/generated/users/item/events/item/exception_occurrences/delta/delta_request_builder.py index 50204fa39a5..e740597797b 100644 --- a/msgraph_beta/generated/users/item/events/item/exception_occurrences/delta/delta_request_builder.py +++ b/msgraph_beta/generated/users/item/events/item/exception_occurrences/delta/delta_request_builder.py @@ -31,7 +31,7 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def get(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> Optional[DeltaGetResponse]: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[DeltaGetResponse] Find more info here: https://learn.microsoft.com/graph/api/event-delta?view=graph-rest-beta @@ -52,7 +52,7 @@ async def get(self,request_configuration: Optional[RequestConfiguration[DeltaReq def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -74,7 +74,7 @@ def with_url(self,raw_url: str) -> DeltaRequestBuilder: @dataclass class DeltaRequestBuilderGetQueryParameters(): """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/users/item/events/item/exception_occurrences/item/instances/delta/delta_request_builder.py b/msgraph_beta/generated/users/item/events/item/exception_occurrences/item/instances/delta/delta_request_builder.py index 794f2c7f79b..4a79bab9bc8 100644 --- a/msgraph_beta/generated/users/item/events/item/exception_occurrences/item/instances/delta/delta_request_builder.py +++ b/msgraph_beta/generated/users/item/events/item/exception_occurrences/item/instances/delta/delta_request_builder.py @@ -31,7 +31,7 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def get(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> Optional[DeltaGetResponse]: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[DeltaGetResponse] Find more info here: https://learn.microsoft.com/graph/api/event-delta?view=graph-rest-beta @@ -52,7 +52,7 @@ async def get(self,request_configuration: Optional[RequestConfiguration[DeltaReq def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -74,7 +74,7 @@ def with_url(self,raw_url: str) -> DeltaRequestBuilder: @dataclass class DeltaRequestBuilderGetQueryParameters(): """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/users/item/events/item/instances/delta/delta_request_builder.py b/msgraph_beta/generated/users/item/events/item/instances/delta/delta_request_builder.py index a088bf5e4ef..013cf887412 100644 --- a/msgraph_beta/generated/users/item/events/item/instances/delta/delta_request_builder.py +++ b/msgraph_beta/generated/users/item/events/item/instances/delta/delta_request_builder.py @@ -31,7 +31,7 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def get(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> Optional[DeltaGetResponse]: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[DeltaGetResponse] Find more info here: https://learn.microsoft.com/graph/api/event-delta?view=graph-rest-beta @@ -52,7 +52,7 @@ async def get(self,request_configuration: Optional[RequestConfiguration[DeltaReq def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -74,7 +74,7 @@ def with_url(self,raw_url: str) -> DeltaRequestBuilder: @dataclass class DeltaRequestBuilderGetQueryParameters(): """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/users/item/events/item/instances/item/exception_occurrences/delta/delta_request_builder.py b/msgraph_beta/generated/users/item/events/item/instances/item/exception_occurrences/delta/delta_request_builder.py index e15ed60c039..bc63707c309 100644 --- a/msgraph_beta/generated/users/item/events/item/instances/item/exception_occurrences/delta/delta_request_builder.py +++ b/msgraph_beta/generated/users/item/events/item/instances/item/exception_occurrences/delta/delta_request_builder.py @@ -31,7 +31,7 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def get(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> Optional[DeltaGetResponse]: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[DeltaGetResponse] Find more info here: https://learn.microsoft.com/graph/api/event-delta?view=graph-rest-beta @@ -52,7 +52,7 @@ async def get(self,request_configuration: Optional[RequestConfiguration[DeltaReq def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -74,7 +74,7 @@ def with_url(self,raw_url: str) -> DeltaRequestBuilder: @dataclass class DeltaRequestBuilderGetQueryParameters(): """ - Get a set of event resources that have been added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar of the user's. In the case of getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). This allows you to maintain and synchronize a local store of events in the specified calendar, without having to fetch all the events of that calendar from the server every time. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. + Get a set of event resources that are added, deleted, or updated in one or more calendars. You can get specific types of these incremental changes in the events in all the calendars of a mailbox or in a specific calendar, or in an event collection of a calendarView (range of events defined by start and end dates) of a calendar. The calendar can be the default calendar or some other specified calendar that belongs to the user. When getting incremental changes on calendarView, the calendar can be a group calendar as well. Typically, synchronizing events in a calendar or calendarView in a local store entails a round of multiple delta function calls. The initial call is a full synchronization, and every subsequent delta call in the same round gets the incremental changes (additions, deletions, or updates). Using deltas allows you to incrementally maintain and synchronize a local store of events in the specified calendar. The following table lists the differences between the delta function on events and the delta function on a calendarView in a calendar. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/users/item/mail_folders/item/child_folders/item/messages/delta/delta_request_builder.py b/msgraph_beta/generated/users/item/mail_folders/item/child_folders/item/messages/delta/delta_request_builder.py index 4d0dc92f5dc..e3abb540729 100644 --- a/msgraph_beta/generated/users/item/mail_folders/item/child_folders/item/messages/delta/delta_request_builder.py +++ b/msgraph_beta/generated/users/item/mail_folders/item/child_folders/item/messages/delta/delta_request_builder.py @@ -31,7 +31,7 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def get(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> Optional[DeltaGetResponse]: """ - Get a set of messages that have been added, deleted, or updated in a specified folder. A delta function call for messages in a folder is similar to a GET request, except that by appropriatelyapplying state tokens in one or more of these calls, you can [query for incremental changes in the messages inthat folder](/graph/delta-query-messages). This allows you to maintain and synchronize a local store of a user's messages withouthaving to fetch the entire set of messages from the server every time. + Get a set of messages that were added, deleted, or updated in a specified folder. A delta function call for messages in a folder is similar to a GET request, except that by appropriatelyapplying state tokens in one or more of these calls, you can [query for incremental changes in the messages inthat folder](/graph/delta-query-messages). Using deltas allows you toincrementally maintain and synchronize a local store of a user's messages. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[DeltaGetResponse] Find more info here: https://learn.microsoft.com/graph/api/message-delta?view=graph-rest-beta @@ -52,7 +52,7 @@ async def get(self,request_configuration: Optional[RequestConfiguration[DeltaReq def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Get a set of messages that have been added, deleted, or updated in a specified folder. A delta function call for messages in a folder is similar to a GET request, except that by appropriatelyapplying state tokens in one or more of these calls, you can [query for incremental changes in the messages inthat folder](/graph/delta-query-messages). This allows you to maintain and synchronize a local store of a user's messages withouthaving to fetch the entire set of messages from the server every time. + Get a set of messages that were added, deleted, or updated in a specified folder. A delta function call for messages in a folder is similar to a GET request, except that by appropriatelyapplying state tokens in one or more of these calls, you can [query for incremental changes in the messages inthat folder](/graph/delta-query-messages). Using deltas allows you toincrementally maintain and synchronize a local store of a user's messages. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -74,7 +74,7 @@ def with_url(self,raw_url: str) -> DeltaRequestBuilder: @dataclass class DeltaRequestBuilderGetQueryParameters(): """ - Get a set of messages that have been added, deleted, or updated in a specified folder. A delta function call for messages in a folder is similar to a GET request, except that by appropriatelyapplying state tokens in one or more of these calls, you can [query for incremental changes in the messages inthat folder](/graph/delta-query-messages). This allows you to maintain and synchronize a local store of a user's messages withouthaving to fetch the entire set of messages from the server every time. + Get a set of messages that were added, deleted, or updated in a specified folder. A delta function call for messages in a folder is similar to a GET request, except that by appropriatelyapplying state tokens in one or more of these calls, you can [query for incremental changes in the messages inthat folder](/graph/delta-query-messages). Using deltas allows you toincrementally maintain and synchronize a local store of a user's messages. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/users/item/mail_folders/item/messages/delta/delta_request_builder.py b/msgraph_beta/generated/users/item/mail_folders/item/messages/delta/delta_request_builder.py index 9d689cbb687..d1f3489307d 100644 --- a/msgraph_beta/generated/users/item/mail_folders/item/messages/delta/delta_request_builder.py +++ b/msgraph_beta/generated/users/item/mail_folders/item/messages/delta/delta_request_builder.py @@ -31,7 +31,7 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def get(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> Optional[DeltaGetResponse]: """ - Get a set of messages that have been added, deleted, or updated in a specified folder. A delta function call for messages in a folder is similar to a GET request, except that by appropriatelyapplying state tokens in one or more of these calls, you can [query for incremental changes in the messages inthat folder](/graph/delta-query-messages). This allows you to maintain and synchronize a local store of a user's messages withouthaving to fetch the entire set of messages from the server every time. + Get a set of messages that were added, deleted, or updated in a specified folder. A delta function call for messages in a folder is similar to a GET request, except that by appropriatelyapplying state tokens in one or more of these calls, you can [query for incremental changes in the messages inthat folder](/graph/delta-query-messages). Using deltas allows you toincrementally maintain and synchronize a local store of a user's messages. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[DeltaGetResponse] Find more info here: https://learn.microsoft.com/graph/api/message-delta?view=graph-rest-beta @@ -52,7 +52,7 @@ async def get(self,request_configuration: Optional[RequestConfiguration[DeltaReq def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Get a set of messages that have been added, deleted, or updated in a specified folder. A delta function call for messages in a folder is similar to a GET request, except that by appropriatelyapplying state tokens in one or more of these calls, you can [query for incremental changes in the messages inthat folder](/graph/delta-query-messages). This allows you to maintain and synchronize a local store of a user's messages withouthaving to fetch the entire set of messages from the server every time. + Get a set of messages that were added, deleted, or updated in a specified folder. A delta function call for messages in a folder is similar to a GET request, except that by appropriatelyapplying state tokens in one or more of these calls, you can [query for incremental changes in the messages inthat folder](/graph/delta-query-messages). Using deltas allows you toincrementally maintain and synchronize a local store of a user's messages. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -74,7 +74,7 @@ def with_url(self,raw_url: str) -> DeltaRequestBuilder: @dataclass class DeltaRequestBuilderGetQueryParameters(): """ - Get a set of messages that have been added, deleted, or updated in a specified folder. A delta function call for messages in a folder is similar to a GET request, except that by appropriatelyapplying state tokens in one or more of these calls, you can [query for incremental changes in the messages inthat folder](/graph/delta-query-messages). This allows you to maintain and synchronize a local store of a user's messages withouthaving to fetch the entire set of messages from the server every time. + Get a set of messages that were added, deleted, or updated in a specified folder. A delta function call for messages in a folder is similar to a GET request, except that by appropriatelyapplying state tokens in one or more of these calls, you can [query for incremental changes in the messages inthat folder](/graph/delta-query-messages). Using deltas allows you toincrementally maintain and synchronize a local store of a user's messages. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/users/item/messages/delta/delta_request_builder.py b/msgraph_beta/generated/users/item/messages/delta/delta_request_builder.py index 35ac9b26c67..d87fa295c1b 100644 --- a/msgraph_beta/generated/users/item/messages/delta/delta_request_builder.py +++ b/msgraph_beta/generated/users/item/messages/delta/delta_request_builder.py @@ -31,7 +31,7 @@ def __init__(self,request_adapter: RequestAdapter, path_parameters: Union[str, D async def get(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> Optional[DeltaGetResponse]: """ - Get a set of messages that have been added, deleted, or updated in a specified folder. A delta function call for messages in a folder is similar to a GET request, except that by appropriatelyapplying state tokens in one or more of these calls, you can [query for incremental changes in the messages inthat folder](/graph/delta-query-messages). This allows you to maintain and synchronize a local store of a user's messages withouthaving to fetch the entire set of messages from the server every time. + Get a set of messages that were added, deleted, or updated in a specified folder. A delta function call for messages in a folder is similar to a GET request, except that by appropriatelyapplying state tokens in one or more of these calls, you can [query for incremental changes in the messages inthat folder](/graph/delta-query-messages). Using deltas allows you toincrementally maintain and synchronize a local store of a user's messages. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[DeltaGetResponse] Find more info here: https://learn.microsoft.com/graph/api/message-delta?view=graph-rest-beta @@ -52,7 +52,7 @@ async def get(self,request_configuration: Optional[RequestConfiguration[DeltaReq def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[DeltaRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Get a set of messages that have been added, deleted, or updated in a specified folder. A delta function call for messages in a folder is similar to a GET request, except that by appropriatelyapplying state tokens in one or more of these calls, you can [query for incremental changes in the messages inthat folder](/graph/delta-query-messages). This allows you to maintain and synchronize a local store of a user's messages withouthaving to fetch the entire set of messages from the server every time. + Get a set of messages that were added, deleted, or updated in a specified folder. A delta function call for messages in a folder is similar to a GET request, except that by appropriatelyapplying state tokens in one or more of these calls, you can [query for incremental changes in the messages inthat folder](/graph/delta-query-messages). Using deltas allows you toincrementally maintain and synchronize a local store of a user's messages. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -74,7 +74,7 @@ def with_url(self,raw_url: str) -> DeltaRequestBuilder: @dataclass class DeltaRequestBuilderGetQueryParameters(): """ - Get a set of messages that have been added, deleted, or updated in a specified folder. A delta function call for messages in a folder is similar to a GET request, except that by appropriatelyapplying state tokens in one or more of these calls, you can [query for incremental changes in the messages inthat folder](/graph/delta-query-messages). This allows you to maintain and synchronize a local store of a user's messages withouthaving to fetch the entire set of messages from the server every time. + Get a set of messages that were added, deleted, or updated in a specified folder. A delta function call for messages in a folder is similar to a GET request, except that by appropriatelyapplying state tokens in one or more of these calls, you can [query for incremental changes in the messages inthat folder](/graph/delta-query-messages). Using deltas allows you toincrementally maintain and synchronize a local store of a user's messages. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/users/item/onenote/notebooks/item/notebook_item_request_builder.py b/msgraph_beta/generated/users/item/onenote/notebooks/item/notebook_item_request_builder.py index 942b02fd7fc..94619946ac0 100644 --- a/msgraph_beta/generated/users/item/onenote/notebooks/item/notebook_item_request_builder.py +++ b/msgraph_beta/generated/users/item/onenote/notebooks/item/notebook_item_request_builder.py @@ -52,7 +52,7 @@ async def delete(self,request_configuration: Optional[RequestConfiguration[Query async def get(self,request_configuration: Optional[RequestConfiguration[NotebookItemRequestBuilderGetQueryParameters]] = None) -> Optional[Notebook]: """ - The collection of OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The collection of OneNote notebooks that the user or group owns. Read-only. Nullable. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[Notebook] """ @@ -106,7 +106,7 @@ def to_delete_request_information(self,request_configuration: Optional[RequestCo def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[NotebookItemRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - The collection of OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The collection of OneNote notebooks that the user or group owns. Read-only. Nullable. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -177,7 +177,7 @@ class NotebookItemRequestBuilderDeleteRequestConfiguration(RequestConfiguration[ @dataclass class NotebookItemRequestBuilderGetQueryParameters(): """ - The collection of OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The collection of OneNote notebooks that the user or group owns. Read-only. Nullable. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/users/item/onenote/notebooks/notebooks_request_builder.py b/msgraph_beta/generated/users/item/onenote/notebooks/notebooks_request_builder.py index 23e16115add..2e6db19b5f6 100644 --- a/msgraph_beta/generated/users/item/onenote/notebooks/notebooks_request_builder.py +++ b/msgraph_beta/generated/users/item/onenote/notebooks/notebooks_request_builder.py @@ -50,7 +50,7 @@ def by_notebook_id(self,notebook_id: str) -> NotebookItemRequestBuilder: async def get(self,request_configuration: Optional[RequestConfiguration[NotebooksRequestBuilderGetQueryParameters]] = None) -> Optional[NotebookCollectionResponse]: """ - The collection of OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The collection of OneNote notebooks that the user or group owns. Read-only. Nullable. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[NotebookCollectionResponse] """ @@ -105,7 +105,7 @@ async def post(self,body: Notebook, request_configuration: Optional[RequestConfi def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[NotebooksRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - The collection of OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The collection of OneNote notebooks that the user or group owns. Read-only. Nullable. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -160,7 +160,7 @@ def get_notebook_from_web_url(self) -> GetNotebookFromWebUrlRequestBuilder: @dataclass class NotebooksRequestBuilderGetQueryParameters(): """ - The collection of OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The collection of OneNote notebooks that the user or group owns. Read-only. Nullable. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/users/item/onenote/pages/item/onenote_page_item_request_builder.py b/msgraph_beta/generated/users/item/onenote/pages/item/onenote_page_item_request_builder.py index c929ed35bfe..842466ade36 100644 --- a/msgraph_beta/generated/users/item/onenote/pages/item/onenote_page_item_request_builder.py +++ b/msgraph_beta/generated/users/item/onenote/pages/item/onenote_page_item_request_builder.py @@ -55,7 +55,7 @@ async def delete(self,request_configuration: Optional[RequestConfiguration[Query async def get(self,request_configuration: Optional[RequestConfiguration[OnenotePageItemRequestBuilderGetQueryParameters]] = None) -> Optional[OnenotePage]: """ - The pages in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The pages in all OneNote notebooks that the user or group owns. Read-only. Nullable. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[OnenotePage] """ @@ -109,7 +109,7 @@ def to_delete_request_information(self,request_configuration: Optional[RequestCo def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[OnenotePageItemRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - The pages in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The pages in all OneNote notebooks that the user or group owns. Read-only. Nullable. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -207,7 +207,7 @@ class OnenotePageItemRequestBuilderDeleteRequestConfiguration(RequestConfigurati @dataclass class OnenotePageItemRequestBuilderGetQueryParameters(): """ - The pages in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The pages in all OneNote notebooks that the user or group owns. Read-only. Nullable. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/users/item/onenote/pages/pages_request_builder.py b/msgraph_beta/generated/users/item/onenote/pages/pages_request_builder.py index a710e425702..76d839d949f 100644 --- a/msgraph_beta/generated/users/item/onenote/pages/pages_request_builder.py +++ b/msgraph_beta/generated/users/item/onenote/pages/pages_request_builder.py @@ -48,7 +48,7 @@ def by_onenote_page_id(self,onenote_page_id: str) -> OnenotePageItemRequestBuild async def get(self,request_configuration: Optional[RequestConfiguration[PagesRequestBuilderGetQueryParameters]] = None) -> Optional[OnenotePageCollectionResponse]: """ - The pages in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The pages in all OneNote notebooks that the user or group owns. Read-only. Nullable. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[OnenotePageCollectionResponse] """ @@ -91,7 +91,7 @@ async def post(self,body: OnenotePage, request_configuration: Optional[RequestCo def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[PagesRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - The pages in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The pages in all OneNote notebooks that the user or group owns. Read-only. Nullable. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -137,7 +137,7 @@ def count(self) -> CountRequestBuilder: @dataclass class PagesRequestBuilderGetQueryParameters(): """ - The pages in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The pages in all OneNote notebooks that the user or group owns. Read-only. Nullable. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/users/item/onenote/section_groups/item/section_group_item_request_builder.py b/msgraph_beta/generated/users/item/onenote/section_groups/item/section_group_item_request_builder.py index b0f6dc22aa3..b8ce3f77bdd 100644 --- a/msgraph_beta/generated/users/item/onenote/section_groups/item/section_group_item_request_builder.py +++ b/msgraph_beta/generated/users/item/onenote/section_groups/item/section_group_item_request_builder.py @@ -53,7 +53,7 @@ async def delete(self,request_configuration: Optional[RequestConfiguration[Query async def get(self,request_configuration: Optional[RequestConfiguration[SectionGroupItemRequestBuilderGetQueryParameters]] = None) -> Optional[SectionGroup]: """ - The section groups in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The section groups in all OneNote notebooks that the user or group owns. Read-only. Nullable. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[SectionGroup] """ @@ -107,7 +107,7 @@ def to_delete_request_information(self,request_configuration: Optional[RequestCo def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[SectionGroupItemRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - The section groups in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The section groups in all OneNote notebooks that the user or group owns. Read-only. Nullable. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -187,7 +187,7 @@ class SectionGroupItemRequestBuilderDeleteRequestConfiguration(RequestConfigurat @dataclass class SectionGroupItemRequestBuilderGetQueryParameters(): """ - The section groups in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The section groups in all OneNote notebooks that the user or group owns. Read-only. Nullable. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/users/item/onenote/section_groups/section_groups_request_builder.py b/msgraph_beta/generated/users/item/onenote/section_groups/section_groups_request_builder.py index 082498ea8bd..5966491c50a 100644 --- a/msgraph_beta/generated/users/item/onenote/section_groups/section_groups_request_builder.py +++ b/msgraph_beta/generated/users/item/onenote/section_groups/section_groups_request_builder.py @@ -48,7 +48,7 @@ def by_section_group_id(self,section_group_id: str) -> SectionGroupItemRequestBu async def get(self,request_configuration: Optional[RequestConfiguration[SectionGroupsRequestBuilderGetQueryParameters]] = None) -> Optional[SectionGroupCollectionResponse]: """ - The section groups in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The section groups in all OneNote notebooks that the user or group owns. Read-only. Nullable. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[SectionGroupCollectionResponse] """ @@ -91,7 +91,7 @@ async def post(self,body: SectionGroup, request_configuration: Optional[RequestC def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[SectionGroupsRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - The section groups in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The section groups in all OneNote notebooks that the user or group owns. Read-only. Nullable. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -137,7 +137,7 @@ def count(self) -> CountRequestBuilder: @dataclass class SectionGroupsRequestBuilderGetQueryParameters(): """ - The section groups in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The section groups in all OneNote notebooks that the user or group owns. Read-only. Nullable. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/users/item/onenote/sections/item/onenote_section_item_request_builder.py b/msgraph_beta/generated/users/item/onenote/sections/item/onenote_section_item_request_builder.py index e5d9337313f..053c9a67c20 100644 --- a/msgraph_beta/generated/users/item/onenote/sections/item/onenote_section_item_request_builder.py +++ b/msgraph_beta/generated/users/item/onenote/sections/item/onenote_section_item_request_builder.py @@ -54,7 +54,7 @@ async def delete(self,request_configuration: Optional[RequestConfiguration[Query async def get(self,request_configuration: Optional[RequestConfiguration[OnenoteSectionItemRequestBuilderGetQueryParameters]] = None) -> Optional[OnenoteSection]: """ - The sections in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The sections in all OneNote notebooks that the user or group owns. Read-only. Nullable. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[OnenoteSection] """ @@ -108,7 +108,7 @@ def to_delete_request_information(self,request_configuration: Optional[RequestCo def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[OnenoteSectionItemRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - The sections in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The sections in all OneNote notebooks that the user or group owns. Read-only. Nullable. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -197,7 +197,7 @@ class OnenoteSectionItemRequestBuilderDeleteRequestConfiguration(RequestConfigur @dataclass class OnenoteSectionItemRequestBuilderGetQueryParameters(): """ - The sections in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The sections in all OneNote notebooks that the user or group owns. Read-only. Nullable. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/users/item/onenote/sections/sections_request_builder.py b/msgraph_beta/generated/users/item/onenote/sections/sections_request_builder.py index 3a654c03cd0..7df5a6cb3bd 100644 --- a/msgraph_beta/generated/users/item/onenote/sections/sections_request_builder.py +++ b/msgraph_beta/generated/users/item/onenote/sections/sections_request_builder.py @@ -48,7 +48,7 @@ def by_onenote_section_id(self,onenote_section_id: str) -> OnenoteSectionItemReq async def get(self,request_configuration: Optional[RequestConfiguration[SectionsRequestBuilderGetQueryParameters]] = None) -> Optional[OnenoteSectionCollectionResponse]: """ - The sections in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The sections in all OneNote notebooks that the user or group owns. Read-only. Nullable. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[OnenoteSectionCollectionResponse] """ @@ -91,7 +91,7 @@ async def post(self,body: OnenoteSection, request_configuration: Optional[Reques def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[SectionsRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - The sections in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The sections in all OneNote notebooks that the user or group owns. Read-only. Nullable. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -137,7 +137,7 @@ def count(self) -> CountRequestBuilder: @dataclass class SectionsRequestBuilderGetQueryParameters(): """ - The sections in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + The sections in all OneNote notebooks that the user or group owns. Read-only. Nullable. """ def get_query_parameter(self,original_name: str) -> str: """ diff --git a/msgraph_beta/generated/users/item/presence/presence_request_builder.py b/msgraph_beta/generated/users/item/presence/presence_request_builder.py index 8f5d7039dee..3d270df1d5d 100644 --- a/msgraph_beta/generated/users/item/presence/presence_request_builder.py +++ b/msgraph_beta/generated/users/item/presence/presence_request_builder.py @@ -54,10 +54,10 @@ async def delete(self,request_configuration: Optional[RequestConfiguration[Query async def get(self,request_configuration: Optional[RequestConfiguration[PresenceRequestBuilderGetQueryParameters]] = None) -> Optional[Presence]: """ - Set a presence status message for a user. An optional expiration date and time can be supplied. + Get a user's presence information. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: Optional[Presence] - Find more info here: https://learn.microsoft.com/graph/api/presence-setstatusmessage?view=graph-rest-beta + Find more info here: https://learn.microsoft.com/graph/api/presence-get?view=graph-rest-beta """ request_info = self.to_get_request_information( request_configuration @@ -109,7 +109,7 @@ def to_delete_request_information(self,request_configuration: Optional[RequestCo def to_get_request_information(self,request_configuration: Optional[RequestConfiguration[PresenceRequestBuilderGetQueryParameters]] = None) -> RequestInformation: """ - Set a presence status message for a user. An optional expiration date and time can be supplied. + Get a user's presence information. param request_configuration: Configuration for the request such as headers, query parameters, and middleware options. Returns: RequestInformation """ @@ -198,7 +198,7 @@ class PresenceRequestBuilderDeleteRequestConfiguration(RequestConfiguration[Quer @dataclass class PresenceRequestBuilderGetQueryParameters(): """ - Set a presence status message for a user. An optional expiration date and time can be supplied. + Get a user's presence information. """ def get_query_parameter(self,original_name: str) -> str: """