diff --git a/src/main/java/com/microsoft/graph/beta/generated/admin/windows/updates/resourceconnections/item/ResourceConnectionItemRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/admin/windows/updates/resourceconnections/item/ResourceConnectionItemRequestBuilder.java index 0159ff148ea..8cc3dbb44bf 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/admin/windows/updates/resourceconnections/item/ResourceConnectionItemRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/admin/windows/updates/resourceconnections/item/ResourceConnectionItemRequestBuilder.java @@ -37,18 +37,18 @@ public ResourceConnectionItemRequestBuilder(@jakarta.annotation.Nonnull final St super(requestAdapter, "{+baseurl}/admin/windows/updates/resourceConnections/{resourceConnection%2Did}{?%24expand,%24select}", rawUrl); } /** - * Delete an operationalInsightsConnection object. + * Delete a resourceConnection object. * @throws ODataError When receiving a 4XX or 5XX status code - * @see Find more info here + * @see Find more info here */ public void delete() { delete(null); } /** - * Delete an operationalInsightsConnection object. + * Delete a resourceConnection object. * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @throws ODataError When receiving a 4XX or 5XX status code - * @see Find more info here + * @see Find more info here */ public void delete(@jakarta.annotation.Nullable final java.util.function.Consumer requestConfiguration) { final RequestInformation requestInfo = toDeleteRequestInformation(requestConfiguration); @@ -106,7 +106,7 @@ public ResourceConnection patch(@jakarta.annotation.Nonnull final ResourceConnec return this.requestAdapter.send(requestInfo, errorMapping, ResourceConnection::createFromDiscriminatorValue); } /** - * Delete an operationalInsightsConnection object. + * Delete a resourceConnection object. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -114,7 +114,7 @@ public RequestInformation toDeleteRequestInformation() { return toDeleteRequestInformation(null); } /** - * Delete an operationalInsightsConnection object. + * Delete a resourceConnection object. * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ diff --git a/src/main/java/com/microsoft/graph/beta/generated/admin/windows/updates/updatableassets/item/UpdatableAssetItemRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/admin/windows/updates/updatableassets/item/UpdatableAssetItemRequestBuilder.java index 30315385c2f..48f24ed68da 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/admin/windows/updates/updatableassets/item/UpdatableAssetItemRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/admin/windows/updates/updatableassets/item/UpdatableAssetItemRequestBuilder.java @@ -93,21 +93,21 @@ public void delete(@jakarta.annotation.Nullable final java.util.function.Consume this.requestAdapter.sendPrimitive(requestInfo, errorMapping, Void.class); } /** - * Read the properties and relationships of an updatableAssetGroup object. + * Read the properties and relationships of an updatableAsset object. * @return a {@link UpdatableAsset} * @throws ODataError When receiving a 4XX or 5XX status code - * @see Find more info here + * @see Find more info here */ @jakarta.annotation.Nullable public UpdatableAsset get() { return get(null); } /** - * Read the properties and relationships of an updatableAssetGroup object. + * Read the properties and relationships of an updatableAsset object. * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link UpdatableAsset} * @throws ODataError When receiving a 4XX or 5XX status code - * @see Find more info here + * @see Find more info here */ @jakarta.annotation.Nullable public UpdatableAsset get(@jakarta.annotation.Nullable final java.util.function.Consumer requestConfiguration) { @@ -162,7 +162,7 @@ public RequestInformation toDeleteRequestInformation(@jakarta.annotation.Nullabl return requestInfo; } /** - * Read the properties and relationships of an updatableAssetGroup object. + * Read the properties and relationships of an updatableAsset object. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -170,7 +170,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * Read the properties and relationships of an updatableAssetGroup object. + * Read the properties and relationships of an updatableAsset object. * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -222,7 +222,7 @@ public UpdatableAssetItemRequestBuilder withUrl(@jakarta.annotation.Nonnull fina public class DeleteRequestConfiguration extends BaseRequestConfiguration { } /** - * Read the properties and relationships of an updatableAssetGroup object. + * Read the properties and relationships of an updatableAsset object. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/admin/windows/updates/updatepolicies/item/compliancechanges/item/ComplianceChangeItemRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/admin/windows/updates/updatepolicies/item/compliancechanges/item/ComplianceChangeItemRequestBuilder.java index 9e2d5fe6f71..966ec8ffabe 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/admin/windows/updates/updatepolicies/item/compliancechanges/item/ComplianceChangeItemRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/admin/windows/updates/updatepolicies/item/compliancechanges/item/ComplianceChangeItemRequestBuilder.java @@ -46,18 +46,18 @@ public ComplianceChangeItemRequestBuilder(@jakarta.annotation.Nonnull final Stri super(requestAdapter, "{+baseurl}/admin/windows/updates/updatePolicies/{updatePolicy%2Did}/complianceChanges/{complianceChange%2Did}{?%24expand,%24select}", rawUrl); } /** - * Delete a complianceChange object. + * Delete a contentApproval object. * @throws ODataError When receiving a 4XX or 5XX status code - * @see Find more info here + * @see Find more info here */ public void delete() { delete(null); } /** - * Delete a complianceChange object. + * Delete a contentApproval object. * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @throws ODataError When receiving a 4XX or 5XX status code - * @see Find more info here + * @see Find more info here */ public void delete(@jakarta.annotation.Nullable final java.util.function.Consumer requestConfiguration) { final RequestInformation requestInfo = toDeleteRequestInformation(requestConfiguration); @@ -90,23 +90,23 @@ public ComplianceChange get(@jakarta.annotation.Nullable final java.util.functio return this.requestAdapter.send(requestInfo, errorMapping, ComplianceChange::createFromDiscriminatorValue); } /** - * Update the properties of a complianceChange object. + * Update the properties of a contentApproval object. * @param body The request body * @return a {@link ComplianceChange} * @throws ODataError When receiving a 4XX or 5XX status code - * @see Find more info here + * @see Find more info here */ @jakarta.annotation.Nullable public ComplianceChange patch(@jakarta.annotation.Nonnull final ComplianceChange body) { return patch(body, null); } /** - * Update the properties of a complianceChange object. + * Update the properties of a contentApproval object. * @param body The request body * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link ComplianceChange} * @throws ODataError When receiving a 4XX or 5XX status code - * @see Find more info here + * @see Find more info here */ @jakarta.annotation.Nullable public ComplianceChange patch(@jakarta.annotation.Nonnull final ComplianceChange body, @jakarta.annotation.Nullable final java.util.function.Consumer requestConfiguration) { @@ -117,7 +117,7 @@ public ComplianceChange patch(@jakarta.annotation.Nonnull final ComplianceChange return this.requestAdapter.send(requestInfo, errorMapping, ComplianceChange::createFromDiscriminatorValue); } /** - * Delete a complianceChange object. + * Delete a contentApproval object. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -125,7 +125,7 @@ public RequestInformation toDeleteRequestInformation() { return toDeleteRequestInformation(null); } /** - * Delete a complianceChange object. + * Delete a contentApproval object. * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -157,7 +157,7 @@ public RequestInformation toGetRequestInformation(@jakarta.annotation.Nullable f return requestInfo; } /** - * Update the properties of a complianceChange object. + * Update the properties of a contentApproval object. * @param body The request body * @return a {@link RequestInformation} */ @@ -166,7 +166,7 @@ public RequestInformation toPatchRequestInformation(@jakarta.annotation.Nonnull return toPatchRequestInformation(body, null); } /** - * Update the properties of a complianceChange object. + * Update the properties of a contentApproval object. * @param body The request body * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} diff --git a/src/main/java/com/microsoft/graph/beta/generated/app/calls/item/participants/invite/InviteRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/app/calls/item/participants/invite/InviteRequestBuilder.java index 325d49a04f5..8f747290eac 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/app/calls/item/participants/invite/InviteRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/app/calls/item/participants/invite/InviteRequestBuilder.java @@ -36,23 +36,23 @@ public InviteRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @ja super(requestAdapter, "{+baseurl}/app/calls/{call%2Did}/participants/invite", rawUrl); } /** - * 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 * @return a {@link InviteParticipantsOperation} * @throws ODataError When receiving a 4XX or 5XX status code - * @see Find more info here + * @see Find more info here */ @jakarta.annotation.Nullable public InviteParticipantsOperation post(@jakarta.annotation.Nonnull final InvitePostRequestBody body) { return post(body, null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link InviteParticipantsOperation} * @throws ODataError When receiving a 4XX or 5XX status code - * @see Find more info here + * @see Find more info here */ @jakarta.annotation.Nullable public InviteParticipantsOperation post(@jakarta.annotation.Nonnull final InvitePostRequestBody body, @jakarta.annotation.Nullable final java.util.function.Consumer requestConfiguration) { @@ -63,7 +63,7 @@ public InviteParticipantsOperation post(@jakarta.annotation.Nonnull final Invite return this.requestAdapter.send(requestInfo, errorMapping, InviteParticipantsOperation::createFromDiscriminatorValue); } /** - * 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 * @return a {@link RequestInformation} */ @@ -72,7 +72,7 @@ public RequestInformation toPostRequestInformation(@jakarta.annotation.Nonnull f return toPostRequestInformation(body, null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} diff --git a/src/main/java/com/microsoft/graph/beta/generated/authenticationmethoddevices/item/hardwareoathdevices/HardwareOathDevicesRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/authenticationmethoddevices/item/hardwareoathdevices/HardwareOathDevicesRequestBuilder.java index 7f73727eec9..4d180414db1 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/authenticationmethoddevices/item/hardwareoathdevices/HardwareOathDevicesRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/authenticationmethoddevices/item/hardwareoathdevices/HardwareOathDevicesRequestBuilder.java @@ -60,7 +60,7 @@ public HardwareOathDevicesRequestBuilder(@jakarta.annotation.Nonnull final Strin super(requestAdapter, "{+baseurl}/authenticationMethodDevices/{authenticationMethodDevice%2Did}/hardwareOathDevices{?%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * Get hardwareOathDevices from authenticationMethodDevices + * Exposes the hardware OATH method in the directory. * @return a {@link HardwareOathTokenAuthenticationMethodDeviceCollectionResponse} * @throws ODataError When receiving a 4XX or 5XX status code */ @@ -69,7 +69,7 @@ public HardwareOathTokenAuthenticationMethodDeviceCollectionResponse get() { return get(null); } /** - * Get hardwareOathDevices from authenticationMethodDevices + * Exposes the hardware OATH method in the directory. * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link HardwareOathTokenAuthenticationMethodDeviceCollectionResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -107,7 +107,7 @@ public HardwareOathTokenAuthenticationMethodDevice post(@jakarta.annotation.Nonn return this.requestAdapter.send(requestInfo, errorMapping, HardwareOathTokenAuthenticationMethodDevice::createFromDiscriminatorValue); } /** - * Get hardwareOathDevices from authenticationMethodDevices + * Exposes the hardware OATH method in the directory. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -115,7 +115,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * Get hardwareOathDevices from authenticationMethodDevices + * Exposes the hardware OATH method in the directory. * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -161,7 +161,7 @@ public HardwareOathDevicesRequestBuilder withUrl(@jakarta.annotation.Nonnull fin return new HardwareOathDevicesRequestBuilder(rawUrl, requestAdapter); } /** - * Get hardwareOathDevices from authenticationMethodDevices + * Exposes the hardware OATH method in the directory. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/authenticationmethoddevices/item/hardwareoathdevices/item/HardwareOathTokenAuthenticationMethodDeviceItemRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/authenticationmethoddevices/item/hardwareoathdevices/item/HardwareOathTokenAuthenticationMethodDeviceItemRequestBuilder.java index 696507a3ac3..0876c90f2cb 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/authenticationmethoddevices/item/hardwareoathdevices/item/HardwareOathTokenAuthenticationMethodDeviceItemRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/authenticationmethoddevices/item/hardwareoathdevices/item/HardwareOathTokenAuthenticationMethodDeviceItemRequestBuilder.java @@ -64,7 +64,7 @@ public void delete(@jakarta.annotation.Nullable final java.util.function.Consume this.requestAdapter.sendPrimitive(requestInfo, errorMapping, Void.class); } /** - * Get hardwareOathDevices from authenticationMethodDevices + * Exposes the hardware OATH method in the directory. * @return a {@link HardwareOathTokenAuthenticationMethodDevice} * @throws ODataError When receiving a 4XX or 5XX status code */ @@ -73,7 +73,7 @@ public HardwareOathTokenAuthenticationMethodDevice get() { return get(null); } /** - * Get hardwareOathDevices from authenticationMethodDevices + * Exposes the hardware OATH method in the directory. * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link HardwareOathTokenAuthenticationMethodDevice} * @throws ODataError When receiving a 4XX or 5XX status code @@ -131,7 +131,7 @@ public RequestInformation toDeleteRequestInformation(@jakarta.annotation.Nullabl return requestInfo; } /** - * Get hardwareOathDevices from authenticationMethodDevices + * Exposes the hardware OATH method in the directory. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -139,7 +139,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * Get hardwareOathDevices from authenticationMethodDevices + * Exposes the hardware OATH method in the directory. * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -191,7 +191,7 @@ public HardwareOathTokenAuthenticationMethodDeviceItemRequestBuilder withUrl(@ja public class DeleteRequestConfiguration extends BaseRequestConfiguration { } /** - * Get hardwareOathDevices from authenticationMethodDevices + * Exposes the hardware OATH method in the directory. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/authenticationmethoddevices/item/hardwareoathdevices/item/assignto/AssignToRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/authenticationmethoddevices/item/hardwareoathdevices/item/assignto/AssignToRequestBuilder.java index 957626d2158..173be352a31 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/authenticationmethoddevices/item/hardwareoathdevices/item/assignto/AssignToRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/authenticationmethoddevices/item/hardwareoathdevices/item/assignto/AssignToRequestBuilder.java @@ -55,7 +55,7 @@ public AssignToRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @ super(requestAdapter, "{+baseurl}/authenticationMethodDevices/{authenticationMethodDevice%2Did}/hardwareOathDevices/{hardwareOathTokenAuthenticationMethodDevice%2Did}/assignTo{?%24expand,%24select}", rawUrl); } /** - * Get assignTo from authenticationMethodDevices + * Assign the hardware OATH token to a user. * @return a {@link User} * @throws ODataError When receiving a 4XX or 5XX status code */ @@ -64,7 +64,7 @@ public User get() { return get(null); } /** - * Get assignTo from authenticationMethodDevices + * Assign the hardware OATH token to a user. * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link User} * @throws ODataError When receiving a 4XX or 5XX status code @@ -77,7 +77,7 @@ public User get(@jakarta.annotation.Nullable final java.util.function.ConsumerFind more info here + * @see Find more info here */ @jakarta.annotation.Nullable public InviteParticipantsOperation post(@jakarta.annotation.Nonnull final InvitePostRequestBody body) { return post(body, null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link InviteParticipantsOperation} * @throws ODataError When receiving a 4XX or 5XX status code - * @see Find more info here + * @see Find more info here */ @jakarta.annotation.Nullable public InviteParticipantsOperation post(@jakarta.annotation.Nonnull final InvitePostRequestBody body, @jakarta.annotation.Nullable final java.util.function.Consumer requestConfiguration) { @@ -63,7 +63,7 @@ public InviteParticipantsOperation post(@jakarta.annotation.Nonnull final Invite return this.requestAdapter.send(requestInfo, errorMapping, InviteParticipantsOperation::createFromDiscriminatorValue); } /** - * 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 * @return a {@link RequestInformation} */ @@ -72,7 +72,7 @@ public RequestInformation toPostRequestInformation(@jakarta.annotation.Nonnull f return toPostRequestInformation(body, null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} diff --git a/src/main/java/com/microsoft/graph/beta/generated/devicemanagement/devicecompliancepolicies/item/scheduledactionsforrule/ScheduledActionsForRuleRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/devicemanagement/devicecompliancepolicies/item/scheduledactionsforrule/ScheduledActionsForRuleRequestBuilder.java index 62ca53adbac..7adff25300c 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/devicemanagement/devicecompliancepolicies/item/scheduledactionsforrule/ScheduledActionsForRuleRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/devicemanagement/devicecompliancepolicies/item/scheduledactionsforrule/ScheduledActionsForRuleRequestBuilder.java @@ -60,7 +60,7 @@ public ScheduledActionsForRuleRequestBuilder(@jakarta.annotation.Nonnull final S super(requestAdapter, "{+baseurl}/deviceManagement/deviceCompliancePolicies/{deviceCompliancePolicy%2Did}/scheduledActionsForRule{?%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * 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. * @return a {@link DeviceComplianceScheduledActionForRuleCollectionResponse} * @throws ODataError When receiving a 4XX or 5XX status code */ @@ -69,7 +69,7 @@ public DeviceComplianceScheduledActionForRuleCollectionResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link DeviceComplianceScheduledActionForRuleCollectionResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -107,7 +107,7 @@ public DeviceComplianceScheduledActionForRule post(@jakarta.annotation.Nonnull f return this.requestAdapter.send(requestInfo, errorMapping, DeviceComplianceScheduledActionForRule::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -115,7 +115,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -161,7 +161,7 @@ public ScheduledActionsForRuleRequestBuilder withUrl(@jakarta.annotation.Nonnull return new ScheduledActionsForRuleRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/devicemanagement/devicecompliancepolicies/item/scheduledactionsforrule/item/DeviceComplianceScheduledActionForRuleItemRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/devicemanagement/devicecompliancepolicies/item/scheduledactionsforrule/item/DeviceComplianceScheduledActionForRuleItemRequestBuilder.java index f22b6c211bf..9623fa78d19 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/devicemanagement/devicecompliancepolicies/item/scheduledactionsforrule/item/DeviceComplianceScheduledActionForRuleItemRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/devicemanagement/devicecompliancepolicies/item/scheduledactionsforrule/item/DeviceComplianceScheduledActionForRuleItemRequestBuilder.java @@ -64,7 +64,7 @@ public void delete(@jakarta.annotation.Nullable final java.util.function.Consume this.requestAdapter.sendPrimitive(requestInfo, errorMapping, Void.class); } /** - * 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. * @return a {@link DeviceComplianceScheduledActionForRule} * @throws ODataError When receiving a 4XX or 5XX status code */ @@ -73,7 +73,7 @@ public DeviceComplianceScheduledActionForRule get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link DeviceComplianceScheduledActionForRule} * @throws ODataError When receiving a 4XX or 5XX status code @@ -131,7 +131,7 @@ public RequestInformation toDeleteRequestInformation(@jakarta.annotation.Nullabl return requestInfo; } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -139,7 +139,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -191,7 +191,7 @@ public DeviceComplianceScheduledActionForRuleItemRequestBuilder withUrl(@jakarta public class DeleteRequestConfiguration extends BaseRequestConfiguration { } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/devicemanagement/virtualendpoint/cloudpcs/item/retrievereviewstatus/RetrieveReviewStatusRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/devicemanagement/virtualendpoint/cloudpcs/item/retrievereviewstatus/RetrieveReviewStatusRequestBuilder.java index 6b80c36a703..49b48af0613 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/devicemanagement/virtualendpoint/cloudpcs/item/retrievereviewstatus/RetrieveReviewStatusRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/devicemanagement/virtualendpoint/cloudpcs/item/retrievereviewstatus/RetrieveReviewStatusRequestBuilder.java @@ -36,19 +36,21 @@ public RetrieveReviewStatusRequestBuilder(@jakarta.annotation.Nonnull final Stri super(requestAdapter, "{+baseurl}/deviceManagement/virtualEndpoint/cloudPCs/{cloudPC%2Did}/retrieveReviewStatus()", rawUrl); } /** - * Invoke function retrieveReviewStatus + * Get the review status of a Cloud PC. * @return a {@link CloudPcReviewStatus} * @throws ODataError When receiving a 4XX or 5XX status code + * @see Find more info here */ @jakarta.annotation.Nullable public CloudPcReviewStatus get() { return get(null); } /** - * Invoke function retrieveReviewStatus + * Get the review status of a Cloud PC. * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link CloudPcReviewStatus} * @throws ODataError When receiving a 4XX or 5XX status code + * @see Find more info here */ @jakarta.annotation.Nullable public CloudPcReviewStatus get(@jakarta.annotation.Nullable final java.util.function.Consumer requestConfiguration) { @@ -58,7 +60,7 @@ public CloudPcReviewStatus get(@jakarta.annotation.Nullable final java.util.func return this.requestAdapter.send(requestInfo, errorMapping, CloudPcReviewStatus::createFromDiscriminatorValue); } /** - * Invoke function retrieveReviewStatus + * Get the review status of a Cloud PC. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -66,7 +68,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * Invoke function retrieveReviewStatus + * Get the review status of a Cloud PC. * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ diff --git a/src/main/java/com/microsoft/graph/beta/generated/devicemanagement/virtualendpoint/cloudpcs/item/retrievesnapshots/RetrieveSnapshotsRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/devicemanagement/virtualendpoint/cloudpcs/item/retrievesnapshots/RetrieveSnapshotsRequestBuilder.java index b7e755262ef..ec43d08340d 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/devicemanagement/virtualendpoint/cloudpcs/item/retrievesnapshots/RetrieveSnapshotsRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/devicemanagement/virtualendpoint/cloudpcs/item/retrievesnapshots/RetrieveSnapshotsRequestBuilder.java @@ -36,19 +36,21 @@ public RetrieveSnapshotsRequestBuilder(@jakarta.annotation.Nonnull final String super(requestAdapter, "{+baseurl}/deviceManagement/virtualEndpoint/cloudPCs/{cloudPC%2Did}/retrieveSnapshots(){?%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * Invoke function retrieveSnapshots + * List all cloudPcSnapshot resources for a Cloud PC. * @return a {@link RetrieveSnapshotsGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code + * @see Find more info here */ @jakarta.annotation.Nullable public RetrieveSnapshotsGetResponse get() { return get(null); } /** - * Invoke function retrieveSnapshots + * List all cloudPcSnapshot resources for a Cloud PC. * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RetrieveSnapshotsGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code + * @see Find more info here */ @jakarta.annotation.Nullable public RetrieveSnapshotsGetResponse get(@jakarta.annotation.Nullable final java.util.function.Consumer requestConfiguration) { @@ -58,7 +60,7 @@ public RetrieveSnapshotsGetResponse get(@jakarta.annotation.Nullable final java. return this.requestAdapter.send(requestInfo, errorMapping, RetrieveSnapshotsGetResponse::createFromDiscriminatorValue); } /** - * Invoke function retrieveSnapshots + * List all cloudPcSnapshot resources for a Cloud PC. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -66,7 +68,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * Invoke function retrieveSnapshots + * List all cloudPcSnapshot resources for a Cloud PC. * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -88,7 +90,7 @@ public RetrieveSnapshotsRequestBuilder withUrl(@jakarta.annotation.Nonnull final return new RetrieveSnapshotsRequestBuilder(rawUrl, requestAdapter); } /** - * Invoke function retrieveSnapshots + * List all cloudPcSnapshot resources for a Cloud PC. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/devicemanagement/virtualendpoint/cloudpcs/item/setreviewstatus/SetReviewStatusRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/devicemanagement/virtualendpoint/cloudpcs/item/setreviewstatus/SetReviewStatusRequestBuilder.java index 0b4cd1fdf8c..62eadc0611a 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/devicemanagement/virtualendpoint/cloudpcs/item/setreviewstatus/SetReviewStatusRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/devicemanagement/virtualendpoint/cloudpcs/item/setreviewstatus/SetReviewStatusRequestBuilder.java @@ -35,18 +35,20 @@ public SetReviewStatusRequestBuilder(@jakarta.annotation.Nonnull final String ra super(requestAdapter, "{+baseurl}/deviceManagement/virtualEndpoint/cloudPCs/{cloudPC%2Did}/setReviewStatus", rawUrl); } /** - * 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 * @throws ODataError When receiving a 4XX or 5XX status code + * @see Find more info here */ public void post(@jakarta.annotation.Nonnull final SetReviewStatusPostRequestBody body) { post(body, null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @throws ODataError When receiving a 4XX or 5XX status code + * @see Find more info here */ public void post(@jakarta.annotation.Nonnull final SetReviewStatusPostRequestBody body, @jakarta.annotation.Nullable final java.util.function.Consumer requestConfiguration) { Objects.requireNonNull(body); @@ -56,7 +58,7 @@ public void post(@jakarta.annotation.Nonnull final SetReviewStatusPostRequestBod this.requestAdapter.sendPrimitive(requestInfo, errorMapping, Void.class); } /** - * 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 * @return a {@link RequestInformation} */ @@ -65,7 +67,7 @@ public RequestInformation toPostRequestInformation(@jakarta.annotation.Nonnull f return toPostRequestInformation(body, null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} diff --git a/src/main/java/com/microsoft/graph/beta/generated/directory/authenticationmethoddevices/AuthenticationMethodDevicesRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/directory/authenticationmethoddevices/AuthenticationMethodDevicesRequestBuilder.java index 39365396806..fed2c610f9c 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/directory/authenticationmethoddevices/AuthenticationMethodDevicesRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/directory/authenticationmethoddevices/AuthenticationMethodDevicesRequestBuilder.java @@ -64,7 +64,7 @@ public void delete(@jakarta.annotation.Nullable final java.util.function.Consume this.requestAdapter.sendPrimitive(requestInfo, errorMapping, Void.class); } /** - * Get authenticationMethodDevices from directory + * Exposes the hardware OATH method in the directory. * @return a {@link AuthenticationMethodDevice} * @throws ODataError When receiving a 4XX or 5XX status code */ @@ -73,7 +73,7 @@ public AuthenticationMethodDevice get() { return get(null); } /** - * Get authenticationMethodDevices from directory + * Exposes the hardware OATH method in the directory. * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link AuthenticationMethodDevice} * @throws ODataError When receiving a 4XX or 5XX status code @@ -131,7 +131,7 @@ public RequestInformation toDeleteRequestInformation(@jakarta.annotation.Nullabl return requestInfo; } /** - * Get authenticationMethodDevices from directory + * Exposes the hardware OATH method in the directory. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -139,7 +139,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * Get authenticationMethodDevices from directory + * Exposes the hardware OATH method in the directory. * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -191,7 +191,7 @@ public AuthenticationMethodDevicesRequestBuilder withUrl(@jakarta.annotation.Non public class DeleteRequestConfiguration extends BaseRequestConfiguration { } /** - * Get authenticationMethodDevices from directory + * Exposes the hardware OATH method in the directory. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/directory/authenticationmethoddevices/hardwareoathdevices/HardwareOathDevicesRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/directory/authenticationmethoddevices/hardwareoathdevices/HardwareOathDevicesRequestBuilder.java index 2b57d31e1c9..3794691dfb6 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/directory/authenticationmethoddevices/hardwareoathdevices/HardwareOathDevicesRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/directory/authenticationmethoddevices/hardwareoathdevices/HardwareOathDevicesRequestBuilder.java @@ -60,19 +60,21 @@ public HardwareOathDevicesRequestBuilder(@jakarta.annotation.Nonnull final Strin super(requestAdapter, "{+baseurl}/directory/authenticationMethodDevices/hardwareOathDevices{?%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * Get hardwareOathDevices from directory + * List all hardware OATH tokens in the directory. * @return a {@link HardwareOathTokenAuthenticationMethodDeviceCollectionResponse} * @throws ODataError When receiving a 4XX or 5XX status code + * @see Find more info here */ @jakarta.annotation.Nullable public HardwareOathTokenAuthenticationMethodDeviceCollectionResponse get() { return get(null); } /** - * Get hardwareOathDevices from directory + * List all hardware OATH tokens in the directory. * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link HardwareOathTokenAuthenticationMethodDeviceCollectionResponse} * @throws ODataError When receiving a 4XX or 5XX status code + * @see Find more info here */ @jakarta.annotation.Nullable public HardwareOathTokenAuthenticationMethodDeviceCollectionResponse get(@jakarta.annotation.Nullable final java.util.function.Consumer requestConfiguration) { @@ -82,21 +84,23 @@ public HardwareOathTokenAuthenticationMethodDeviceCollectionResponse get(@jakart return this.requestAdapter.send(requestInfo, errorMapping, HardwareOathTokenAuthenticationMethodDeviceCollectionResponse::createFromDiscriminatorValue); } /** - * Create new navigation property to hardwareOathDevices for directory + * Create a new hardwareOathTokenAuthenticationMethodDevice object. Supports bulk creation. * @param body The request body * @return a {@link HardwareOathTokenAuthenticationMethodDevice} * @throws ODataError When receiving a 4XX or 5XX status code + * @see Find more info here */ @jakarta.annotation.Nullable public HardwareOathTokenAuthenticationMethodDevice post(@jakarta.annotation.Nonnull final HardwareOathTokenAuthenticationMethodDevice body) { return post(body, null); } /** - * Create new navigation property to hardwareOathDevices for directory + * Create a new hardwareOathTokenAuthenticationMethodDevice object. Supports bulk creation. * @param body The request body * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link HardwareOathTokenAuthenticationMethodDevice} * @throws ODataError When receiving a 4XX or 5XX status code + * @see Find more info here */ @jakarta.annotation.Nullable public HardwareOathTokenAuthenticationMethodDevice post(@jakarta.annotation.Nonnull final HardwareOathTokenAuthenticationMethodDevice body, @jakarta.annotation.Nullable final java.util.function.Consumer requestConfiguration) { @@ -107,7 +111,7 @@ public HardwareOathTokenAuthenticationMethodDevice post(@jakarta.annotation.Nonn return this.requestAdapter.send(requestInfo, errorMapping, HardwareOathTokenAuthenticationMethodDevice::createFromDiscriminatorValue); } /** - * Get hardwareOathDevices from directory + * List all hardware OATH tokens in the directory. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -115,7 +119,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * Get hardwareOathDevices from directory + * List all hardware OATH tokens in the directory. * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -127,7 +131,7 @@ public RequestInformation toGetRequestInformation(@jakarta.annotation.Nullable f return requestInfo; } /** - * Create new navigation property to hardwareOathDevices for directory + * Create a new hardwareOathTokenAuthenticationMethodDevice object. Supports bulk creation. * @param body The request body * @return a {@link RequestInformation} */ @@ -136,7 +140,7 @@ public RequestInformation toPostRequestInformation(@jakarta.annotation.Nonnull f return toPostRequestInformation(body, null); } /** - * Create new navigation property to hardwareOathDevices for directory + * Create a new hardwareOathTokenAuthenticationMethodDevice object. Supports bulk creation. * @param body The request body * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} @@ -161,7 +165,7 @@ public HardwareOathDevicesRequestBuilder withUrl(@jakarta.annotation.Nonnull fin return new HardwareOathDevicesRequestBuilder(rawUrl, requestAdapter); } /** - * Get hardwareOathDevices from directory + * List all hardware OATH tokens in the directory. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/directory/authenticationmethoddevices/hardwareoathdevices/item/HardwareOathTokenAuthenticationMethodDeviceItemRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/directory/authenticationmethoddevices/hardwareoathdevices/item/HardwareOathTokenAuthenticationMethodDeviceItemRequestBuilder.java index 2ef9d685b89..3433d736d34 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/directory/authenticationmethoddevices/hardwareoathdevices/item/HardwareOathTokenAuthenticationMethodDeviceItemRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/directory/authenticationmethoddevices/hardwareoathdevices/item/HardwareOathTokenAuthenticationMethodDeviceItemRequestBuilder.java @@ -46,16 +46,18 @@ public HardwareOathTokenAuthenticationMethodDeviceItemRequestBuilder(@jakarta.an super(requestAdapter, "{+baseurl}/directory/authenticationMethodDevices/hardwareOathDevices/{hardwareOathTokenAuthenticationMethodDevice%2Did}{?%24expand,%24select}", rawUrl); } /** - * Delete navigation property hardwareOathDevices for directory + * Delete a Hardware OATH token. Token needs to be unassigned. * @throws ODataError When receiving a 4XX or 5XX status code + * @see Find more info here */ public void delete() { delete(null); } /** - * Delete navigation property hardwareOathDevices for directory + * Delete a Hardware OATH token. Token needs to be unassigned. * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @throws ODataError When receiving a 4XX or 5XX status code + * @see Find more info here */ public void delete(@jakarta.annotation.Nullable final java.util.function.Consumer requestConfiguration) { final RequestInformation requestInfo = toDeleteRequestInformation(requestConfiguration); @@ -64,19 +66,21 @@ public void delete(@jakarta.annotation.Nullable final java.util.function.Consume this.requestAdapter.sendPrimitive(requestInfo, errorMapping, Void.class); } /** - * Get hardwareOathDevices from directory + * Read the properties and relationships of a hardwareOathTokenAuthenticationMethodDevice object. * @return a {@link HardwareOathTokenAuthenticationMethodDevice} * @throws ODataError When receiving a 4XX or 5XX status code + * @see Find more info here */ @jakarta.annotation.Nullable public HardwareOathTokenAuthenticationMethodDevice get() { return get(null); } /** - * Get hardwareOathDevices from directory + * Read the properties and relationships of a hardwareOathTokenAuthenticationMethodDevice object. * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link HardwareOathTokenAuthenticationMethodDevice} * @throws ODataError When receiving a 4XX or 5XX status code + * @see Find more info here */ @jakarta.annotation.Nullable public HardwareOathTokenAuthenticationMethodDevice get(@jakarta.annotation.Nullable final java.util.function.Consumer requestConfiguration) { @@ -86,21 +90,23 @@ public HardwareOathTokenAuthenticationMethodDevice get(@jakarta.annotation.Nulla return this.requestAdapter.send(requestInfo, errorMapping, HardwareOathTokenAuthenticationMethodDevice::createFromDiscriminatorValue); } /** - * Update the navigation property hardwareOathDevices in directory + * Update the properties of a hardwareOathTokenAuthenticationMethodDevice object. The token needs to unassigned. * @param body The request body * @return a {@link HardwareOathTokenAuthenticationMethodDevice} * @throws ODataError When receiving a 4XX or 5XX status code + * @see Find more info here */ @jakarta.annotation.Nullable public HardwareOathTokenAuthenticationMethodDevice patch(@jakarta.annotation.Nonnull final HardwareOathTokenAuthenticationMethodDevice body) { return patch(body, null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link HardwareOathTokenAuthenticationMethodDevice} * @throws ODataError When receiving a 4XX or 5XX status code + * @see Find more info here */ @jakarta.annotation.Nullable public HardwareOathTokenAuthenticationMethodDevice patch(@jakarta.annotation.Nonnull final HardwareOathTokenAuthenticationMethodDevice body, @jakarta.annotation.Nullable final java.util.function.Consumer requestConfiguration) { @@ -111,7 +117,7 @@ public HardwareOathTokenAuthenticationMethodDevice patch(@jakarta.annotation.Non return this.requestAdapter.send(requestInfo, errorMapping, HardwareOathTokenAuthenticationMethodDevice::createFromDiscriminatorValue); } /** - * Delete navigation property hardwareOathDevices for directory + * Delete a Hardware OATH token. Token needs to be unassigned. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -119,7 +125,7 @@ public RequestInformation toDeleteRequestInformation() { return toDeleteRequestInformation(null); } /** - * Delete navigation property hardwareOathDevices for directory + * Delete a Hardware OATH token. Token needs to be unassigned. * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -131,7 +137,7 @@ public RequestInformation toDeleteRequestInformation(@jakarta.annotation.Nullabl return requestInfo; } /** - * Get hardwareOathDevices from directory + * Read the properties and relationships of a hardwareOathTokenAuthenticationMethodDevice object. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -139,7 +145,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * Get hardwareOathDevices from directory + * Read the properties and relationships of a hardwareOathTokenAuthenticationMethodDevice object. * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -151,7 +157,7 @@ public RequestInformation toGetRequestInformation(@jakarta.annotation.Nullable f return requestInfo; } /** - * Update the navigation property hardwareOathDevices in directory + * Update the properties of a hardwareOathTokenAuthenticationMethodDevice object. The token needs to unassigned. * @param body The request body * @return a {@link RequestInformation} */ @@ -160,7 +166,7 @@ public RequestInformation toPatchRequestInformation(@jakarta.annotation.Nonnull return toPatchRequestInformation(body, null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} @@ -191,7 +197,7 @@ public HardwareOathTokenAuthenticationMethodDeviceItemRequestBuilder withUrl(@ja public class DeleteRequestConfiguration extends BaseRequestConfiguration { } /** - * Get hardwareOathDevices from directory + * Read the properties and relationships of a hardwareOathTokenAuthenticationMethodDevice object. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/directory/authenticationmethoddevices/hardwareoathdevices/item/assignto/AssignToRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/directory/authenticationmethoddevices/hardwareoathdevices/item/assignto/AssignToRequestBuilder.java index d8a25f3d685..682dfefd442 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/directory/authenticationmethoddevices/hardwareoathdevices/item/assignto/AssignToRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/directory/authenticationmethoddevices/hardwareoathdevices/item/assignto/AssignToRequestBuilder.java @@ -55,7 +55,7 @@ public AssignToRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @ super(requestAdapter, "{+baseurl}/directory/authenticationMethodDevices/hardwareOathDevices/{hardwareOathTokenAuthenticationMethodDevice%2Did}/assignTo{?%24expand,%24select}", rawUrl); } /** - * Get assignTo from directory + * Assign the hardware OATH token to a user. * @return a {@link User} * @throws ODataError When receiving a 4XX or 5XX status code */ @@ -64,7 +64,7 @@ public User get() { return get(null); } /** - * Get assignTo from directory + * Assign the hardware OATH token to a user. * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link User} * @throws ODataError When receiving a 4XX or 5XX status code @@ -77,7 +77,7 @@ public User get(@jakarta.annotation.Nullable final java.util.function.ConsumerFind more info here + * @see Find more info here */ @jakarta.annotation.Nullable public WorkbookTable post(@jakarta.annotation.Nonnull final AddPostRequestBody body) { return post(body, null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link WorkbookTable} * @throws ODataError When receiving a 4XX or 5XX status code - * @see Find more info here + * @see Find more info here */ @jakarta.annotation.Nullable public WorkbookTable post(@jakarta.annotation.Nonnull final AddPostRequestBody body, @jakarta.annotation.Nullable final java.util.function.Consumer requestConfiguration) { @@ -63,7 +63,7 @@ public WorkbookTable post(@jakarta.annotation.Nonnull final AddPostRequestBody b return this.requestAdapter.send(requestInfo, errorMapping, WorkbookTable::createFromDiscriminatorValue); } /** - * 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 * @return a {@link RequestInformation} */ @@ -72,7 +72,7 @@ public RequestInformation toPostRequestInformation(@jakarta.annotation.Nonnull f return toPostRequestInformation(body, null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} diff --git a/src/main/java/com/microsoft/graph/beta/generated/drives/item/items/item/workbook/worksheets/item/tables/add/AddRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/drives/item/items/item/workbook/worksheets/item/tables/add/AddRequestBuilder.java index 1eff2c749f4..2b5f324c12d 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/drives/item/items/item/workbook/worksheets/item/tables/add/AddRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/drives/item/items/item/workbook/worksheets/item/tables/add/AddRequestBuilder.java @@ -36,23 +36,23 @@ public AddRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @jakar super(requestAdapter, "{+baseurl}/drives/{drive%2Did}/items/{driveItem%2Did}/workbook/worksheets/{workbookWorksheet%2Did}/tables/add", rawUrl); } /** - * 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 * @return a {@link WorkbookTable} * @throws ODataError When receiving a 4XX or 5XX status code - * @see Find more info here + * @see Find more info here */ @jakarta.annotation.Nullable public WorkbookTable post(@jakarta.annotation.Nonnull final AddPostRequestBody body) { return post(body, null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link WorkbookTable} * @throws ODataError When receiving a 4XX or 5XX status code - * @see Find more info here + * @see Find more info here */ @jakarta.annotation.Nullable public WorkbookTable post(@jakarta.annotation.Nonnull final AddPostRequestBody body, @jakarta.annotation.Nullable final java.util.function.Consumer requestConfiguration) { @@ -63,7 +63,7 @@ public WorkbookTable post(@jakarta.annotation.Nonnull final AddPostRequestBody b return this.requestAdapter.send(requestInfo, errorMapping, WorkbookTable::createFromDiscriminatorValue); } /** - * 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 * @return a {@link RequestInformation} */ @@ -72,7 +72,7 @@ public RequestInformation toPostRequestInformation(@jakarta.annotation.Nonnull f return toPostRequestInformation(body, null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} diff --git a/src/main/java/com/microsoft/graph/beta/generated/external/authorizationsystems/item/AuthorizationSystemItemRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/external/authorizationsystems/item/AuthorizationSystemItemRequestBuilder.java index 79b9a5abc30..72223c15f22 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/external/authorizationsystems/item/AuthorizationSystemItemRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/external/authorizationsystems/item/AuthorizationSystemItemRequestBuilder.java @@ -64,7 +64,7 @@ public void delete(@jakarta.annotation.Nullable final java.util.function.Consume this.requestAdapter.sendPrimitive(requestInfo, errorMapping, Void.class); } /** - * 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. * @return a {@link AuthorizationSystem} * @throws ODataError When receiving a 4XX or 5XX status code */ @@ -73,7 +73,7 @@ public AuthorizationSystem get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link AuthorizationSystem} * @throws ODataError When receiving a 4XX or 5XX status code @@ -131,7 +131,7 @@ public RequestInformation toDeleteRequestInformation(@jakarta.annotation.Nullabl return requestInfo; } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -139,7 +139,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -191,7 +191,7 @@ public AuthorizationSystemItemRequestBuilder withUrl(@jakarta.annotation.Nonnull public class DeleteRequestConfiguration extends BaseRequestConfiguration { } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/external/connections/item/schema/SchemaRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/external/connections/item/schema/SchemaRequestBuilder.java index 0aee76cfb16..05701d147cd 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/external/connections/item/schema/SchemaRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/external/connections/item/schema/SchemaRequestBuilder.java @@ -61,23 +61,23 @@ public Schema get(@jakarta.annotation.Nullable final java.util.function.Consumer return this.requestAdapter.send(requestInfo, errorMapping, Schema::createFromDiscriminatorValue); } /** - * 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 * @return a {@link Schema} * @throws ODataError When receiving a 4XX or 5XX status code - * @see Find more info here + * @see Find more info here */ @jakarta.annotation.Nullable public Schema patch(@jakarta.annotation.Nonnull final Schema body) { return patch(body, null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link Schema} * @throws ODataError When receiving a 4XX or 5XX status code - * @see Find more info here + * @see Find more info here */ @jakarta.annotation.Nullable public Schema patch(@jakarta.annotation.Nonnull final Schema body, @jakarta.annotation.Nullable final java.util.function.Consumer requestConfiguration) { @@ -108,7 +108,7 @@ public RequestInformation toGetRequestInformation(@jakarta.annotation.Nullable f return requestInfo; } /** - * 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 * @return a {@link RequestInformation} */ @@ -117,7 +117,7 @@ public RequestInformation toPatchRequestInformation(@jakarta.annotation.Nonnull return toPatchRequestInformation(body, null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} diff --git a/src/main/java/com/microsoft/graph/beta/generated/external/industrydata/dataconnectors/DataConnectorsRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/external/industrydata/dataconnectors/DataConnectorsRequestBuilder.java index 968f017efcc..ee0c87ba44e 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/external/industrydata/dataconnectors/DataConnectorsRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/external/industrydata/dataconnectors/DataConnectorsRequestBuilder.java @@ -84,23 +84,23 @@ public IndustryDataConnectorCollectionResponse get(@jakarta.annotation.Nullable return this.requestAdapter.send(requestInfo, errorMapping, IndustryDataConnectorCollectionResponse::createFromDiscriminatorValue); } /** - * Create a new azureDataLakeConnector object. + * Create a new oneRosterApiDataConnector object. * @param body The request body * @return a {@link IndustryDataConnector} * @throws ODataError When receiving a 4XX or 5XX status code - * @see Find more info here + * @see Find more info here */ @jakarta.annotation.Nullable public IndustryDataConnector post(@jakarta.annotation.Nonnull final IndustryDataConnector body) { return post(body, null); } /** - * Create a new azureDataLakeConnector object. + * Create a new oneRosterApiDataConnector object. * @param body The request body * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link IndustryDataConnector} * @throws ODataError When receiving a 4XX or 5XX status code - * @see Find more info here + * @see Find more info here */ @jakarta.annotation.Nullable public IndustryDataConnector post(@jakarta.annotation.Nonnull final IndustryDataConnector body, @jakarta.annotation.Nullable final java.util.function.Consumer requestConfiguration) { @@ -131,7 +131,7 @@ public RequestInformation toGetRequestInformation(@jakarta.annotation.Nullable f return requestInfo; } /** - * Create a new azureDataLakeConnector object. + * Create a new oneRosterApiDataConnector object. * @param body The request body * @return a {@link RequestInformation} */ @@ -140,7 +140,7 @@ public RequestInformation toPostRequestInformation(@jakarta.annotation.Nonnull f return toPostRequestInformation(body, null); } /** - * Create a new azureDataLakeConnector object. + * Create a new oneRosterApiDataConnector object. * @param body The request body * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} diff --git a/src/main/java/com/microsoft/graph/beta/generated/external/industrydata/inboundflows/InboundFlowsRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/external/industrydata/inboundflows/InboundFlowsRequestBuilder.java index 5d7d5ff3e56..adb3ef364d6 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/external/industrydata/inboundflows/InboundFlowsRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/external/industrydata/inboundflows/InboundFlowsRequestBuilder.java @@ -84,23 +84,23 @@ public InboundFlowCollectionResponse get(@jakarta.annotation.Nullable final java return this.requestAdapter.send(requestInfo, errorMapping, InboundFlowCollectionResponse::createFromDiscriminatorValue); } /** - * Create a new inboundFileFlow object. + * Create a new inboundApiFlow object. * @param body The request body * @return a {@link InboundFlow} * @throws ODataError When receiving a 4XX or 5XX status code - * @see Find more info here + * @see Find more info here */ @jakarta.annotation.Nullable public InboundFlow post(@jakarta.annotation.Nonnull final InboundFlow body) { return post(body, null); } /** - * Create a new inboundFileFlow object. + * Create a new inboundApiFlow object. * @param body The request body * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link InboundFlow} * @throws ODataError When receiving a 4XX or 5XX status code - * @see Find more info here + * @see Find more info here */ @jakarta.annotation.Nullable public InboundFlow post(@jakarta.annotation.Nonnull final InboundFlow body, @jakarta.annotation.Nullable final java.util.function.Consumer requestConfiguration) { @@ -131,7 +131,7 @@ public RequestInformation toGetRequestInformation(@jakarta.annotation.Nullable f return requestInfo; } /** - * Create a new inboundFileFlow object. + * Create a new inboundApiFlow object. * @param body The request body * @return a {@link RequestInformation} */ @@ -140,7 +140,7 @@ public RequestInformation toPostRequestInformation(@jakarta.annotation.Nonnull f return toPostRequestInformation(body, null); } /** - * Create a new inboundFileFlow object. + * Create a new inboundApiFlow object. * @param body The request body * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} diff --git a/src/main/java/com/microsoft/graph/beta/generated/groups/GroupsRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/groups/GroupsRequestBuilder.java index cb2fd935ec2..ae9adcbc3b1 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/groups/GroupsRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/groups/GroupsRequestBuilder.java @@ -129,23 +129,23 @@ public GroupCollectionResponse get(@jakarta.annotation.Nullable final java.util. return this.requestAdapter.send(requestInfo, errorMapping, GroupCollectionResponse::createFromDiscriminatorValue); } /** - * 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 * @return a {@link Group} * @throws ODataError When receiving a 4XX or 5XX status code - * @see Find more info here + * @see Find more info here */ @jakarta.annotation.Nullable public Group post(@jakarta.annotation.Nonnull final Group body) { return post(body, null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link Group} * @throws ODataError When receiving a 4XX or 5XX status code - * @see Find more info here + * @see Find more info here */ @jakarta.annotation.Nullable public Group post(@jakarta.annotation.Nonnull final Group body, @jakarta.annotation.Nullable final java.util.function.Consumer requestConfiguration) { @@ -176,7 +176,7 @@ public RequestInformation toGetRequestInformation(@jakarta.annotation.Nullable f return requestInfo; } /** - * 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 * @return a {@link RequestInformation} */ @@ -185,7 +185,7 @@ public RequestInformation toPostRequestInformation(@jakarta.annotation.Nonnull f return toPostRequestInformation(body, null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} diff --git a/src/main/java/com/microsoft/graph/beta/generated/groups/item/calendar/calendarview/delta/DeltaRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/groups/item/calendar/calendarview/delta/DeltaRequestBuilder.java index d444870bfbd..fd736c5a800 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/groups/item/calendar/calendarview/delta/DeltaRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/groups/item/calendar/calendarview/delta/DeltaRequestBuilder.java @@ -36,7 +36,7 @@ public DeltaRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @jak super(requestAdapter, "{+baseurl}/groups/{group%2Did}/calendar/calendarView/delta()?endDateTime={endDateTime}&startDateTime={startDateTime}{&%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * 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. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code * @see Find more info here @@ -46,7 +46,7 @@ public DeltaGetResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -60,7 +60,7 @@ public DeltaGetResponse get(@jakarta.annotation.Nullable final java.util.functio return this.requestAdapter.send(requestInfo, errorMapping, DeltaGetResponse::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -68,7 +68,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -90,7 +90,7 @@ public DeltaRequestBuilder withUrl(@jakarta.annotation.Nonnull final String rawU return new DeltaRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/groups/item/calendar/calendarview/item/exceptionoccurrences/delta/DeltaRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/groups/item/calendar/calendarview/item/exceptionoccurrences/delta/DeltaRequestBuilder.java index d03e5669154..ced19383e40 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/groups/item/calendar/calendarview/item/exceptionoccurrences/delta/DeltaRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/groups/item/calendar/calendarview/item/exceptionoccurrences/delta/DeltaRequestBuilder.java @@ -36,7 +36,7 @@ public DeltaRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @jak super(requestAdapter, "{+baseurl}/groups/{group%2Did}/calendar/calendarView/{event%2Did}/exceptionOccurrences/delta()?endDateTime={endDateTime}&startDateTime={startDateTime}{&%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * 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. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code * @see Find more info here @@ -46,7 +46,7 @@ public DeltaGetResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -60,7 +60,7 @@ public DeltaGetResponse get(@jakarta.annotation.Nullable final java.util.functio return this.requestAdapter.send(requestInfo, errorMapping, DeltaGetResponse::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -68,7 +68,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -90,7 +90,7 @@ public DeltaRequestBuilder withUrl(@jakarta.annotation.Nonnull final String rawU return new DeltaRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/groups/item/calendar/calendarview/item/exceptionoccurrences/item/instances/delta/DeltaRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/groups/item/calendar/calendarview/item/exceptionoccurrences/item/instances/delta/DeltaRequestBuilder.java index b9e32da7242..a766d39e7c8 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/groups/item/calendar/calendarview/item/exceptionoccurrences/item/instances/delta/DeltaRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/groups/item/calendar/calendarview/item/exceptionoccurrences/item/instances/delta/DeltaRequestBuilder.java @@ -36,7 +36,7 @@ public DeltaRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @jak super(requestAdapter, "{+baseurl}/groups/{group%2Did}/calendar/calendarView/{event%2Did}/exceptionOccurrences/{event%2Did1}/instances/delta()?endDateTime={endDateTime}&startDateTime={startDateTime}{&%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * 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. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code * @see Find more info here @@ -46,7 +46,7 @@ public DeltaGetResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -60,7 +60,7 @@ public DeltaGetResponse get(@jakarta.annotation.Nullable final java.util.functio return this.requestAdapter.send(requestInfo, errorMapping, DeltaGetResponse::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -68,7 +68,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -90,7 +90,7 @@ public DeltaRequestBuilder withUrl(@jakarta.annotation.Nonnull final String rawU return new DeltaRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/groups/item/calendar/calendarview/item/instances/delta/DeltaRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/groups/item/calendar/calendarview/item/instances/delta/DeltaRequestBuilder.java index 813414d5b52..ec61d3e5068 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/groups/item/calendar/calendarview/item/instances/delta/DeltaRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/groups/item/calendar/calendarview/item/instances/delta/DeltaRequestBuilder.java @@ -36,7 +36,7 @@ public DeltaRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @jak super(requestAdapter, "{+baseurl}/groups/{group%2Did}/calendar/calendarView/{event%2Did}/instances/delta()?endDateTime={endDateTime}&startDateTime={startDateTime}{&%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * 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. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code * @see Find more info here @@ -46,7 +46,7 @@ public DeltaGetResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -60,7 +60,7 @@ public DeltaGetResponse get(@jakarta.annotation.Nullable final java.util.functio return this.requestAdapter.send(requestInfo, errorMapping, DeltaGetResponse::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -68,7 +68,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -90,7 +90,7 @@ public DeltaRequestBuilder withUrl(@jakarta.annotation.Nonnull final String rawU return new DeltaRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/groups/item/calendar/calendarview/item/instances/item/exceptionoccurrences/delta/DeltaRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/groups/item/calendar/calendarview/item/instances/item/exceptionoccurrences/delta/DeltaRequestBuilder.java index cf0c07691a1..8efc241913c 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/groups/item/calendar/calendarview/item/instances/item/exceptionoccurrences/delta/DeltaRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/groups/item/calendar/calendarview/item/instances/item/exceptionoccurrences/delta/DeltaRequestBuilder.java @@ -36,7 +36,7 @@ public DeltaRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @jak super(requestAdapter, "{+baseurl}/groups/{group%2Did}/calendar/calendarView/{event%2Did}/instances/{event%2Did1}/exceptionOccurrences/delta()?endDateTime={endDateTime}&startDateTime={startDateTime}{&%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * 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. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code * @see Find more info here @@ -46,7 +46,7 @@ public DeltaGetResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -60,7 +60,7 @@ public DeltaGetResponse get(@jakarta.annotation.Nullable final java.util.functio return this.requestAdapter.send(requestInfo, errorMapping, DeltaGetResponse::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -68,7 +68,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -90,7 +90,7 @@ public DeltaRequestBuilder withUrl(@jakarta.annotation.Nonnull final String rawU return new DeltaRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/groups/item/calendar/events/delta/DeltaRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/groups/item/calendar/events/delta/DeltaRequestBuilder.java index ceec8149894..a54a25964d4 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/groups/item/calendar/events/delta/DeltaRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/groups/item/calendar/events/delta/DeltaRequestBuilder.java @@ -36,7 +36,7 @@ public DeltaRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @jak super(requestAdapter, "{+baseurl}/groups/{group%2Did}/calendar/events/delta()?endDateTime={endDateTime}&startDateTime={startDateTime}{&%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * 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. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code * @see Find more info here @@ -46,7 +46,7 @@ public DeltaGetResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -60,7 +60,7 @@ public DeltaGetResponse get(@jakarta.annotation.Nullable final java.util.functio return this.requestAdapter.send(requestInfo, errorMapping, DeltaGetResponse::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -68,7 +68,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -90,7 +90,7 @@ public DeltaRequestBuilder withUrl(@jakarta.annotation.Nonnull final String rawU return new DeltaRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/groups/item/calendar/events/item/exceptionoccurrences/delta/DeltaRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/groups/item/calendar/events/item/exceptionoccurrences/delta/DeltaRequestBuilder.java index c90b7e8c868..ef10bd69901 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/groups/item/calendar/events/item/exceptionoccurrences/delta/DeltaRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/groups/item/calendar/events/item/exceptionoccurrences/delta/DeltaRequestBuilder.java @@ -36,7 +36,7 @@ public DeltaRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @jak super(requestAdapter, "{+baseurl}/groups/{group%2Did}/calendar/events/{event%2Did}/exceptionOccurrences/delta()?endDateTime={endDateTime}&startDateTime={startDateTime}{&%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * 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. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code * @see Find more info here @@ -46,7 +46,7 @@ public DeltaGetResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -60,7 +60,7 @@ public DeltaGetResponse get(@jakarta.annotation.Nullable final java.util.functio return this.requestAdapter.send(requestInfo, errorMapping, DeltaGetResponse::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -68,7 +68,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -90,7 +90,7 @@ public DeltaRequestBuilder withUrl(@jakarta.annotation.Nonnull final String rawU return new DeltaRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/groups/item/calendar/events/item/exceptionoccurrences/item/instances/delta/DeltaRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/groups/item/calendar/events/item/exceptionoccurrences/item/instances/delta/DeltaRequestBuilder.java index 82e0e5c0a45..b924f0ea5e8 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/groups/item/calendar/events/item/exceptionoccurrences/item/instances/delta/DeltaRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/groups/item/calendar/events/item/exceptionoccurrences/item/instances/delta/DeltaRequestBuilder.java @@ -36,7 +36,7 @@ public DeltaRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @jak super(requestAdapter, "{+baseurl}/groups/{group%2Did}/calendar/events/{event%2Did}/exceptionOccurrences/{event%2Did1}/instances/delta()?endDateTime={endDateTime}&startDateTime={startDateTime}{&%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * 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. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code * @see Find more info here @@ -46,7 +46,7 @@ public DeltaGetResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -60,7 +60,7 @@ public DeltaGetResponse get(@jakarta.annotation.Nullable final java.util.functio return this.requestAdapter.send(requestInfo, errorMapping, DeltaGetResponse::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -68,7 +68,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -90,7 +90,7 @@ public DeltaRequestBuilder withUrl(@jakarta.annotation.Nonnull final String rawU return new DeltaRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/groups/item/calendar/events/item/instances/delta/DeltaRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/groups/item/calendar/events/item/instances/delta/DeltaRequestBuilder.java index a5eaa431345..39e697c65f7 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/groups/item/calendar/events/item/instances/delta/DeltaRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/groups/item/calendar/events/item/instances/delta/DeltaRequestBuilder.java @@ -36,7 +36,7 @@ public DeltaRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @jak super(requestAdapter, "{+baseurl}/groups/{group%2Did}/calendar/events/{event%2Did}/instances/delta()?endDateTime={endDateTime}&startDateTime={startDateTime}{&%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * 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. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code * @see Find more info here @@ -46,7 +46,7 @@ public DeltaGetResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -60,7 +60,7 @@ public DeltaGetResponse get(@jakarta.annotation.Nullable final java.util.functio return this.requestAdapter.send(requestInfo, errorMapping, DeltaGetResponse::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -68,7 +68,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -90,7 +90,7 @@ public DeltaRequestBuilder withUrl(@jakarta.annotation.Nonnull final String rawU return new DeltaRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/groups/item/calendar/events/item/instances/item/exceptionoccurrences/delta/DeltaRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/groups/item/calendar/events/item/instances/item/exceptionoccurrences/delta/DeltaRequestBuilder.java index d5f9af2fe87..7bb1b4ae7bd 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/groups/item/calendar/events/item/instances/item/exceptionoccurrences/delta/DeltaRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/groups/item/calendar/events/item/instances/item/exceptionoccurrences/delta/DeltaRequestBuilder.java @@ -36,7 +36,7 @@ public DeltaRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @jak super(requestAdapter, "{+baseurl}/groups/{group%2Did}/calendar/events/{event%2Did}/instances/{event%2Did1}/exceptionOccurrences/delta()?endDateTime={endDateTime}&startDateTime={startDateTime}{&%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * 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. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code * @see Find more info here @@ -46,7 +46,7 @@ public DeltaGetResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -60,7 +60,7 @@ public DeltaGetResponse get(@jakarta.annotation.Nullable final java.util.functio return this.requestAdapter.send(requestInfo, errorMapping, DeltaGetResponse::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -68,7 +68,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -90,7 +90,7 @@ public DeltaRequestBuilder withUrl(@jakarta.annotation.Nonnull final String rawU return new DeltaRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/groups/item/calendarview/delta/DeltaRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/groups/item/calendarview/delta/DeltaRequestBuilder.java index 99d3880b99b..255584dfd81 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/groups/item/calendarview/delta/DeltaRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/groups/item/calendarview/delta/DeltaRequestBuilder.java @@ -36,7 +36,7 @@ public DeltaRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @jak super(requestAdapter, "{+baseurl}/groups/{group%2Did}/calendarView/delta()?endDateTime={endDateTime}&startDateTime={startDateTime}{&%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * 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. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code * @see Find more info here @@ -46,7 +46,7 @@ public DeltaGetResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -60,7 +60,7 @@ public DeltaGetResponse get(@jakarta.annotation.Nullable final java.util.functio return this.requestAdapter.send(requestInfo, errorMapping, DeltaGetResponse::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -68,7 +68,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -90,7 +90,7 @@ public DeltaRequestBuilder withUrl(@jakarta.annotation.Nonnull final String rawU return new DeltaRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/groups/item/calendarview/item/exceptionoccurrences/delta/DeltaRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/groups/item/calendarview/item/exceptionoccurrences/delta/DeltaRequestBuilder.java index 2fee6f44afc..cf80ea905cc 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/groups/item/calendarview/item/exceptionoccurrences/delta/DeltaRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/groups/item/calendarview/item/exceptionoccurrences/delta/DeltaRequestBuilder.java @@ -36,7 +36,7 @@ public DeltaRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @jak super(requestAdapter, "{+baseurl}/groups/{group%2Did}/calendarView/{event%2Did}/exceptionOccurrences/delta()?endDateTime={endDateTime}&startDateTime={startDateTime}{&%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * 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. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code * @see Find more info here @@ -46,7 +46,7 @@ public DeltaGetResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -60,7 +60,7 @@ public DeltaGetResponse get(@jakarta.annotation.Nullable final java.util.functio return this.requestAdapter.send(requestInfo, errorMapping, DeltaGetResponse::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -68,7 +68,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -90,7 +90,7 @@ public DeltaRequestBuilder withUrl(@jakarta.annotation.Nonnull final String rawU return new DeltaRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/groups/item/calendarview/item/exceptionoccurrences/item/instances/delta/DeltaRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/groups/item/calendarview/item/exceptionoccurrences/item/instances/delta/DeltaRequestBuilder.java index 436d865add3..bd8b24c4724 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/groups/item/calendarview/item/exceptionoccurrences/item/instances/delta/DeltaRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/groups/item/calendarview/item/exceptionoccurrences/item/instances/delta/DeltaRequestBuilder.java @@ -36,7 +36,7 @@ public DeltaRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @jak super(requestAdapter, "{+baseurl}/groups/{group%2Did}/calendarView/{event%2Did}/exceptionOccurrences/{event%2Did1}/instances/delta()?endDateTime={endDateTime}&startDateTime={startDateTime}{&%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * 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. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code * @see Find more info here @@ -46,7 +46,7 @@ public DeltaGetResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -60,7 +60,7 @@ public DeltaGetResponse get(@jakarta.annotation.Nullable final java.util.functio return this.requestAdapter.send(requestInfo, errorMapping, DeltaGetResponse::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -68,7 +68,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -90,7 +90,7 @@ public DeltaRequestBuilder withUrl(@jakarta.annotation.Nonnull final String rawU return new DeltaRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/groups/item/calendarview/item/instances/delta/DeltaRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/groups/item/calendarview/item/instances/delta/DeltaRequestBuilder.java index b4b2e19a154..97c9d028921 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/groups/item/calendarview/item/instances/delta/DeltaRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/groups/item/calendarview/item/instances/delta/DeltaRequestBuilder.java @@ -36,7 +36,7 @@ public DeltaRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @jak super(requestAdapter, "{+baseurl}/groups/{group%2Did}/calendarView/{event%2Did}/instances/delta()?endDateTime={endDateTime}&startDateTime={startDateTime}{&%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * 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. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code * @see Find more info here @@ -46,7 +46,7 @@ public DeltaGetResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -60,7 +60,7 @@ public DeltaGetResponse get(@jakarta.annotation.Nullable final java.util.functio return this.requestAdapter.send(requestInfo, errorMapping, DeltaGetResponse::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -68,7 +68,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -90,7 +90,7 @@ public DeltaRequestBuilder withUrl(@jakarta.annotation.Nonnull final String rawU return new DeltaRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/groups/item/calendarview/item/instances/item/exceptionoccurrences/delta/DeltaRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/groups/item/calendarview/item/instances/item/exceptionoccurrences/delta/DeltaRequestBuilder.java index ae91cdda6b3..0976b62cda8 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/groups/item/calendarview/item/instances/item/exceptionoccurrences/delta/DeltaRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/groups/item/calendarview/item/instances/item/exceptionoccurrences/delta/DeltaRequestBuilder.java @@ -36,7 +36,7 @@ public DeltaRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @jak super(requestAdapter, "{+baseurl}/groups/{group%2Did}/calendarView/{event%2Did}/instances/{event%2Did1}/exceptionOccurrences/delta()?endDateTime={endDateTime}&startDateTime={startDateTime}{&%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * 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. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code * @see Find more info here @@ -46,7 +46,7 @@ public DeltaGetResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -60,7 +60,7 @@ public DeltaGetResponse get(@jakarta.annotation.Nullable final java.util.functio return this.requestAdapter.send(requestInfo, errorMapping, DeltaGetResponse::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -68,7 +68,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -90,7 +90,7 @@ public DeltaRequestBuilder withUrl(@jakarta.annotation.Nonnull final String rawU return new DeltaRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/groups/item/conversations/ConversationsRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/groups/item/conversations/ConversationsRequestBuilder.java index d101eebe4fb..0d4a96e9fbd 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/groups/item/conversations/ConversationsRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/groups/item/conversations/ConversationsRequestBuilder.java @@ -84,23 +84,23 @@ public ConversationCollectionResponse get(@jakarta.annotation.Nullable final jav return this.requestAdapter.send(requestInfo, errorMapping, ConversationCollectionResponse::createFromDiscriminatorValue); } /** - * 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 * @return a {@link Conversation} * @throws ODataError When receiving a 4XX or 5XX status code - * @see Find more info here + * @see Find more info here */ @jakarta.annotation.Nullable public Conversation post(@jakarta.annotation.Nonnull final Conversation body) { return post(body, null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link Conversation} * @throws ODataError When receiving a 4XX or 5XX status code - * @see Find more info here + * @see Find more info here */ @jakarta.annotation.Nullable public Conversation post(@jakarta.annotation.Nonnull final Conversation body, @jakarta.annotation.Nullable final java.util.function.Consumer requestConfiguration) { @@ -131,7 +131,7 @@ public RequestInformation toGetRequestInformation(@jakarta.annotation.Nullable f return requestInfo; } /** - * 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 * @return a {@link RequestInformation} */ @@ -140,7 +140,7 @@ public RequestInformation toPostRequestInformation(@jakarta.annotation.Nonnull f return toPostRequestInformation(body, null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} diff --git a/src/main/java/com/microsoft/graph/beta/generated/groups/item/conversations/item/ConversationItemRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/groups/item/conversations/item/ConversationItemRequestBuilder.java index 140bf5014ec..9b86a4c5e74 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/groups/item/conversations/item/ConversationItemRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/groups/item/conversations/item/ConversationItemRequestBuilder.java @@ -46,18 +46,18 @@ public ConversationItemRequestBuilder(@jakarta.annotation.Nonnull final String r super(requestAdapter, "{+baseurl}/groups/{group%2Did}/conversations/{conversation%2Did}{?%24expand,%24select}", rawUrl); } /** - * Delete conversation. + * Delete a group's conversation object. * @throws ODataError When receiving a 4XX or 5XX status code - * @see Find more info here + * @see Find more info here */ public void delete() { delete(null); } /** - * Delete conversation. + * Delete a group's conversation object. * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @throws ODataError When receiving a 4XX or 5XX status code - * @see Find more info here + * @see Find more info here */ public void delete(@jakarta.annotation.Nullable final java.util.function.Consumer requestConfiguration) { final RequestInformation requestInfo = toDeleteRequestInformation(requestConfiguration); @@ -66,21 +66,21 @@ public void delete(@jakarta.annotation.Nullable final java.util.function.Consume this.requestAdapter.sendPrimitive(requestInfo, errorMapping, Void.class); } /** - * Retrieve the properties and relationships of conversation object. + * Get a group's conversation object. * @return a {@link Conversation} * @throws ODataError When receiving a 4XX or 5XX status code - * @see Find more info here + * @see Find more info here */ @jakarta.annotation.Nullable public Conversation get() { return get(null); } /** - * Retrieve the properties and relationships of conversation object. + * Get a group's conversation object. * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link Conversation} * @throws ODataError When receiving a 4XX or 5XX status code - * @see Find more info here + * @see Find more info here */ @jakarta.annotation.Nullable public Conversation get(@jakarta.annotation.Nullable final java.util.function.Consumer requestConfiguration) { @@ -90,7 +90,7 @@ public Conversation get(@jakarta.annotation.Nullable final java.util.function.Co return this.requestAdapter.send(requestInfo, errorMapping, Conversation::createFromDiscriminatorValue); } /** - * Delete conversation. + * Delete a group's conversation object. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -98,7 +98,7 @@ public RequestInformation toDeleteRequestInformation() { return toDeleteRequestInformation(null); } /** - * Delete conversation. + * Delete a group's conversation object. * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -110,7 +110,7 @@ public RequestInformation toDeleteRequestInformation(@jakarta.annotation.Nullabl return requestInfo; } /** - * Retrieve the properties and relationships of conversation object. + * Get a group's conversation object. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -118,7 +118,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * Retrieve the properties and relationships of conversation object. + * Get a group's conversation object. * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -146,7 +146,7 @@ public ConversationItemRequestBuilder withUrl(@jakarta.annotation.Nonnull final public class DeleteRequestConfiguration extends BaseRequestConfiguration { } /** - * Retrieve the properties and relationships of conversation object. + * Get a group's conversation object. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/groups/item/conversations/item/threads/item/reply/ReplyRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/groups/item/conversations/item/threads/item/reply/ReplyRequestBuilder.java index a0a535579af..53b66403afc 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/groups/item/conversations/item/threads/item/reply/ReplyRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/groups/item/conversations/item/threads/item/reply/ReplyRequestBuilder.java @@ -35,20 +35,20 @@ public ReplyRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @jak super(requestAdapter, "{+baseurl}/groups/{group%2Did}/conversations/{conversation%2Did}/threads/{conversationThread%2Did}/reply", rawUrl); } /** - * 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 * @throws ODataError When receiving a 4XX or 5XX status code - * @see Find more info here + * @see Find more info here */ public void post(@jakarta.annotation.Nonnull final ReplyPostRequestBody body) { post(body, null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @throws ODataError When receiving a 4XX or 5XX status code - * @see Find more info here + * @see Find more info here */ public void post(@jakarta.annotation.Nonnull final ReplyPostRequestBody body, @jakarta.annotation.Nullable final java.util.function.Consumer requestConfiguration) { Objects.requireNonNull(body); @@ -58,7 +58,7 @@ public void post(@jakarta.annotation.Nonnull final ReplyPostRequestBody body, @j this.requestAdapter.sendPrimitive(requestInfo, errorMapping, Void.class); } /** - * 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 * @return a {@link RequestInformation} */ @@ -67,7 +67,7 @@ public RequestInformation toPostRequestInformation(@jakarta.annotation.Nonnull f return toPostRequestInformation(body, null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} diff --git a/src/main/java/com/microsoft/graph/beta/generated/groups/item/events/delta/DeltaRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/groups/item/events/delta/DeltaRequestBuilder.java index a67d5dfee91..b4e9aaaeda4 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/groups/item/events/delta/DeltaRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/groups/item/events/delta/DeltaRequestBuilder.java @@ -36,7 +36,7 @@ public DeltaRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @jak super(requestAdapter, "{+baseurl}/groups/{group%2Did}/events/delta()?endDateTime={endDateTime}&startDateTime={startDateTime}{&%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * 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. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code * @see Find more info here @@ -46,7 +46,7 @@ public DeltaGetResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -60,7 +60,7 @@ public DeltaGetResponse get(@jakarta.annotation.Nullable final java.util.functio return this.requestAdapter.send(requestInfo, errorMapping, DeltaGetResponse::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -68,7 +68,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -90,7 +90,7 @@ public DeltaRequestBuilder withUrl(@jakarta.annotation.Nonnull final String rawU return new DeltaRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/groups/item/events/item/exceptionoccurrences/delta/DeltaRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/groups/item/events/item/exceptionoccurrences/delta/DeltaRequestBuilder.java index 4c205c91c26..afffadebbdd 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/groups/item/events/item/exceptionoccurrences/delta/DeltaRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/groups/item/events/item/exceptionoccurrences/delta/DeltaRequestBuilder.java @@ -36,7 +36,7 @@ public DeltaRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @jak super(requestAdapter, "{+baseurl}/groups/{group%2Did}/events/{event%2Did}/exceptionOccurrences/delta()?endDateTime={endDateTime}&startDateTime={startDateTime}{&%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * 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. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code * @see Find more info here @@ -46,7 +46,7 @@ public DeltaGetResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -60,7 +60,7 @@ public DeltaGetResponse get(@jakarta.annotation.Nullable final java.util.functio return this.requestAdapter.send(requestInfo, errorMapping, DeltaGetResponse::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -68,7 +68,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -90,7 +90,7 @@ public DeltaRequestBuilder withUrl(@jakarta.annotation.Nonnull final String rawU return new DeltaRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/groups/item/events/item/exceptionoccurrences/item/instances/delta/DeltaRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/groups/item/events/item/exceptionoccurrences/item/instances/delta/DeltaRequestBuilder.java index ce274c9a6f7..bf5c0759444 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/groups/item/events/item/exceptionoccurrences/item/instances/delta/DeltaRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/groups/item/events/item/exceptionoccurrences/item/instances/delta/DeltaRequestBuilder.java @@ -36,7 +36,7 @@ public DeltaRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @jak super(requestAdapter, "{+baseurl}/groups/{group%2Did}/events/{event%2Did}/exceptionOccurrences/{event%2Did1}/instances/delta()?endDateTime={endDateTime}&startDateTime={startDateTime}{&%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * 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. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code * @see Find more info here @@ -46,7 +46,7 @@ public DeltaGetResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -60,7 +60,7 @@ public DeltaGetResponse get(@jakarta.annotation.Nullable final java.util.functio return this.requestAdapter.send(requestInfo, errorMapping, DeltaGetResponse::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -68,7 +68,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -90,7 +90,7 @@ public DeltaRequestBuilder withUrl(@jakarta.annotation.Nonnull final String rawU return new DeltaRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/groups/item/events/item/instances/delta/DeltaRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/groups/item/events/item/instances/delta/DeltaRequestBuilder.java index dca34a25693..0e7d8b9c0e5 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/groups/item/events/item/instances/delta/DeltaRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/groups/item/events/item/instances/delta/DeltaRequestBuilder.java @@ -36,7 +36,7 @@ public DeltaRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @jak super(requestAdapter, "{+baseurl}/groups/{group%2Did}/events/{event%2Did}/instances/delta()?endDateTime={endDateTime}&startDateTime={startDateTime}{&%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * 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. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code * @see Find more info here @@ -46,7 +46,7 @@ public DeltaGetResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -60,7 +60,7 @@ public DeltaGetResponse get(@jakarta.annotation.Nullable final java.util.functio return this.requestAdapter.send(requestInfo, errorMapping, DeltaGetResponse::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -68,7 +68,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -90,7 +90,7 @@ public DeltaRequestBuilder withUrl(@jakarta.annotation.Nonnull final String rawU return new DeltaRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/groups/item/events/item/instances/item/exceptionoccurrences/delta/DeltaRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/groups/item/events/item/instances/item/exceptionoccurrences/delta/DeltaRequestBuilder.java index faca21ffcb0..f7c9385cd7e 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/groups/item/events/item/instances/item/exceptionoccurrences/delta/DeltaRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/groups/item/events/item/instances/item/exceptionoccurrences/delta/DeltaRequestBuilder.java @@ -36,7 +36,7 @@ public DeltaRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @jak super(requestAdapter, "{+baseurl}/groups/{group%2Did}/events/{event%2Did}/instances/{event%2Did1}/exceptionOccurrences/delta()?endDateTime={endDateTime}&startDateTime={startDateTime}{&%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * 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. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code * @see Find more info here @@ -46,7 +46,7 @@ public DeltaGetResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -60,7 +60,7 @@ public DeltaGetResponse get(@jakarta.annotation.Nullable final java.util.functio return this.requestAdapter.send(requestInfo, errorMapping, DeltaGetResponse::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -68,7 +68,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -90,7 +90,7 @@ public DeltaRequestBuilder withUrl(@jakarta.annotation.Nonnull final String rawU return new DeltaRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/groups/item/onenote/notebooks/NotebooksRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/groups/item/onenote/notebooks/NotebooksRequestBuilder.java index 96665e3238b..b7b89c34fdf 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/groups/item/onenote/notebooks/NotebooksRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/groups/item/onenote/notebooks/NotebooksRequestBuilder.java @@ -70,7 +70,7 @@ public NotebooksRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, super(requestAdapter, "{+baseurl}/groups/{group%2Did}/onenote/notebooks{?%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * 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. * @return a {@link NotebookCollectionResponse} * @throws ODataError When receiving a 4XX or 5XX status code */ @@ -79,7 +79,7 @@ public NotebookCollectionResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link NotebookCollectionResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -127,7 +127,7 @@ public Notebook post(@jakarta.annotation.Nonnull final Notebook body, @jakarta.a return this.requestAdapter.send(requestInfo, errorMapping, Notebook::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -135,7 +135,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -181,7 +181,7 @@ public NotebooksRequestBuilder withUrl(@jakarta.annotation.Nonnull final String return new NotebooksRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/groups/item/onenote/notebooks/item/NotebookItemRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/groups/item/onenote/notebooks/item/NotebookItemRequestBuilder.java index 23cab9cd7a2..bf7d4b9ab74 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/groups/item/onenote/notebooks/item/NotebookItemRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/groups/item/onenote/notebooks/item/NotebookItemRequestBuilder.java @@ -82,7 +82,7 @@ public void delete(@jakarta.annotation.Nullable final java.util.function.Consume this.requestAdapter.sendPrimitive(requestInfo, errorMapping, Void.class); } /** - * 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. * @return a {@link Notebook} * @throws ODataError When receiving a 4XX or 5XX status code */ @@ -91,7 +91,7 @@ public Notebook get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link Notebook} * @throws ODataError When receiving a 4XX or 5XX status code @@ -149,7 +149,7 @@ public RequestInformation toDeleteRequestInformation(@jakarta.annotation.Nullabl return requestInfo; } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -157,7 +157,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -209,7 +209,7 @@ public NotebookItemRequestBuilder withUrl(@jakarta.annotation.Nonnull final Stri public class DeleteRequestConfiguration extends BaseRequestConfiguration { } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/groups/item/onenote/pages/PagesRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/groups/item/onenote/pages/PagesRequestBuilder.java index af044476a8a..89024aec033 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/groups/item/onenote/pages/PagesRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/groups/item/onenote/pages/PagesRequestBuilder.java @@ -60,7 +60,7 @@ public PagesRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @jak super(requestAdapter, "{+baseurl}/groups/{group%2Did}/onenote/pages{?%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * 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. * @return a {@link OnenotePageCollectionResponse} * @throws ODataError When receiving a 4XX or 5XX status code */ @@ -69,7 +69,7 @@ public OnenotePageCollectionResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link OnenotePageCollectionResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -107,7 +107,7 @@ public OnenotePage post(@jakarta.annotation.Nonnull final OnenotePage body, @jak return this.requestAdapter.send(requestInfo, errorMapping, OnenotePage::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -115,7 +115,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -161,7 +161,7 @@ public PagesRequestBuilder withUrl(@jakarta.annotation.Nonnull final String rawU return new PagesRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/groups/item/onenote/pages/item/OnenotePageItemRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/groups/item/onenote/pages/item/OnenotePageItemRequestBuilder.java index 41042c437f4..8046aa1e0ee 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/groups/item/onenote/pages/item/OnenotePageItemRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/groups/item/onenote/pages/item/OnenotePageItemRequestBuilder.java @@ -109,7 +109,7 @@ public void delete(@jakarta.annotation.Nullable final java.util.function.Consume this.requestAdapter.sendPrimitive(requestInfo, errorMapping, Void.class); } /** - * 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. * @return a {@link OnenotePage} * @throws ODataError When receiving a 4XX or 5XX status code */ @@ -118,7 +118,7 @@ public OnenotePage get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link OnenotePage} * @throws ODataError When receiving a 4XX or 5XX status code @@ -176,7 +176,7 @@ public RequestInformation toDeleteRequestInformation(@jakarta.annotation.Nullabl return requestInfo; } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -184,7 +184,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -236,7 +236,7 @@ public OnenotePageItemRequestBuilder withUrl(@jakarta.annotation.Nonnull final S public class DeleteRequestConfiguration extends BaseRequestConfiguration { } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/groups/item/onenote/sectiongroups/SectionGroupsRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/groups/item/onenote/sectiongroups/SectionGroupsRequestBuilder.java index 5a37ab754ed..641f0455616 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/groups/item/onenote/sectiongroups/SectionGroupsRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/groups/item/onenote/sectiongroups/SectionGroupsRequestBuilder.java @@ -60,7 +60,7 @@ public SectionGroupsRequestBuilder(@jakarta.annotation.Nonnull final String rawU super(requestAdapter, "{+baseurl}/groups/{group%2Did}/onenote/sectionGroups{?%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * 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. * @return a {@link SectionGroupCollectionResponse} * @throws ODataError When receiving a 4XX or 5XX status code */ @@ -69,7 +69,7 @@ public SectionGroupCollectionResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link SectionGroupCollectionResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -107,7 +107,7 @@ public SectionGroup post(@jakarta.annotation.Nonnull final SectionGroup body, @j return this.requestAdapter.send(requestInfo, errorMapping, SectionGroup::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -115,7 +115,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -161,7 +161,7 @@ public SectionGroupsRequestBuilder withUrl(@jakarta.annotation.Nonnull final Str return new SectionGroupsRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/groups/item/onenote/sectiongroups/item/SectionGroupItemRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/groups/item/onenote/sectiongroups/item/SectionGroupItemRequestBuilder.java index 4ce4978736c..b200e824a09 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/groups/item/onenote/sectiongroups/item/SectionGroupItemRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/groups/item/onenote/sectiongroups/item/SectionGroupItemRequestBuilder.java @@ -91,7 +91,7 @@ public void delete(@jakarta.annotation.Nullable final java.util.function.Consume this.requestAdapter.sendPrimitive(requestInfo, errorMapping, Void.class); } /** - * 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. * @return a {@link SectionGroup} * @throws ODataError When receiving a 4XX or 5XX status code */ @@ -100,7 +100,7 @@ public SectionGroup get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link SectionGroup} * @throws ODataError When receiving a 4XX or 5XX status code @@ -158,7 +158,7 @@ public RequestInformation toDeleteRequestInformation(@jakarta.annotation.Nullabl return requestInfo; } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -166,7 +166,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -218,7 +218,7 @@ public SectionGroupItemRequestBuilder withUrl(@jakarta.annotation.Nonnull final public class DeleteRequestConfiguration extends BaseRequestConfiguration { } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/groups/item/onenote/sections/SectionsRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/groups/item/onenote/sections/SectionsRequestBuilder.java index 6f114be381a..7e95882d08a 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/groups/item/onenote/sections/SectionsRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/groups/item/onenote/sections/SectionsRequestBuilder.java @@ -60,7 +60,7 @@ public SectionsRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @ super(requestAdapter, "{+baseurl}/groups/{group%2Did}/onenote/sections{?%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * 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. * @return a {@link OnenoteSectionCollectionResponse} * @throws ODataError When receiving a 4XX or 5XX status code */ @@ -69,7 +69,7 @@ public OnenoteSectionCollectionResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link OnenoteSectionCollectionResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -107,7 +107,7 @@ public OnenoteSection post(@jakarta.annotation.Nonnull final OnenoteSection body return this.requestAdapter.send(requestInfo, errorMapping, OnenoteSection::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -115,7 +115,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -161,7 +161,7 @@ public SectionsRequestBuilder withUrl(@jakarta.annotation.Nonnull final String r return new SectionsRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/groups/item/onenote/sections/item/OnenoteSectionItemRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/groups/item/onenote/sections/item/OnenoteSectionItemRequestBuilder.java index 5e140fbf384..94878d10bb1 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/groups/item/onenote/sections/item/OnenoteSectionItemRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/groups/item/onenote/sections/item/OnenoteSectionItemRequestBuilder.java @@ -100,7 +100,7 @@ public void delete(@jakarta.annotation.Nullable final java.util.function.Consume this.requestAdapter.sendPrimitive(requestInfo, errorMapping, Void.class); } /** - * 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. * @return a {@link OnenoteSection} * @throws ODataError When receiving a 4XX or 5XX status code */ @@ -109,7 +109,7 @@ public OnenoteSection get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link OnenoteSection} * @throws ODataError When receiving a 4XX or 5XX status code @@ -167,7 +167,7 @@ public RequestInformation toDeleteRequestInformation(@jakarta.annotation.Nullabl return requestInfo; } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -175,7 +175,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -227,7 +227,7 @@ public OnenoteSectionItemRequestBuilder withUrl(@jakarta.annotation.Nonnull fina public class DeleteRequestConfiguration extends BaseRequestConfiguration { } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/groups/item/sites/item/onenote/notebooks/NotebooksRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/groups/item/sites/item/onenote/notebooks/NotebooksRequestBuilder.java index 65c2cc6cb44..d973591ed8c 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/groups/item/sites/item/onenote/notebooks/NotebooksRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/groups/item/sites/item/onenote/notebooks/NotebooksRequestBuilder.java @@ -70,7 +70,7 @@ public NotebooksRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, super(requestAdapter, "{+baseurl}/groups/{group%2Did}/sites/{site%2Did}/onenote/notebooks{?%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * 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. * @return a {@link NotebookCollectionResponse} * @throws ODataError When receiving a 4XX or 5XX status code */ @@ -79,7 +79,7 @@ public NotebookCollectionResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link NotebookCollectionResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -127,7 +127,7 @@ public Notebook post(@jakarta.annotation.Nonnull final Notebook body, @jakarta.a return this.requestAdapter.send(requestInfo, errorMapping, Notebook::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -135,7 +135,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -181,7 +181,7 @@ public NotebooksRequestBuilder withUrl(@jakarta.annotation.Nonnull final String return new NotebooksRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/groups/item/sites/item/onenote/notebooks/item/NotebookItemRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/groups/item/sites/item/onenote/notebooks/item/NotebookItemRequestBuilder.java index eaad5efd930..bec7036834d 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/groups/item/sites/item/onenote/notebooks/item/NotebookItemRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/groups/item/sites/item/onenote/notebooks/item/NotebookItemRequestBuilder.java @@ -82,7 +82,7 @@ public void delete(@jakarta.annotation.Nullable final java.util.function.Consume this.requestAdapter.sendPrimitive(requestInfo, errorMapping, Void.class); } /** - * 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. * @return a {@link Notebook} * @throws ODataError When receiving a 4XX or 5XX status code */ @@ -91,7 +91,7 @@ public Notebook get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link Notebook} * @throws ODataError When receiving a 4XX or 5XX status code @@ -149,7 +149,7 @@ public RequestInformation toDeleteRequestInformation(@jakarta.annotation.Nullabl return requestInfo; } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -157,7 +157,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -209,7 +209,7 @@ public NotebookItemRequestBuilder withUrl(@jakarta.annotation.Nonnull final Stri public class DeleteRequestConfiguration extends BaseRequestConfiguration { } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/groups/item/sites/item/onenote/pages/PagesRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/groups/item/sites/item/onenote/pages/PagesRequestBuilder.java index fead457c822..a620fb73ba6 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/groups/item/sites/item/onenote/pages/PagesRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/groups/item/sites/item/onenote/pages/PagesRequestBuilder.java @@ -60,7 +60,7 @@ public PagesRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @jak super(requestAdapter, "{+baseurl}/groups/{group%2Did}/sites/{site%2Did}/onenote/pages{?%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * 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. * @return a {@link OnenotePageCollectionResponse} * @throws ODataError When receiving a 4XX or 5XX status code */ @@ -69,7 +69,7 @@ public OnenotePageCollectionResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link OnenotePageCollectionResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -107,7 +107,7 @@ public OnenotePage post(@jakarta.annotation.Nonnull final OnenotePage body, @jak return this.requestAdapter.send(requestInfo, errorMapping, OnenotePage::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -115,7 +115,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -161,7 +161,7 @@ public PagesRequestBuilder withUrl(@jakarta.annotation.Nonnull final String rawU return new PagesRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/groups/item/sites/item/onenote/pages/item/OnenotePageItemRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/groups/item/sites/item/onenote/pages/item/OnenotePageItemRequestBuilder.java index 72fcafa7f59..16a2e1adb30 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/groups/item/sites/item/onenote/pages/item/OnenotePageItemRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/groups/item/sites/item/onenote/pages/item/OnenotePageItemRequestBuilder.java @@ -109,7 +109,7 @@ public void delete(@jakarta.annotation.Nullable final java.util.function.Consume this.requestAdapter.sendPrimitive(requestInfo, errorMapping, Void.class); } /** - * 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. * @return a {@link OnenotePage} * @throws ODataError When receiving a 4XX or 5XX status code */ @@ -118,7 +118,7 @@ public OnenotePage get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link OnenotePage} * @throws ODataError When receiving a 4XX or 5XX status code @@ -176,7 +176,7 @@ public RequestInformation toDeleteRequestInformation(@jakarta.annotation.Nullabl return requestInfo; } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -184,7 +184,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -236,7 +236,7 @@ public OnenotePageItemRequestBuilder withUrl(@jakarta.annotation.Nonnull final S public class DeleteRequestConfiguration extends BaseRequestConfiguration { } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/groups/item/sites/item/onenote/sectiongroups/SectionGroupsRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/groups/item/sites/item/onenote/sectiongroups/SectionGroupsRequestBuilder.java index cfd082a919d..e1d9b1fc611 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/groups/item/sites/item/onenote/sectiongroups/SectionGroupsRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/groups/item/sites/item/onenote/sectiongroups/SectionGroupsRequestBuilder.java @@ -60,7 +60,7 @@ public SectionGroupsRequestBuilder(@jakarta.annotation.Nonnull final String rawU super(requestAdapter, "{+baseurl}/groups/{group%2Did}/sites/{site%2Did}/onenote/sectionGroups{?%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * 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. * @return a {@link SectionGroupCollectionResponse} * @throws ODataError When receiving a 4XX or 5XX status code */ @@ -69,7 +69,7 @@ public SectionGroupCollectionResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link SectionGroupCollectionResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -107,7 +107,7 @@ public SectionGroup post(@jakarta.annotation.Nonnull final SectionGroup body, @j return this.requestAdapter.send(requestInfo, errorMapping, SectionGroup::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -115,7 +115,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -161,7 +161,7 @@ public SectionGroupsRequestBuilder withUrl(@jakarta.annotation.Nonnull final Str return new SectionGroupsRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/groups/item/sites/item/onenote/sectiongroups/item/SectionGroupItemRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/groups/item/sites/item/onenote/sectiongroups/item/SectionGroupItemRequestBuilder.java index 6387a58bd6f..df393922f0a 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/groups/item/sites/item/onenote/sectiongroups/item/SectionGroupItemRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/groups/item/sites/item/onenote/sectiongroups/item/SectionGroupItemRequestBuilder.java @@ -91,7 +91,7 @@ public void delete(@jakarta.annotation.Nullable final java.util.function.Consume this.requestAdapter.sendPrimitive(requestInfo, errorMapping, Void.class); } /** - * 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. * @return a {@link SectionGroup} * @throws ODataError When receiving a 4XX or 5XX status code */ @@ -100,7 +100,7 @@ public SectionGroup get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link SectionGroup} * @throws ODataError When receiving a 4XX or 5XX status code @@ -158,7 +158,7 @@ public RequestInformation toDeleteRequestInformation(@jakarta.annotation.Nullabl return requestInfo; } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -166,7 +166,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -218,7 +218,7 @@ public SectionGroupItemRequestBuilder withUrl(@jakarta.annotation.Nonnull final public class DeleteRequestConfiguration extends BaseRequestConfiguration { } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/groups/item/sites/item/onenote/sections/SectionsRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/groups/item/sites/item/onenote/sections/SectionsRequestBuilder.java index 1059b4f61cc..db5fe0c2286 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/groups/item/sites/item/onenote/sections/SectionsRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/groups/item/sites/item/onenote/sections/SectionsRequestBuilder.java @@ -60,7 +60,7 @@ public SectionsRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @ super(requestAdapter, "{+baseurl}/groups/{group%2Did}/sites/{site%2Did}/onenote/sections{?%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * 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. * @return a {@link OnenoteSectionCollectionResponse} * @throws ODataError When receiving a 4XX or 5XX status code */ @@ -69,7 +69,7 @@ public OnenoteSectionCollectionResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link OnenoteSectionCollectionResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -107,7 +107,7 @@ public OnenoteSection post(@jakarta.annotation.Nonnull final OnenoteSection body return this.requestAdapter.send(requestInfo, errorMapping, OnenoteSection::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -115,7 +115,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -161,7 +161,7 @@ public SectionsRequestBuilder withUrl(@jakarta.annotation.Nonnull final String r return new SectionsRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/groups/item/sites/item/onenote/sections/item/OnenoteSectionItemRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/groups/item/sites/item/onenote/sections/item/OnenoteSectionItemRequestBuilder.java index b3b98e9d440..a1a6932e2a6 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/groups/item/sites/item/onenote/sections/item/OnenoteSectionItemRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/groups/item/sites/item/onenote/sections/item/OnenoteSectionItemRequestBuilder.java @@ -100,7 +100,7 @@ public void delete(@jakarta.annotation.Nullable final java.util.function.Consume this.requestAdapter.sendPrimitive(requestInfo, errorMapping, Void.class); } /** - * 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. * @return a {@link OnenoteSection} * @throws ODataError When receiving a 4XX or 5XX status code */ @@ -109,7 +109,7 @@ public OnenoteSection get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link OnenoteSection} * @throws ODataError When receiving a 4XX or 5XX status code @@ -167,7 +167,7 @@ public RequestInformation toDeleteRequestInformation(@jakarta.annotation.Nullabl return requestInfo; } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -175,7 +175,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -227,7 +227,7 @@ public OnenoteSectionItemRequestBuilder withUrl(@jakarta.annotation.Nonnull fina public class DeleteRequestConfiguration extends BaseRequestConfiguration { } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/groups/item/threads/item/reply/ReplyRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/groups/item/threads/item/reply/ReplyRequestBuilder.java index 87c1e46161c..5b3a74e21b3 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/groups/item/threads/item/reply/ReplyRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/groups/item/threads/item/reply/ReplyRequestBuilder.java @@ -35,20 +35,20 @@ public ReplyRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @jak super(requestAdapter, "{+baseurl}/groups/{group%2Did}/threads/{conversationThread%2Did}/reply", rawUrl); } /** - * 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 * @throws ODataError When receiving a 4XX or 5XX status code - * @see Find more info here + * @see Find more info here */ public void post(@jakarta.annotation.Nonnull final ReplyPostRequestBody body) { post(body, null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @throws ODataError When receiving a 4XX or 5XX status code - * @see Find more info here + * @see Find more info here */ public void post(@jakarta.annotation.Nonnull final ReplyPostRequestBody body, @jakarta.annotation.Nullable final java.util.function.Consumer requestConfiguration) { Objects.requireNonNull(body); @@ -58,7 +58,7 @@ public void post(@jakarta.annotation.Nonnull final ReplyPostRequestBody body, @j this.requestAdapter.sendPrimitive(requestInfo, errorMapping, Void.class); } /** - * 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 * @return a {@link RequestInformation} */ @@ -67,7 +67,7 @@ public RequestInformation toPostRequestInformation(@jakarta.annotation.Nonnull f return toPostRequestInformation(body, null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} diff --git a/src/main/java/com/microsoft/graph/beta/generated/identity/conditionalaccess/namedlocations/item/NamedLocationItemRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/identity/conditionalaccess/namedlocations/item/NamedLocationItemRequestBuilder.java index 276a7571e05..79d707ddcfa 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/identity/conditionalaccess/namedlocations/item/NamedLocationItemRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/identity/conditionalaccess/namedlocations/item/NamedLocationItemRequestBuilder.java @@ -81,23 +81,23 @@ public NamedLocation get(@jakarta.annotation.Nullable final java.util.function.C return this.requestAdapter.send(requestInfo, errorMapping, NamedLocation::createFromDiscriminatorValue); } /** - * Update the properties of a countryNamedLocation object. + * Update the properties of an ipNamedLocation object. * @param body The request body * @return a {@link NamedLocation} * @throws ODataError When receiving a 4XX or 5XX status code - * @see Find more info here + * @see Find more info here */ @jakarta.annotation.Nullable public NamedLocation patch(@jakarta.annotation.Nonnull final NamedLocation body) { return patch(body, null); } /** - * Update the properties of a countryNamedLocation object. + * Update the properties of an ipNamedLocation object. * @param body The request body * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link NamedLocation} * @throws ODataError When receiving a 4XX or 5XX status code - * @see Find more info here + * @see Find more info here */ @jakarta.annotation.Nullable public NamedLocation patch(@jakarta.annotation.Nonnull final NamedLocation body, @jakarta.annotation.Nullable final java.util.function.Consumer requestConfiguration) { @@ -148,7 +148,7 @@ public RequestInformation toGetRequestInformation(@jakarta.annotation.Nullable f return requestInfo; } /** - * Update the properties of a countryNamedLocation object. + * Update the properties of an ipNamedLocation object. * @param body The request body * @return a {@link RequestInformation} */ @@ -157,7 +157,7 @@ public RequestInformation toPatchRequestInformation(@jakarta.annotation.Nonnull return toPatchRequestInformation(body, null); } /** - * Update the properties of a countryNamedLocation object. + * Update the properties of an ipNamedLocation object. * @param body The request body * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} diff --git a/src/main/java/com/microsoft/graph/beta/generated/identitygovernance/entitlementmanagement/accesspackagecatalogs/item/accesspackagecustomworkflowextensions/item/CustomCalloutExtensionItemRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/identitygovernance/entitlementmanagement/accesspackagecatalogs/item/accesspackagecustomworkflowextensions/item/CustomCalloutExtensionItemRequestBuilder.java index 2cd0acf0558..8ee861354e1 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/identitygovernance/entitlementmanagement/accesspackagecatalogs/item/accesspackagecustomworkflowextensions/item/CustomCalloutExtensionItemRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/identitygovernance/entitlementmanagement/accesspackagecatalogs/item/accesspackagecustomworkflowextensions/item/CustomCalloutExtensionItemRequestBuilder.java @@ -61,12 +61,12 @@ public void delete(@jakarta.annotation.Nullable final java.util.function.Consume this.requestAdapter.sendPrimitive(requestInfo, errorMapping, Void.class); } /** - * Read the properties and relationships of an accessPackageAssignmentWorkflowExtension object. + * Read the properties and relationships of an accessPackageAssignmentRequestWorkflowExtension object. * @return a {@link CustomCalloutExtension} * @throws ODataError When receiving a 4XX or 5XX status code * @deprecated * as of 2022-10/PrivatePreview:MicrosofEntitlementManagementCustomextensions - * @see Find more info here + * @see Find more info here */ @jakarta.annotation.Nullable @Deprecated @@ -74,13 +74,13 @@ public CustomCalloutExtension get() { return get(null); } /** - * Read the properties and relationships of an accessPackageAssignmentWorkflowExtension object. + * Read the properties and relationships of an accessPackageAssignmentRequestWorkflowExtension object. * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link CustomCalloutExtension} * @throws ODataError When receiving a 4XX or 5XX status code * @deprecated * as of 2022-10/PrivatePreview:MicrosofEntitlementManagementCustomextensions - * @see Find more info here + * @see Find more info here */ @jakarta.annotation.Nullable @Deprecated @@ -150,7 +150,7 @@ public RequestInformation toDeleteRequestInformation(@jakarta.annotation.Nullabl return requestInfo; } /** - * Read the properties and relationships of an accessPackageAssignmentWorkflowExtension object. + * Read the properties and relationships of an accessPackageAssignmentRequestWorkflowExtension object. * @return a {@link RequestInformation} * @deprecated * as of 2022-10/PrivatePreview:MicrosofEntitlementManagementCustomextensions @@ -161,7 +161,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * Read the properties and relationships of an accessPackageAssignmentWorkflowExtension object. + * Read the properties and relationships of an accessPackageAssignmentRequestWorkflowExtension object. * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} * @deprecated @@ -225,7 +225,7 @@ public CustomCalloutExtensionItemRequestBuilder withUrl(@jakarta.annotation.Nonn public class DeleteRequestConfiguration extends BaseRequestConfiguration { } /** - * Read the properties and relationships of an accessPackageAssignmentWorkflowExtension object. + * Read the properties and relationships of an accessPackageAssignmentRequestWorkflowExtension object. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/identitygovernance/entitlementmanagement/accesspackagecatalogs/item/customaccesspackageworkflowextensions/item/CustomAccessPackageWorkflowExtensionItemRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/identitygovernance/entitlementmanagement/accesspackagecatalogs/item/customaccesspackageworkflowextensions/item/CustomAccessPackageWorkflowExtensionItemRequestBuilder.java index 6b59fa3ccc1..05de789ee29 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/identitygovernance/entitlementmanagement/accesspackagecatalogs/item/customaccesspackageworkflowextensions/item/CustomAccessPackageWorkflowExtensionItemRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/identitygovernance/entitlementmanagement/accesspackagecatalogs/item/customaccesspackageworkflowextensions/item/CustomAccessPackageWorkflowExtensionItemRequestBuilder.java @@ -37,23 +37,23 @@ public CustomAccessPackageWorkflowExtensionItemRequestBuilder(@jakarta.annotatio super(requestAdapter, "{+baseurl}/identityGovernance/entitlementManagement/accessPackageCatalogs/{accessPackageCatalog%2Did}/customAccessPackageWorkflowExtensions/{customAccessPackageWorkflowExtension%2Did}{?%24expand,%24select}", rawUrl); } /** - * 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. * @throws ODataError When receiving a 4XX or 5XX status code * @deprecated * as of 2022-10/PrivatePreview:MicrosofEntitlementManagementCustomextensions - * @see Find more info here + * @see Find more info here */ @Deprecated public void delete() { delete(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @throws ODataError When receiving a 4XX or 5XX status code * @deprecated * as of 2022-10/PrivatePreview:MicrosofEntitlementManagementCustomextensions - * @see Find more info here + * @see Find more info here */ @Deprecated public void delete(@jakarta.annotation.Nullable final java.util.function.Consumer requestConfiguration) { @@ -126,7 +126,7 @@ public CustomAccessPackageWorkflowExtension patch(@jakarta.annotation.Nonnull fi return this.requestAdapter.send(requestInfo, errorMapping, CustomAccessPackageWorkflowExtension::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} * @deprecated * as of 2022-10/PrivatePreview:MicrosofEntitlementManagementCustomextensions @@ -137,7 +137,7 @@ public RequestInformation toDeleteRequestInformation() { return toDeleteRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} * @deprecated diff --git a/src/main/java/com/microsoft/graph/beta/generated/identitygovernance/entitlementmanagement/accesspackages/item/AccessPackageItemRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/identitygovernance/entitlementmanagement/accesspackages/item/AccessPackageItemRequestBuilder.java index da1af3d0790..9f344f53507 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/identitygovernance/entitlementmanagement/accesspackages/item/AccessPackageItemRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/identitygovernance/entitlementmanagement/accesspackages/item/AccessPackageItemRequestBuilder.java @@ -140,21 +140,21 @@ public void delete(@jakarta.annotation.Nullable final java.util.function.Consume this.requestAdapter.sendPrimitive(requestInfo, errorMapping, Void.class); } /** - * 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. * @return a {@link AccessPackage} * @throws ODataError When receiving a 4XX or 5XX status code - * @see Find more info here + * @see Find more info here */ @jakarta.annotation.Nullable public AccessPackage get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link AccessPackage} * @throws ODataError When receiving a 4XX or 5XX status code - * @see Find more info here + * @see Find more info here */ @jakarta.annotation.Nullable public AccessPackage get(@jakarta.annotation.Nullable final java.util.function.Consumer requestConfiguration) { @@ -211,7 +211,7 @@ public RequestInformation toDeleteRequestInformation(@jakarta.annotation.Nullabl return requestInfo; } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -219,7 +219,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -271,7 +271,7 @@ public AccessPackageItemRequestBuilder withUrl(@jakarta.annotation.Nonnull final public class DeleteRequestConfiguration extends BaseRequestConfiguration { } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/identitygovernance/entitlementmanagement/accesspackageswithuniquename/AccessPackagesWithUniqueNameRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/identitygovernance/entitlementmanagement/accesspackageswithuniquename/AccessPackagesWithUniqueNameRequestBuilder.java index 897fa96024e..1cef5cd718b 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/identitygovernance/entitlementmanagement/accesspackageswithuniquename/AccessPackagesWithUniqueNameRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/identitygovernance/entitlementmanagement/accesspackageswithuniquename/AccessPackagesWithUniqueNameRequestBuilder.java @@ -77,21 +77,21 @@ public void delete(@jakarta.annotation.Nullable final java.util.function.Consume this.requestAdapter.sendPrimitive(requestInfo, errorMapping, Void.class); } /** - * 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. * @return a {@link AccessPackage} * @throws ODataError When receiving a 4XX or 5XX status code - * @see Find more info here + * @see Find more info here */ @jakarta.annotation.Nullable public AccessPackage get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link AccessPackage} * @throws ODataError When receiving a 4XX or 5XX status code - * @see Find more info here + * @see Find more info here */ @jakarta.annotation.Nullable public AccessPackage get(@jakarta.annotation.Nullable final java.util.function.Consumer requestConfiguration) { @@ -148,7 +148,7 @@ public RequestInformation toDeleteRequestInformation(@jakarta.annotation.Nullabl return requestInfo; } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -156,7 +156,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -208,7 +208,7 @@ public AccessPackagesWithUniqueNameRequestBuilder withUrl(@jakarta.annotation.No public class DeleteRequestConfiguration extends BaseRequestConfiguration { } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/identitygovernance/termsofuse/agreements/item/AgreementItemRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/identitygovernance/termsofuse/agreements/item/AgreementItemRequestBuilder.java index 306bf0cb964..0b9698d6fab 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/identitygovernance/termsofuse/agreements/item/AgreementItemRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/identitygovernance/termsofuse/agreements/item/AgreementItemRequestBuilder.java @@ -84,21 +84,21 @@ public void delete(@jakarta.annotation.Nullable final java.util.function.Consume this.requestAdapter.sendPrimitive(requestInfo, errorMapping, Void.class); } /** - * 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. * @return a {@link Agreement} * @throws ODataError When receiving a 4XX or 5XX status code - * @see Find more info here + * @see Find more info here */ @jakarta.annotation.Nullable public Agreement get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link Agreement} * @throws ODataError When receiving a 4XX or 5XX status code - * @see Find more info here + * @see Find more info here */ @jakarta.annotation.Nullable public Agreement get(@jakarta.annotation.Nullable final java.util.function.Consumer requestConfiguration) { @@ -155,7 +155,7 @@ public RequestInformation toDeleteRequestInformation(@jakarta.annotation.Nullabl return requestInfo; } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -163,7 +163,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -215,7 +215,7 @@ public AgreementItemRequestBuilder withUrl(@jakarta.annotation.Nonnull final Str public class DeleteRequestConfiguration extends BaseRequestConfiguration { } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/identityprotection/riskdetections/item/RiskDetectionItemRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/identityprotection/riskdetections/item/RiskDetectionItemRequestBuilder.java index 8b665bac99f..68dc31ca98a 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/identityprotection/riskdetections/item/RiskDetectionItemRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/identityprotection/riskdetections/item/RiskDetectionItemRequestBuilder.java @@ -55,21 +55,21 @@ public void delete(@jakarta.annotation.Nullable final java.util.function.Consume this.requestAdapter.sendPrimitive(requestInfo, errorMapping, Void.class); } /** - * Retrieve the properties of a riskDetection object. + * Retrieve the properties of a collection of riskDetection objects. * @return a {@link RiskDetection} * @throws ODataError When receiving a 4XX or 5XX status code - * @see Find more info here + * @see Find more info here */ @jakarta.annotation.Nullable public RiskDetection get() { return get(null); } /** - * Retrieve the properties of a riskDetection object. + * Retrieve the properties of a collection of riskDetection objects. * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RiskDetection} * @throws ODataError When receiving a 4XX or 5XX status code - * @see Find more info here + * @see Find more info here */ @jakarta.annotation.Nullable public RiskDetection get(@jakarta.annotation.Nullable final java.util.function.Consumer requestConfiguration) { @@ -124,7 +124,7 @@ public RequestInformation toDeleteRequestInformation(@jakarta.annotation.Nullabl return requestInfo; } /** - * Retrieve the properties of a riskDetection object. + * Retrieve the properties of a collection of riskDetection objects. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -132,7 +132,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * Retrieve the properties of a riskDetection object. + * Retrieve the properties of a collection of riskDetection objects. * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -184,7 +184,7 @@ public RiskDetectionItemRequestBuilder withUrl(@jakarta.annotation.Nonnull final public class DeleteRequestConfiguration extends BaseRequestConfiguration { } /** - * Retrieve the properties of a riskDetection object. + * Retrieve the properties of a collection of riskDetection objects. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/kiota-lock.json b/src/main/java/com/microsoft/graph/beta/generated/kiota-lock.json index ce72c25cb09..f3580576db2 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/kiota-lock.json +++ b/src/main/java/com/microsoft/graph/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": "com.Microsoft.Graph.Beta", diff --git a/src/main/java/com/microsoft/graph/beta/generated/models/AndroidManagedAppProtection.java b/src/main/java/com/microsoft/graph/beta/generated/models/AndroidManagedAppProtection.java index 846df11760d..37fe49a5567 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/models/AndroidManagedAppProtection.java +++ b/src/main/java/com/microsoft/graph/beta/generated/models/AndroidManagedAppProtection.java @@ -165,7 +165,7 @@ public Boolean getConnectToVpnOnLaunch() { return this.backingStore.get("connectToVpnOnLaunch"); } /** - * Gets the customBrowserDisplayName property value. Friendly name of the preferred custom browser to open weblink on Android. + * Gets the customBrowserDisplayName property value. Friendly name of the preferred custom browser to open weblink on Android. When this property is configured, ManagedBrowserToOpenLinksRequired should be true. * @return a {@link String} */ @jakarta.annotation.Nullable @@ -173,7 +173,7 @@ public String getCustomBrowserDisplayName() { return this.backingStore.get("customBrowserDisplayName"); } /** - * Gets the customBrowserPackageId property value. Unique identifier of a custom browser to open weblink on Android. + * Gets the customBrowserPackageId property value. Unique identifier of the preferred custom browser to open weblink on Android. When this property is configured, ManagedBrowserToOpenLinksRequired should be true. * @return a {@link String} */ @jakarta.annotation.Nullable @@ -615,14 +615,14 @@ public void setConnectToVpnOnLaunch(@jakarta.annotation.Nullable final Boolean v this.backingStore.set("connectToVpnOnLaunch", value); } /** - * Sets the customBrowserDisplayName property value. Friendly name of the preferred custom browser to open weblink on Android. + * Sets the customBrowserDisplayName property value. Friendly name of the preferred custom browser to open weblink on Android. When this property is configured, ManagedBrowserToOpenLinksRequired should be true. * @param value Value to set for the customBrowserDisplayName property. */ public void setCustomBrowserDisplayName(@jakarta.annotation.Nullable final String value) { this.backingStore.set("customBrowserDisplayName", value); } /** - * Sets the customBrowserPackageId property value. Unique identifier of a custom browser to open weblink on Android. + * Sets the customBrowserPackageId property value. Unique identifier of the preferred custom browser to open weblink on Android. When this property is configured, ManagedBrowserToOpenLinksRequired should be true. * @param value Value to set for the customBrowserPackageId property. */ public void setCustomBrowserPackageId(@jakarta.annotation.Nullable final String value) { diff --git a/src/main/java/com/microsoft/graph/beta/generated/models/Authentication.java b/src/main/java/com/microsoft/graph/beta/generated/models/Authentication.java index 6f041ab2ca9..0fbafa7aeab 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/models/Authentication.java +++ b/src/main/java/com/microsoft/graph/beta/generated/models/Authentication.java @@ -65,7 +65,7 @@ public Map> getFieldDeserializers return deserializerMap; } /** - * Gets the hardwareOathMethods property value. The hardwareOathMethods property + * Gets the hardwareOathMethods property value. The hardware OATH time-based one-time password (TOTP) devices assigned to a user for authentication. * @return a {@link java.util.List} */ @jakarta.annotation.Nullable @@ -206,7 +206,7 @@ public void setFido2Methods(@jakarta.annotation.Nullable final java.util.List value) { diff --git a/src/main/java/com/microsoft/graph/beta/generated/models/AuthenticationMethodDevice.java b/src/main/java/com/microsoft/graph/beta/generated/models/AuthenticationMethodDevice.java index bfbb4490b11..c651967f5b9 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/models/AuthenticationMethodDevice.java +++ b/src/main/java/com/microsoft/graph/beta/generated/models/AuthenticationMethodDevice.java @@ -32,7 +32,7 @@ public static AuthenticationMethodDevice createFromDiscriminatorValue(@jakarta.a return new AuthenticationMethodDevice(); } /** - * Gets the displayName property value. The displayName property + * Gets the displayName property value. Optional name given to the hardware OATH device. * @return a {@link String} */ @jakarta.annotation.Nullable @@ -51,7 +51,7 @@ public Map> getFieldDeserializers return deserializerMap; } /** - * Gets the hardwareOathDevices property value. The hardwareOathDevices property + * Gets the hardwareOathDevices property value. Exposes the hardware OATH method in the directory. * @return a {@link java.util.List} */ @jakarta.annotation.Nullable @@ -69,14 +69,14 @@ public void serialize(@jakarta.annotation.Nonnull final SerializationWriter writ writer.writeCollectionOfObjectValues("hardwareOathDevices", this.getHardwareOathDevices()); } /** - * Sets the displayName property value. The displayName property + * Sets the displayName property value. Optional name given to the hardware OATH device. * @param value Value to set for the displayName property. */ public void setDisplayName(@jakarta.annotation.Nullable final String value) { this.backingStore.set("displayName", value); } /** - * Sets the hardwareOathDevices property value. The hardwareOathDevices property + * Sets the hardwareOathDevices property value. Exposes the hardware OATH method in the directory. * @param value Value to set for the hardwareOathDevices property. */ public void setHardwareOathDevices(@jakarta.annotation.Nullable final java.util.List value) { diff --git a/src/main/java/com/microsoft/graph/beta/generated/models/BaseSitePage.java b/src/main/java/com/microsoft/graph/beta/generated/models/BaseSitePage.java index 3eeb63fdc4a..7cae4cd6e3d 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/models/BaseSitePage.java +++ b/src/main/java/com/microsoft/graph/beta/generated/models/BaseSitePage.java @@ -48,7 +48,7 @@ public Map> getFieldDeserializers return deserializerMap; } /** - * Gets the pageLayout property value. The name of the page layout of the page. The possible values are: microsoftReserved, article, home, unknownFutureValue. + * Gets the pageLayout property value. 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. * @return a {@link PageLayoutType} */ @jakarta.annotation.Nullable @@ -83,7 +83,7 @@ public void serialize(@jakarta.annotation.Nonnull final SerializationWriter writ writer.writeStringValue("title", this.getTitle()); } /** - * Sets the pageLayout property value. The name of the page layout of the page. The possible values are: microsoftReserved, article, home, unknownFutureValue. + * Sets the pageLayout property value. 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. * @param value Value to set for the pageLayout property. */ public void setPageLayout(@jakarta.annotation.Nullable final PageLayoutType value) { diff --git a/src/main/java/com/microsoft/graph/beta/generated/models/CloudPcCrossRegionDisasterRecoverySetting.java b/src/main/java/com/microsoft/graph/beta/generated/models/CloudPcCrossRegionDisasterRecoverySetting.java index 7e5530756a3..a637ec1918e 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/models/CloudPcCrossRegionDisasterRecoverySetting.java +++ b/src/main/java/com/microsoft/graph/beta/generated/models/CloudPcCrossRegionDisasterRecoverySetting.java @@ -56,7 +56,7 @@ public BackingStore getBackingStore() { return this.backingStore; } /** - * Gets the crossRegionDisasterRecoveryEnabled property value. True if an end user is allowed to set up cross-region disaster recovery for Cloud PC; otherwise, false. The default value is false. + * Gets the crossRegionDisasterRecoveryEnabled property value. 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. * @return a {@link Boolean} */ @jakarta.annotation.Nullable @@ -72,7 +72,7 @@ public CloudPcDisasterRecoveryNetworkSetting getDisasterRecoveryNetworkSetting() return this.backingStore.get("disasterRecoveryNetworkSetting"); } /** - * Gets the disasterRecoveryType property value. The disasterRecoveryType property + * Gets the disasterRecoveryType property value. 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. * @return a {@link CloudPcDisasterRecoveryType} */ @jakarta.annotation.Nullable @@ -138,7 +138,7 @@ public void setBackingStore(@jakarta.annotation.Nonnull final BackingStore value this.backingStore = value; } /** - * Sets the crossRegionDisasterRecoveryEnabled property value. True if an end user is allowed to set up cross-region disaster recovery for Cloud PC; otherwise, false. The default value is false. + * Sets the crossRegionDisasterRecoveryEnabled property value. 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. * @param value Value to set for the crossRegionDisasterRecoveryEnabled property. */ public void setCrossRegionDisasterRecoveryEnabled(@jakarta.annotation.Nullable final Boolean value) { @@ -152,7 +152,7 @@ public void setDisasterRecoveryNetworkSetting(@jakarta.annotation.Nullable final this.backingStore.set("disasterRecoveryNetworkSetting", value); } /** - * Sets the disasterRecoveryType property value. The disasterRecoveryType property + * Sets the disasterRecoveryType property value. 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. * @param value Value to set for the disasterRecoveryType property. */ public void setDisasterRecoveryType(@jakarta.annotation.Nullable final CloudPcDisasterRecoveryType value) { diff --git a/src/main/java/com/microsoft/graph/beta/generated/models/DeviceCompliancePolicy.java b/src/main/java/com/microsoft/graph/beta/generated/models/DeviceCompliancePolicy.java index c281082874b..8ee264d9149 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/models/DeviceCompliancePolicy.java +++ b/src/main/java/com/microsoft/graph/beta/generated/models/DeviceCompliancePolicy.java @@ -141,7 +141,7 @@ public java.util.List getRoleScopeTagIds() { return this.backingStore.get("roleScopeTagIds"); } /** - * Gets the scheduledActionsForRule property value. The list of scheduled action for this rule + * Gets the scheduledActionsForRule property value. The list of scheduled action per rule for this compliance policy. This is a required property when creating any individual per-platform compliance policies. * @return a {@link java.util.List} */ @jakarta.annotation.Nullable @@ -257,7 +257,7 @@ public void setRoleScopeTagIds(@jakarta.annotation.Nullable final java.util.List this.backingStore.set("roleScopeTagIds", value); } /** - * Sets the scheduledActionsForRule property value. The list of scheduled action for this rule + * Sets the scheduledActionsForRule property value. 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 value Value to set for the scheduledActionsForRule property. */ public void setScheduledActionsForRule(@jakarta.annotation.Nullable final java.util.List value) { diff --git a/src/main/java/com/microsoft/graph/beta/generated/models/DeviceManagementConfigurationChoiceSettingDefinition.java b/src/main/java/com/microsoft/graph/beta/generated/models/DeviceManagementConfigurationChoiceSettingDefinition.java index 9f022cdb6dc..6310d89e8d6 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/models/DeviceManagementConfigurationChoiceSettingDefinition.java +++ b/src/main/java/com/microsoft/graph/beta/generated/models/DeviceManagementConfigurationChoiceSettingDefinition.java @@ -32,7 +32,7 @@ public static DeviceManagementConfigurationChoiceSettingDefinition createFromDis return new DeviceManagementConfigurationChoiceSettingDefinition(); } /** - * Gets the defaultOptionId property value. Default option for the choice setting. + * Gets the defaultOptionId property value. Default option for choice setting * @return a {@link String} */ @jakarta.annotation.Nullable @@ -51,7 +51,7 @@ public Map> getFieldDeserializers return deserializerMap; } /** - * Gets the options property value. Options for the setting that can be selected. + * Gets the options property value. Options for the setting that can be selected * @return a {@link java.util.List} */ @jakarta.annotation.Nullable @@ -69,14 +69,14 @@ public void serialize(@jakarta.annotation.Nonnull final SerializationWriter writ writer.writeCollectionOfObjectValues("options", this.getOptions()); } /** - * Sets the defaultOptionId property value. Default option for the choice setting. + * Sets the defaultOptionId property value. Default option for choice setting * @param value Value to set for the defaultOptionId property. */ public void setDefaultOptionId(@jakarta.annotation.Nullable final String value) { this.backingStore.set("defaultOptionId", value); } /** - * Sets the options property value. Options for the setting that can be selected. + * Sets the options property value. Options for the setting that can be selected * @param value Value to set for the options property. */ public void setOptions(@jakarta.annotation.Nullable final java.util.List value) { diff --git a/src/main/java/com/microsoft/graph/beta/generated/models/DeviceManagementConfigurationReferredSettingInformation.java b/src/main/java/com/microsoft/graph/beta/generated/models/DeviceManagementConfigurationReferredSettingInformation.java index 1e8ca805d9e..b3ec96f2168 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/models/DeviceManagementConfigurationReferredSettingInformation.java +++ b/src/main/java/com/microsoft/graph/beta/generated/models/DeviceManagementConfigurationReferredSettingInformation.java @@ -78,7 +78,7 @@ public String getOdataType() { return this.backingStore.get("odataType"); } /** - * Gets the settingDefinitionId property value. Setting definition id that is being referred to a setting. Applicable for reusable setting. + * Gets the settingDefinitionId property value. Setting definition id that is being referred to a setting. Applicable for reusable setting * @return a {@link String} */ @jakarta.annotation.Nullable @@ -118,7 +118,7 @@ public void setOdataType(@jakarta.annotation.Nullable final String value) { this.backingStore.set("odataType", value); } /** - * Sets the settingDefinitionId property value. Setting definition id that is being referred to a setting. Applicable for reusable setting. + * Sets the settingDefinitionId property value. Setting definition id that is being referred to a setting. Applicable for reusable setting * @param value Value to set for the settingDefinitionId property. */ public void setSettingDefinitionId(@jakarta.annotation.Nullable final String value) { diff --git a/src/main/java/com/microsoft/graph/beta/generated/models/DeviceManagementConfigurationSettingGroupCollectionDefinition.java b/src/main/java/com/microsoft/graph/beta/generated/models/DeviceManagementConfigurationSettingGroupCollectionDefinition.java index cd92b22c293..bf95eb6fa2d 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/models/DeviceManagementConfigurationSettingGroupCollectionDefinition.java +++ b/src/main/java/com/microsoft/graph/beta/generated/models/DeviceManagementConfigurationSettingGroupCollectionDefinition.java @@ -36,7 +36,7 @@ public Map> getFieldDeserializers return deserializerMap; } /** - * Gets the maximumCount property value. Maximum number of setting group count in the collection. Valid values 1 to 100 + * Gets the maximumCount property value. Maximum number of setting group count in the collection * @return a {@link Integer} */ @jakarta.annotation.Nullable @@ -44,7 +44,7 @@ public Integer getMaximumCount() { return this.backingStore.get("maximumCount"); } /** - * Gets the minimumCount property value. Minimum number of setting group count in the collection. Valid values 1 to 100 + * Gets the minimumCount property value. Minimum number of setting group count in the collection * @return a {@link Integer} */ @jakarta.annotation.Nullable @@ -62,14 +62,14 @@ public void serialize(@jakarta.annotation.Nonnull final SerializationWriter writ writer.writeIntegerValue("minimumCount", this.getMinimumCount()); } /** - * Sets the maximumCount property value. Maximum number of setting group count in the collection. Valid values 1 to 100 + * Sets the maximumCount property value. Maximum number of setting group count in the collection * @param value Value to set for the maximumCount property. */ public void setMaximumCount(@jakarta.annotation.Nullable final Integer value) { this.backingStore.set("maximumCount", value); } /** - * Sets the minimumCount property value. Minimum number of setting group count in the collection. Valid values 1 to 100 + * Sets the minimumCount property value. Minimum number of setting group count in the collection * @param value Value to set for the minimumCount property. */ public void setMinimumCount(@jakarta.annotation.Nullable final Integer value) { diff --git a/src/main/java/com/microsoft/graph/beta/generated/models/DeviceManagementConfigurationSettingGroupDefinition.java b/src/main/java/com/microsoft/graph/beta/generated/models/DeviceManagementConfigurationSettingGroupDefinition.java index 629aa1a1f46..5a76fa8aeb5 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/models/DeviceManagementConfigurationSettingGroupDefinition.java +++ b/src/main/java/com/microsoft/graph/beta/generated/models/DeviceManagementConfigurationSettingGroupDefinition.java @@ -32,7 +32,7 @@ public static DeviceManagementConfigurationSettingGroupDefinition createFromDisc return new DeviceManagementConfigurationSettingGroupDefinition(); } /** - * Gets the childIds property value. Dependent child settings to this group of settings + * Gets the childIds property value. Dependent child settings to this group of settings. * @return a {@link java.util.List} */ @jakarta.annotation.Nullable @@ -79,7 +79,7 @@ public void serialize(@jakarta.annotation.Nonnull final SerializationWriter writ writer.writeCollectionOfObjectValues("dependentOn", this.getDependentOn()); } /** - * Sets the childIds property value. Dependent child settings to this group of settings + * Sets the childIds property value. Dependent child settings to this group of settings. * @param value Value to set for the childIds property. */ public void setChildIds(@jakarta.annotation.Nullable final java.util.List value) { diff --git a/src/main/java/com/microsoft/graph/beta/generated/models/DeviceManagementConfigurationSimpleSettingCollectionDefinition.java b/src/main/java/com/microsoft/graph/beta/generated/models/DeviceManagementConfigurationSimpleSettingCollectionDefinition.java index 3db7d730eaf..6799f204485 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/models/DeviceManagementConfigurationSimpleSettingCollectionDefinition.java +++ b/src/main/java/com/microsoft/graph/beta/generated/models/DeviceManagementConfigurationSimpleSettingCollectionDefinition.java @@ -36,7 +36,7 @@ public Map> getFieldDeserializers return deserializerMap; } /** - * Gets the maximumCount property value. Maximum number of simple settings in the collection + * Gets the maximumCount property value. Maximum number of simple settings in the collection. Valid values 1 to 100 * @return a {@link Integer} */ @jakarta.annotation.Nullable @@ -44,7 +44,7 @@ public Integer getMaximumCount() { return this.backingStore.get("maximumCount"); } /** - * Gets the minimumCount property value. Minimum number of simple settings in the collection + * Gets the minimumCount property value. Minimum number of simple settings in the collection. Valid values 1 to 100 * @return a {@link Integer} */ @jakarta.annotation.Nullable @@ -62,14 +62,14 @@ public void serialize(@jakarta.annotation.Nonnull final SerializationWriter writ writer.writeIntegerValue("minimumCount", this.getMinimumCount()); } /** - * Sets the maximumCount property value. Maximum number of simple settings in the collection + * Sets the maximumCount property value. Maximum number of simple settings in the collection. Valid values 1 to 100 * @param value Value to set for the maximumCount property. */ public void setMaximumCount(@jakarta.annotation.Nullable final Integer value) { this.backingStore.set("maximumCount", value); } /** - * Sets the minimumCount property value. Minimum number of simple settings in the collection + * Sets the minimumCount property value. Minimum number of simple settings in the collection. Valid values 1 to 100 * @param value Value to set for the minimumCount property. */ public void setMinimumCount(@jakarta.annotation.Nullable final Integer value) { diff --git a/src/main/java/com/microsoft/graph/beta/generated/models/Directory.java b/src/main/java/com/microsoft/graph/beta/generated/models/Directory.java index 26b8029b968..278e1e719d7 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/models/Directory.java +++ b/src/main/java/com/microsoft/graph/beta/generated/models/Directory.java @@ -41,7 +41,7 @@ public java.util.List getAttributeSets() { return this.backingStore.get("attributeSets"); } /** - * Gets the authenticationMethodDevices property value. The authenticationMethodDevices property + * Gets the authenticationMethodDevices property value. Exposes the hardware OATH method in the directory. * @return a {@link AuthenticationMethodDevice} */ @jakarta.annotation.Nullable @@ -246,7 +246,7 @@ public void setAttributeSets(@jakarta.annotation.Nullable final java.util.List getFieldsOfStudy() { return this.backingStore.get("fieldsOfStudy"); } /** - * Gets the grade property value. The final grade, class, GPA or score. + * Gets the grade property value. The final grade, class, GPA, or score. * @return a {@link String} */ @jakarta.annotation.Nullable @@ -131,7 +131,7 @@ public String getGrade() { return this.backingStore.get("grade"); } /** - * Gets the notes property value. Additional notes the user has provided. + * Gets the notes property value. More notes the user provided. * @return a {@link String} */ @jakarta.annotation.Nullable @@ -216,7 +216,7 @@ public void setDescription(@jakarta.annotation.Nullable final String value) { this.backingStore.set("description", value); } /** - * Sets the displayName property value. Long-form name of the program that the user has provided. + * Sets the displayName property value. Long-form name of the program that the user provided. * @param value Value to set for the displayName property. */ public void setDisplayName(@jakarta.annotation.Nullable final String value) { @@ -230,14 +230,14 @@ public void setFieldsOfStudy(@jakarta.annotation.Nullable final java.util.List> getFieldDeserializers return deserializerMap; } /** - * Gets the hashFunction property value. The hashFunction property + * Gets the hashFunction property value. Hash function of the hardrware token. The possible values are: hmacsha1 or hmacsha256. Default value is: hmacsha1. Supports $filter (eq). * @return a {@link HardwareOathTokenHashFunction} */ @jakarta.annotation.Nullable @@ -68,7 +68,7 @@ public HardwareOathTokenHashFunction getHashFunction() { return this.backingStore.get("hashFunction"); } /** - * Gets the manufacturer property value. The manufacturer property + * Gets the manufacturer property value. Manufacturer name of the hardware token. Supports $filter (eq). * @return a {@link String} */ @jakarta.annotation.Nullable @@ -76,7 +76,7 @@ public String getManufacturer() { return this.backingStore.get("manufacturer"); } /** - * Gets the model property value. The model property + * Gets the model property value. Model name of the hardware token. Supports $filter (eq). * @return a {@link String} */ @jakarta.annotation.Nullable @@ -84,7 +84,7 @@ public String getModel() { return this.backingStore.get("model"); } /** - * Gets the secretKey property value. The secretKey property + * Gets the secretKey property value. Secret key of the specific hardware token, provided by the vendor. * @return a {@link String} */ @jakarta.annotation.Nullable @@ -92,7 +92,7 @@ public String getSecretKey() { return this.backingStore.get("secretKey"); } /** - * Gets the serialNumber property value. The serialNumber property + * Gets the serialNumber property value. Serial number of the specific hardware token, often found on the back of the device. Supports $select and $filter (eq). * @return a {@link String} */ @jakarta.annotation.Nullable @@ -100,7 +100,7 @@ public String getSerialNumber() { return this.backingStore.get("serialNumber"); } /** - * Gets the status property value. The status property + * Gets the status property value. Status of the hardware OATH token.The possible values are: available, assigned, activated, failedActivation. Supports $filter(eq). * @return a {@link HardwareOathTokenStatus} */ @jakarta.annotation.Nullable @@ -108,7 +108,7 @@ public HardwareOathTokenStatus getStatus() { return this.backingStore.get("status"); } /** - * Gets the timeIntervalInSeconds property value. The timeIntervalInSeconds property + * Gets the timeIntervalInSeconds property value. Refresh interval of the 6-digit verification code, in seconds. The possible values are: 30 or 60. Supports $filter (eq). * @return a {@link Integer} */ @jakarta.annotation.Nullable @@ -133,63 +133,63 @@ public void serialize(@jakarta.annotation.Nonnull final SerializationWriter writ writer.writeIntegerValue("timeIntervalInSeconds", this.getTimeIntervalInSeconds()); } /** - * Sets the assignedTo property value. The assignedTo property + * Sets the assignedTo property value. User the token is assigned to. Nullable. Supports $filter (eq). * @param value Value to set for the assignedTo property. */ public void setAssignedTo(@jakarta.annotation.Nullable final Identity value) { this.backingStore.set("assignedTo", value); } /** - * Sets the assignTo property value. The assignTo property + * Sets the assignTo property value. Assign the hardware OATH token to a user. * @param value Value to set for the assignTo property. */ public void setAssignTo(@jakarta.annotation.Nullable final User value) { this.backingStore.set("assignTo", value); } /** - * Sets the hashFunction property value. The hashFunction property + * Sets the hashFunction property value. Hash function of the hardrware token. The possible values are: hmacsha1 or hmacsha256. Default value is: hmacsha1. Supports $filter (eq). * @param value Value to set for the hashFunction property. */ public void setHashFunction(@jakarta.annotation.Nullable final HardwareOathTokenHashFunction value) { this.backingStore.set("hashFunction", value); } /** - * Sets the manufacturer property value. The manufacturer property + * Sets the manufacturer property value. Manufacturer name of the hardware token. Supports $filter (eq). * @param value Value to set for the manufacturer property. */ public void setManufacturer(@jakarta.annotation.Nullable final String value) { this.backingStore.set("manufacturer", value); } /** - * Sets the model property value. The model property + * Sets the model property value. Model name of the hardware token. Supports $filter (eq). * @param value Value to set for the model property. */ public void setModel(@jakarta.annotation.Nullable final String value) { this.backingStore.set("model", value); } /** - * Sets the secretKey property value. The secretKey property + * Sets the secretKey property value. Secret key of the specific hardware token, provided by the vendor. * @param value Value to set for the secretKey property. */ public void setSecretKey(@jakarta.annotation.Nullable final String value) { this.backingStore.set("secretKey", value); } /** - * Sets the serialNumber property value. The serialNumber property + * Sets the serialNumber property value. Serial number of the specific hardware token, often found on the back of the device. Supports $select and $filter (eq). * @param value Value to set for the serialNumber property. */ public void setSerialNumber(@jakarta.annotation.Nullable final String value) { this.backingStore.set("serialNumber", value); } /** - * Sets the status property value. The status property + * Sets the status property value. Status of the hardware OATH token.The possible values are: available, assigned, activated, failedActivation. Supports $filter(eq). * @param value Value to set for the status property. */ public void setStatus(@jakarta.annotation.Nullable final HardwareOathTokenStatus value) { this.backingStore.set("status", value); } /** - * Sets the timeIntervalInSeconds property value. The timeIntervalInSeconds property + * Sets the timeIntervalInSeconds property value. Refresh interval of the 6-digit verification code, in seconds. The possible values are: 30 or 60. Supports $filter (eq). * @param value Value to set for the timeIntervalInSeconds property. */ public void setTimeIntervalInSeconds(@jakarta.annotation.Nullable final Integer value) { diff --git a/src/main/java/com/microsoft/graph/beta/generated/models/Identity.java b/src/main/java/com/microsoft/graph/beta/generated/models/Identity.java index cb3d8402d7f..87e928b904a 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/models/Identity.java +++ b/src/main/java/com/microsoft/graph/beta/generated/models/Identity.java @@ -89,7 +89,7 @@ public BackingStore getBackingStore() { return this.backingStore; } /** - * Gets the displayName property value. 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. + * Gets the displayName property value. The display name of the identity. This property is read-only. * @return a {@link String} */ @jakarta.annotation.Nullable @@ -109,7 +109,7 @@ public Map> getFieldDeserializers return deserializerMap; } /** - * Gets the id property value. 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. + * Gets the id property value. The identifier of the identity. This property is read-only. * @return a {@link String} */ @jakarta.annotation.Nullable @@ -151,14 +151,14 @@ public void setBackingStore(@jakarta.annotation.Nonnull final BackingStore value this.backingStore = value; } /** - * Sets the displayName property value. 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. + * Sets the displayName property value. The display name of the identity. This property is read-only. * @param value Value to set for the displayName property. */ public void setDisplayName(@jakarta.annotation.Nullable final String value) { this.backingStore.set("displayName", value); } /** - * Sets the id property value. 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. + * Sets the id property value. The identifier of the identity. This property is read-only. * @param value Value to set for the id property. */ public void setId(@jakarta.annotation.Nullable final String value) { diff --git a/src/main/java/com/microsoft/graph/beta/generated/models/IdentitySet.java b/src/main/java/com/microsoft/graph/beta/generated/models/IdentitySet.java index 462fcb1b4f5..be649f8e258 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/models/IdentitySet.java +++ b/src/main/java/com/microsoft/graph/beta/generated/models/IdentitySet.java @@ -60,7 +60,7 @@ public Map getAdditionalData() { return value; } /** - * Gets the application property value. The Identity of the Application. This property is read-only. + * Gets the application property value. Optional. The application associated with this action. * @return a {@link Identity} */ @jakarta.annotation.Nullable @@ -76,7 +76,7 @@ public BackingStore getBackingStore() { return this.backingStore; } /** - * Gets the device property value. The Identity of the Device. This property is read-only. + * Gets the device property value. Optional. The device associated with this action. * @return a {@link Identity} */ @jakarta.annotation.Nullable @@ -105,7 +105,7 @@ public String getOdataType() { return this.backingStore.get("odataType"); } /** - * Gets the user property value. The Identity of the User. This property is read-only. + * Gets the user property value. Optional. The user associated with this action. * @return a {@link Identity} */ @jakarta.annotation.Nullable @@ -132,7 +132,7 @@ public void setAdditionalData(@jakarta.annotation.Nullable final Map> getFieldDeserializers return deserializerMap; } /** - * Gets the initiatorType property value. Type of initiator. Possible values are: user, application, system, unknownFutureValue. + * Gets the initiatorType property value. The type of the initiator. Possible values are: user, application, system, unknownFutureValue. * @return a {@link InitiatorType} */ @jakarta.annotation.Nullable @@ -53,7 +53,7 @@ public void serialize(@jakarta.annotation.Nonnull final SerializationWriter writ writer.writeEnumValue("initiatorType", this.getInitiatorType()); } /** - * Sets the initiatorType property value. Type of initiator. Possible values are: user, application, system, unknownFutureValue. + * Sets the initiatorType property value. The type of the initiator. Possible values are: user, application, system, unknownFutureValue. * @param value Value to set for the initiatorType property. */ public void setInitiatorType(@jakarta.annotation.Nullable final InitiatorType value) { diff --git a/src/main/java/com/microsoft/graph/beta/generated/models/ItemAttachment.java b/src/main/java/com/microsoft/graph/beta/generated/models/ItemAttachment.java index 9d3418788ab..772609bf961 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/models/ItemAttachment.java +++ b/src/main/java/com/microsoft/graph/beta/generated/models/ItemAttachment.java @@ -36,7 +36,7 @@ public Map> getFieldDeserializers return deserializerMap; } /** - * Gets the item property value. The attached contact, message or event. Navigation property. + * Gets the item property value. The attached contact, message, or event. Navigation property. * @return a {@link OutlookItem} */ @jakarta.annotation.Nullable @@ -53,7 +53,7 @@ public void serialize(@jakarta.annotation.Nonnull final SerializationWriter writ writer.writeObjectValue("item", this.getItem()); } /** - * Sets the item property value. The attached contact, message or event. Navigation property. + * Sets the item property value. The attached contact, message, or event. Navigation property. * @param value Value to set for the item property. */ public void setItem(@jakarta.annotation.Nullable final OutlookItem value) { diff --git a/src/main/java/com/microsoft/graph/beta/generated/models/KeyValuePair.java b/src/main/java/com/microsoft/graph/beta/generated/models/KeyValuePair.java index 1b704cf9838..6c8e60f7359 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/models/KeyValuePair.java +++ b/src/main/java/com/microsoft/graph/beta/generated/models/KeyValuePair.java @@ -68,7 +68,7 @@ public Map> getFieldDeserializers return deserializerMap; } /** - * Gets the name property value. 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. + * Gets the name property value. Name for this key-value pair * @return a {@link String} */ @jakarta.annotation.Nullable @@ -84,7 +84,7 @@ public String getOdataType() { return this.backingStore.get("odataType"); } /** - * Gets the value property value. 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. + * Gets the value property value. Value for this key-value pair * @return a {@link String} */ @jakarta.annotation.Nullable @@ -118,7 +118,7 @@ public void setBackingStore(@jakarta.annotation.Nonnull final BackingStore value this.backingStore = value; } /** - * Sets the name property value. 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. + * Sets the name property value. Name for this key-value pair * @param value Value to set for the name property. */ public void setName(@jakarta.annotation.Nullable final String value) { @@ -132,7 +132,7 @@ public void setOdataType(@jakarta.annotation.Nullable final String value) { this.backingStore.set("odataType", value); } /** - * Sets the value property value. 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. + * Sets the value property value. Value for this key-value pair * @param value Value to set for the value property. */ public void setValue(@jakarta.annotation.Nullable final String value) { diff --git a/src/main/java/com/microsoft/graph/beta/generated/models/MacOsLobAppAssignmentSettings.java b/src/main/java/com/microsoft/graph/beta/generated/models/MacOsLobAppAssignmentSettings.java index 279bfd72943..9b7124da50b 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/models/MacOsLobAppAssignmentSettings.java +++ b/src/main/java/com/microsoft/graph/beta/generated/models/MacOsLobAppAssignmentSettings.java @@ -39,7 +39,7 @@ public Map> getFieldDeserializers return deserializerMap; } /** - * Gets the uninstallOnDeviceRemoval property value. Whether or not to uninstall the app when device is removed from Intune. + * Gets the uninstallOnDeviceRemoval property value. 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. * @return a {@link Boolean} */ @jakarta.annotation.Nullable @@ -56,7 +56,7 @@ public void serialize(@jakarta.annotation.Nonnull final SerializationWriter writ writer.writeBooleanValue("uninstallOnDeviceRemoval", this.getUninstallOnDeviceRemoval()); } /** - * Sets the uninstallOnDeviceRemoval property value. Whether or not to uninstall the app when device is removed from Intune. + * Sets the uninstallOnDeviceRemoval property value. 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. * @param value Value to set for the uninstallOnDeviceRemoval property. */ public void setUninstallOnDeviceRemoval(@jakarta.annotation.Nullable final Boolean value) { diff --git a/src/main/java/com/microsoft/graph/beta/generated/models/MailTips.java b/src/main/java/com/microsoft/graph/beta/generated/models/MailTips.java index ba99af285c7..b0f564581fa 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/models/MailTips.java +++ b/src/main/java/com/microsoft/graph/beta/generated/models/MailTips.java @@ -49,7 +49,7 @@ public Map getAdditionalData() { return value; } /** - * Gets the automaticReplies property value. Mail tips for automatic reply if it has been set up by the recipient. + * Gets the automaticReplies property value. Mailtips for an automatic reply if set up by the recipient. * @return a {@link AutomaticRepliesMailTips} */ @jakarta.annotation.Nullable @@ -73,7 +73,7 @@ public String getCustomMailTip() { return this.backingStore.get("customMailTip"); } /** - * Gets the deliveryRestricted property value. 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. + * Gets the deliveryRestricted property value. 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. * @return a {@link Boolean} */ @jakarta.annotation.Nullable @@ -127,7 +127,7 @@ public Map> getFieldDeserializers return deserializerMap; } /** - * Gets the isModerated property value. 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. + * Gets the isModerated property value. 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. * @return a {@link Boolean} */ @jakarta.annotation.Nullable @@ -143,7 +143,7 @@ public Boolean getMailboxFull() { return this.backingStore.get("mailboxFull"); } /** - * Gets the maxMessageSize property value. The maximum message size that has been configured for the recipient's organization or mailbox. + * Gets the maxMessageSize property value. The maximum message size configured for the recipient's organization or mailbox. * @return a {@link Integer} */ @jakarta.annotation.Nullable @@ -159,7 +159,7 @@ public String getOdataType() { return this.backingStore.get("odataType"); } /** - * Gets the recipientScope property value. 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. + * Gets the recipientScope property value. 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. * @return a {@link EnumSet} */ @jakarta.annotation.Nullable @@ -211,7 +211,7 @@ public void setAdditionalData(@jakarta.annotation.Nullable final Map value) { diff --git a/src/main/java/com/microsoft/graph/beta/generated/models/MailboxRestoreArtifact.java b/src/main/java/com/microsoft/graph/beta/generated/models/MailboxRestoreArtifact.java index 9d102e8c08e..18863719c1b 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/models/MailboxRestoreArtifact.java +++ b/src/main/java/com/microsoft/graph/beta/generated/models/MailboxRestoreArtifact.java @@ -44,7 +44,7 @@ public Map> getFieldDeserializers return deserializerMap; } /** - * Gets the restoredFolderId property value. The new restored folder identifier for the user. + * Gets the restoredFolderId property value. The newly restored folder identifier for the user. * @return a {@link String} */ @jakarta.annotation.Nullable @@ -60,7 +60,7 @@ public String getRestoredFolderName() { return this.backingStore.get("restoredFolderName"); } /** - * Gets the restoredItemCount property value. The restoredItemCount property + * Gets the restoredItemCount property value. The number of items that are being restored in the folder. * @return a {@link Integer} */ @jakarta.annotation.Nullable @@ -78,7 +78,7 @@ public void serialize(@jakarta.annotation.Nonnull final SerializationWriter writ writer.writeIntegerValue("restoredItemCount", this.getRestoredItemCount()); } /** - * Sets the restoredFolderId property value. The new restored folder identifier for the user. + * Sets the restoredFolderId property value. The newly restored folder identifier for the user. * @param value Value to set for the restoredFolderId property. */ public void setRestoredFolderId(@jakarta.annotation.Nullable final String value) { @@ -92,7 +92,7 @@ public void setRestoredFolderName(@jakarta.annotation.Nullable final String valu this.backingStore.set("restoredFolderName", value); } /** - * Sets the restoredItemCount property value. The restoredItemCount property + * Sets the restoredItemCount property value. The number of items that are being restored in the folder. * @param value Value to set for the restoredItemCount property. */ public void setRestoredItemCount(@jakarta.annotation.Nullable final Integer value) { diff --git a/src/main/java/com/microsoft/graph/beta/generated/models/NewsLinkPage.java b/src/main/java/com/microsoft/graph/beta/generated/models/NewsLinkPage.java index d18c7e38bf7..d8717c5dc60 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/models/NewsLinkPage.java +++ b/src/main/java/com/microsoft/graph/beta/generated/models/NewsLinkPage.java @@ -25,7 +25,7 @@ public static NewsLinkPage createFromDiscriminatorValue(@jakarta.annotation.Nonn return new NewsLinkPage(); } /** - * Gets the bannerImageWebUrl property value. The bannerImageWebUrl property + * Gets the bannerImageWebUrl property value. A link to the banner image for the newsLinkPage. * @return a {@link String} */ @jakarta.annotation.Nullable @@ -45,7 +45,7 @@ public Map> getFieldDeserializers return deserializerMap; } /** - * Gets the newsSharepointIds property value. The newsSharepointIds property + * Gets the newsSharepointIds property value. The SharePoint IDs of the referenced news article if it's recognized as a SharePoint resource. Read-only. * @return a {@link SharepointIds} */ @jakarta.annotation.Nullable @@ -53,7 +53,7 @@ public SharepointIds getNewsSharepointIds() { return this.backingStore.get("newsSharepointIds"); } /** - * Gets the newsWebUrl property value. The newsWebUrl property + * Gets the newsWebUrl property value. The URL of the news article referenced by the newsLinkPage. It can be an external link. * @return a {@link String} */ @jakarta.annotation.Nullable @@ -72,21 +72,21 @@ public void serialize(@jakarta.annotation.Nonnull final SerializationWriter writ writer.writeStringValue("newsWebUrl", this.getNewsWebUrl()); } /** - * Sets the bannerImageWebUrl property value. The bannerImageWebUrl property + * Sets the bannerImageWebUrl property value. A link to the banner image for the newsLinkPage. * @param value Value to set for the bannerImageWebUrl property. */ public void setBannerImageWebUrl(@jakarta.annotation.Nullable final String value) { this.backingStore.set("bannerImageWebUrl", value); } /** - * Sets the newsSharepointIds property value. The newsSharepointIds property + * Sets the newsSharepointIds property value. The SharePoint IDs of the referenced news article if it's recognized as a SharePoint resource. Read-only. * @param value Value to set for the newsSharepointIds property. */ public void setNewsSharepointIds(@jakarta.annotation.Nullable final SharepointIds value) { this.backingStore.set("newsSharepointIds", value); } /** - * Sets the newsWebUrl property value. The newsWebUrl property + * Sets the newsWebUrl property value. The URL of the news article referenced by the newsLinkPage. It can be an external link. * @param value Value to set for the newsWebUrl property. */ public void setNewsWebUrl(@jakarta.annotation.Nullable final String value) { diff --git a/src/main/java/com/microsoft/graph/beta/generated/models/OnAttributeCollectionExternalUsersSelfServiceSignUp.java b/src/main/java/com/microsoft/graph/beta/generated/models/OnAttributeCollectionExternalUsersSelfServiceSignUp.java index e95fd594b48..5031032a986 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/models/OnAttributeCollectionExternalUsersSelfServiceSignUp.java +++ b/src/main/java/com/microsoft/graph/beta/generated/models/OnAttributeCollectionExternalUsersSelfServiceSignUp.java @@ -26,7 +26,7 @@ public static OnAttributeCollectionExternalUsersSelfServiceSignUp createFromDisc return new OnAttributeCollectionExternalUsersSelfServiceSignUp(); } /** - * Gets the attributeCollectionPage property value. 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. + * Gets the attributeCollectionPage property value. 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. * @return a {@link AuthenticationAttributeCollectionPage} */ @jakarta.annotation.Nullable @@ -63,7 +63,7 @@ public void serialize(@jakarta.annotation.Nonnull final SerializationWriter writ writer.writeCollectionOfObjectValues("attributes", this.getAttributes()); } /** - * Sets the attributeCollectionPage property value. 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. + * Sets the attributeCollectionPage property value. 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. * @param value Value to set for the attributeCollectionPage property. */ public void setAttributeCollectionPage(@jakarta.annotation.Nullable final AuthenticationAttributeCollectionPage value) { diff --git a/src/main/java/com/microsoft/graph/beta/generated/models/OnInteractiveAuthFlowStartListener.java b/src/main/java/com/microsoft/graph/beta/generated/models/OnInteractiveAuthFlowStartListener.java index 3024c8d0a0e..9ec3a47dd74 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/models/OnInteractiveAuthFlowStartListener.java +++ b/src/main/java/com/microsoft/graph/beta/generated/models/OnInteractiveAuthFlowStartListener.java @@ -36,7 +36,7 @@ public Map> getFieldDeserializers return deserializerMap; } /** - * Gets the handler property value. Required. Configuration for what to invoke if the event resolves to this listener. This lets us define potential handler configurations per-event. + * Gets the handler property value. 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. * @return a {@link OnInteractiveAuthFlowStartHandler} */ @jakarta.annotation.Nullable @@ -53,7 +53,7 @@ public void serialize(@jakarta.annotation.Nonnull final SerializationWriter writ writer.writeObjectValue("handler", this.getHandler()); } /** - * Sets the handler property value. Required. Configuration for what to invoke if the event resolves to this listener. This lets us define potential handler configurations per-event. + * Sets the handler property value. 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. * @param value Value to set for the handler property. */ public void setHandler(@jakarta.annotation.Nullable final OnInteractiveAuthFlowStartHandler value) { diff --git a/src/main/java/com/microsoft/graph/beta/generated/models/OneDriveForBusinessProtectionPolicy.java b/src/main/java/com/microsoft/graph/beta/generated/models/OneDriveForBusinessProtectionPolicy.java index 1bb740286a5..6038d5a2ac7 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/models/OneDriveForBusinessProtectionPolicy.java +++ b/src/main/java/com/microsoft/graph/beta/generated/models/OneDriveForBusinessProtectionPolicy.java @@ -26,7 +26,7 @@ public static OneDriveForBusinessProtectionPolicy createFromDiscriminatorValue(@ return new OneDriveForBusinessProtectionPolicy(); } /** - * Gets the driveInclusionRules property value. Contains the details of the Onedrive for Business protection rule. + * Gets the driveInclusionRules property value. Contains the details of the OneDrive for Work or School protection rule. * @return a {@link java.util.List} */ @jakarta.annotation.Nullable @@ -34,7 +34,7 @@ public java.util.List getDriveInclusionRules() { return this.backingStore.get("driveInclusionRules"); } /** - * Gets the driveProtectionUnits property value. Contains the protection units associated with a OneDrive for Business protection policy. + * Gets the driveProtectionUnits property value. Contains the protection units associated with a OneDrive for Work or School protection policy. * @return a {@link java.util.List} */ @jakarta.annotation.Nullable @@ -73,14 +73,14 @@ public void serialize(@jakarta.annotation.Nonnull final SerializationWriter writ writer.writeCollectionOfObjectValues("driveProtectionUnitsBulkAdditionJobs", this.getDriveProtectionUnitsBulkAdditionJobs()); } /** - * Sets the driveInclusionRules property value. Contains the details of the Onedrive for Business protection rule. + * Sets the driveInclusionRules property value. Contains the details of the OneDrive for Work or School protection rule. * @param value Value to set for the driveInclusionRules property. */ public void setDriveInclusionRules(@jakarta.annotation.Nullable final java.util.List value) { this.backingStore.set("driveInclusionRules", value); } /** - * Sets the driveProtectionUnits property value. Contains the protection units associated with a OneDrive for Business protection policy. + * Sets the driveProtectionUnits property value. Contains the protection units associated with a OneDrive for Work or School protection policy. * @param value Value to set for the driveProtectionUnits property. */ public void setDriveProtectionUnits(@jakarta.annotation.Nullable final java.util.List value) { diff --git a/src/main/java/com/microsoft/graph/beta/generated/models/OneDriveForBusinessRestoreSession.java b/src/main/java/com/microsoft/graph/beta/generated/models/OneDriveForBusinessRestoreSession.java index ad44703d26b..7acf84f886c 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/models/OneDriveForBusinessRestoreSession.java +++ b/src/main/java/com/microsoft/graph/beta/generated/models/OneDriveForBusinessRestoreSession.java @@ -26,7 +26,7 @@ public static OneDriveForBusinessRestoreSession createFromDiscriminatorValue(@ja return new OneDriveForBusinessRestoreSession(); } /** - * Gets the driveRestoreArtifacts property value. A collection of restore points and destination details that can be used to restore a OneDrive for Business drive. + * Gets the driveRestoreArtifacts property value. A collection of restore points and destination details that can be used to restore a OneDrive for Work or School drive. * @return a {@link java.util.List} */ @jakarta.annotation.Nullable @@ -63,7 +63,7 @@ public void serialize(@jakarta.annotation.Nonnull final SerializationWriter writ writer.writeCollectionOfObjectValues("driveRestoreArtifactsBulkAdditionRequests", this.getDriveRestoreArtifactsBulkAdditionRequests()); } /** - * Sets the driveRestoreArtifacts property value. A collection of restore points and destination details that can be used to restore a OneDrive for Business drive. + * Sets the driveRestoreArtifacts property value. A collection of restore points and destination details that can be used to restore a OneDrive for Work or School drive. * @param value Value to set for the driveRestoreArtifacts property. */ public void setDriveRestoreArtifacts(@jakarta.annotation.Nullable final java.util.List value) { diff --git a/src/main/java/com/microsoft/graph/beta/generated/models/Onenote.java b/src/main/java/com/microsoft/graph/beta/generated/models/Onenote.java index 2d27b95805f..a1d3c40a770 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/models/Onenote.java +++ b/src/main/java/com/microsoft/graph/beta/generated/models/Onenote.java @@ -40,7 +40,7 @@ public Map> getFieldDeserializers return deserializerMap; } /** - * Gets the notebooks property value. The collection of OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * Gets the notebooks property value. The collection of OneNote notebooks that the user or group owns. Read-only. Nullable. * @return a {@link java.util.List} */ @jakarta.annotation.Nullable @@ -56,7 +56,7 @@ public java.util.List getOperations() { return this.backingStore.get("operations"); } /** - * Gets the pages property value. The pages in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * Gets the pages property value. The pages in all OneNote notebooks that the user or group owns. Read-only. Nullable. * @return a {@link java.util.List} */ @jakarta.annotation.Nullable @@ -72,7 +72,7 @@ public java.util.List getResources() { return this.backingStore.get("resources"); } /** - * Gets the sectionGroups property value. The section groups in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * Gets the sectionGroups property value. The section groups in all OneNote notebooks that the user or group owns. Read-only. Nullable. * @return a {@link java.util.List} */ @jakarta.annotation.Nullable @@ -80,7 +80,7 @@ public java.util.List getSectionGroups() { return this.backingStore.get("sectionGroups"); } /** - * Gets the sections property value. The sections in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * Gets the sections property value. The sections in all OneNote notebooks that the user or group owns. Read-only. Nullable. * @return a {@link java.util.List} */ @jakarta.annotation.Nullable @@ -102,7 +102,7 @@ public void serialize(@jakarta.annotation.Nonnull final SerializationWriter writ writer.writeCollectionOfObjectValues("sections", this.getSections()); } /** - * Sets the notebooks property value. The collection of OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * Sets the notebooks property value. The collection of OneNote notebooks that the user or group owns. Read-only. Nullable. * @param value Value to set for the notebooks property. */ public void setNotebooks(@jakarta.annotation.Nullable final java.util.List value) { @@ -116,7 +116,7 @@ public void setOperations(@jakarta.annotation.Nullable final java.util.List value) { @@ -130,14 +130,14 @@ public void setResources(@jakarta.annotation.Nullable final java.util.List value) { this.backingStore.set("sectionGroups", value); } /** - * Sets the sections property value. The sections in all OneNote notebooks that are owned by the user or group. Read-only. Nullable. + * Sets the sections property value. The sections in all OneNote notebooks that the user or group owns. Read-only. Nullable. * @param value Value to set for the sections property. */ public void setSections(@jakarta.annotation.Nullable final java.util.List value) { diff --git a/src/main/java/com/microsoft/graph/beta/generated/models/RestoreSessionArtifactCount.java b/src/main/java/com/microsoft/graph/beta/generated/models/RestoreSessionArtifactCount.java index 89cde5f43de..f0c99b42868 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/models/RestoreSessionArtifactCount.java +++ b/src/main/java/com/microsoft/graph/beta/generated/models/RestoreSessionArtifactCount.java @@ -56,7 +56,7 @@ public BackingStore getBackingStore() { return this.backingStore; } /** - * Gets the completed property value. The completed property + * Gets the completed property value. The number of artifacts whose restoration completed. * @return a {@link Integer} */ @jakarta.annotation.Nullable @@ -64,7 +64,7 @@ public Integer getCompleted() { return this.backingStore.get("completed"); } /** - * Gets the failed property value. The failed property + * Gets the failed property value. The number of artifacts whose restoration failed. * @return a {@link Integer} */ @jakarta.annotation.Nullable @@ -86,7 +86,7 @@ public Map> getFieldDeserializers return deserializerMap; } /** - * Gets the inProgress property value. The inProgress property + * Gets the inProgress property value. The number of artifacts whose restoration is in progress. * @return a {@link Integer} */ @jakarta.annotation.Nullable @@ -102,7 +102,7 @@ public String getOdataType() { return this.backingStore.get("odataType"); } /** - * Gets the total property value. The total property + * Gets the total property value. The number of artifacts present in the restore session. * @return a {@link Integer} */ @jakarta.annotation.Nullable @@ -138,21 +138,21 @@ public void setBackingStore(@jakarta.annotation.Nonnull final BackingStore value this.backingStore = value; } /** - * Sets the completed property value. The completed property + * Sets the completed property value. The number of artifacts whose restoration completed. * @param value Value to set for the completed property. */ public void setCompleted(@jakarta.annotation.Nullable final Integer value) { this.backingStore.set("completed", value); } /** - * Sets the failed property value. The failed property + * Sets the failed property value. The number of artifacts whose restoration failed. * @param value Value to set for the failed property. */ public void setFailed(@jakarta.annotation.Nullable final Integer value) { this.backingStore.set("failed", value); } /** - * Sets the inProgress property value. The inProgress property + * Sets the inProgress property value. The number of artifacts whose restoration is in progress. * @param value Value to set for the inProgress property. */ public void setInProgress(@jakarta.annotation.Nullable final Integer value) { @@ -166,7 +166,7 @@ public void setOdataType(@jakarta.annotation.Nullable final String value) { this.backingStore.set("odataType", value); } /** - * Sets the total property value. The total property + * Sets the total property value. The number of artifacts present in the restore session. * @param value Value to set for the total property. */ public void setTotal(@jakarta.annotation.Nullable final Integer value) { diff --git a/src/main/java/com/microsoft/graph/beta/generated/models/RestoreSessionBase.java b/src/main/java/com/microsoft/graph/beta/generated/models/RestoreSessionBase.java index 91afa9abffd..a80cc62f900 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/models/RestoreSessionBase.java +++ b/src/main/java/com/microsoft/graph/beta/generated/models/RestoreSessionBase.java @@ -101,7 +101,7 @@ public OffsetDateTime getLastModifiedDateTime() { return this.backingStore.get("lastModifiedDateTime"); } /** - * Gets the restoreJobType property value. The restoreJobType property + * Gets the restoreJobType property value. Indicates whether the restore session was created normally or by a bulk job. * @return a {@link RestoreJobType} */ @jakarta.annotation.Nullable @@ -109,7 +109,7 @@ public RestoreJobType getRestoreJobType() { return this.backingStore.get("restoreJobType"); } /** - * Gets the restoreSessionArtifactCount property value. The restoreSessionArtifactCount property + * Gets the restoreSessionArtifactCount property value. The number of metadata artifacts that belong to this restore session. * @return a {@link RestoreSessionArtifactCount} */ @jakarta.annotation.Nullable @@ -184,14 +184,14 @@ public void setLastModifiedDateTime(@jakarta.annotation.Nullable final OffsetDat this.backingStore.set("lastModifiedDateTime", value); } /** - * Sets the restoreJobType property value. The restoreJobType property + * Sets the restoreJobType property value. Indicates whether the restore session was created normally or by a bulk job. * @param value Value to set for the restoreJobType property. */ public void setRestoreJobType(@jakarta.annotation.Nullable final RestoreJobType value) { this.backingStore.set("restoreJobType", value); } /** - * Sets the restoreSessionArtifactCount property value. The restoreSessionArtifactCount property + * Sets the restoreSessionArtifactCount property value. The number of metadata artifacts that belong to this restore session. * @param value Value to set for the restoreSessionArtifactCount property. */ public void setRestoreSessionArtifactCount(@jakarta.annotation.Nullable final RestoreSessionArtifactCount value) { diff --git a/src/main/java/com/microsoft/graph/beta/generated/models/WindowsDomainJoinConfiguration.java b/src/main/java/com/microsoft/graph/beta/generated/models/WindowsDomainJoinConfiguration.java index 5559029a4ea..d258eae6c09 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/models/WindowsDomainJoinConfiguration.java +++ b/src/main/java/com/microsoft/graph/beta/generated/models/WindowsDomainJoinConfiguration.java @@ -67,7 +67,7 @@ public Map> getFieldDeserializers return deserializerMap; } /** - * Gets the networkAccessConfigurations property value. Reference to device configurations required for network connectivity + * Gets the networkAccessConfigurations property value. Reference to device configurations required for network connectivity. This collection can contain a maximum of 2 elements. * @return a {@link java.util.List} */ @jakarta.annotation.Nullable @@ -117,7 +117,7 @@ public void setComputerNameSuffixRandomCharCount(@jakarta.annotation.Nullable fi this.backingStore.set("computerNameSuffixRandomCharCount", value); } /** - * Sets the networkAccessConfigurations property value. Reference to device configurations required for network connectivity + * Sets the networkAccessConfigurations property value. Reference to device configurations required for network connectivity. This collection can contain a maximum of 2 elements. * @param value Value to set for the networkAccessConfigurations property. */ public void setNetworkAccessConfigurations(@jakarta.annotation.Nullable final java.util.List value) { diff --git a/src/main/java/com/microsoft/graph/beta/generated/models/WindowsUniversalAppXAppAssignmentSettings.java b/src/main/java/com/microsoft/graph/beta/generated/models/WindowsUniversalAppXAppAssignmentSettings.java index 0872224ab0f..52d6a1a72bf 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/models/WindowsUniversalAppXAppAssignmentSettings.java +++ b/src/main/java/com/microsoft/graph/beta/generated/models/WindowsUniversalAppXAppAssignmentSettings.java @@ -39,7 +39,7 @@ public Map> getFieldDeserializers return deserializerMap; } /** - * Gets the useDeviceContext property value. Whether or not to use device execution context for Windows Universal AppX mobile app. + * Gets the useDeviceContext property value. 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. * @return a {@link Boolean} */ @jakarta.annotation.Nullable @@ -56,7 +56,7 @@ public void serialize(@jakarta.annotation.Nonnull final SerializationWriter writ writer.writeBooleanValue("useDeviceContext", this.getUseDeviceContext()); } /** - * Sets the useDeviceContext property value. Whether or not to use device execution context for Windows Universal AppX mobile app. + * Sets the useDeviceContext property value. 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. * @param value Value to set for the useDeviceContext property. */ public void setUseDeviceContext(@jakarta.annotation.Nullable final Boolean value) { diff --git a/src/main/java/com/microsoft/graph/beta/generated/models/externalconnectors/Configuration.java b/src/main/java/com/microsoft/graph/beta/generated/models/externalconnectors/Configuration.java index 6a9b77c461a..0b4c8023fb1 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/models/externalconnectors/Configuration.java +++ b/src/main/java/com/microsoft/graph/beta/generated/models/externalconnectors/Configuration.java @@ -48,7 +48,7 @@ public Map getAdditionalData() { return value; } /** - * Gets the authorizedAppIds property value. A collection of application IDs for registered Microsoft Entra apps that are allowed to manage the externalConnection and to index content in the externalConnection. + * Gets the authorizedAppIds property value. A collection of application IDs for registered Microsoft Entra apps allowed to manage the externalConnection and index content in the externalConnection. * @return a {@link java.util.List} */ @jakarta.annotation.Nullable @@ -100,7 +100,7 @@ public void setAdditionalData(@jakarta.annotation.Nullable final Map value) { diff --git a/src/main/java/com/microsoft/graph/beta/generated/models/externalconnectors/External.java b/src/main/java/com/microsoft/graph/beta/generated/models/externalconnectors/External.java index 81e0fcd1f2d..d67d821e807 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/models/externalconnectors/External.java +++ b/src/main/java/com/microsoft/graph/beta/generated/models/externalconnectors/External.java @@ -50,7 +50,7 @@ public Map getAdditionalData() { return value; } /** - * Gets the authorizationSystems property value. Represents an onboarded AWS account, Azure subscription, or GCP project that Microsoft Entra Permissions Management will collect and analyze permissions and actions on. + * Gets the authorizationSystems property value. 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. * @return a {@link java.util.List} */ @jakarta.annotation.Nullable @@ -122,7 +122,7 @@ public void setAdditionalData(@jakarta.annotation.Nullable final Map value) { diff --git a/src/main/java/com/microsoft/graph/beta/generated/models/networkaccess/Connectivity.java b/src/main/java/com/microsoft/graph/beta/generated/models/networkaccess/Connectivity.java index 0bb962cc90d..9b53924fac0 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/models/networkaccess/Connectivity.java +++ b/src/main/java/com/microsoft/graph/beta/generated/models/networkaccess/Connectivity.java @@ -26,7 +26,7 @@ public static Connectivity createFromDiscriminatorValue(@jakarta.annotation.Nonn return new Connectivity(); } /** - * Gets the branches property value. Branches represent locations for connectivity. DEPRECATED AND TO BE RETIRED SOON. Use the remoteNetwork relationship and its associated APIs instead. + * Gets the branches property value. The locations for connectivity. DEPRECATED AND TO BE RETIRED SOON. Use the remoteNetwork relationship and its associated APIs instead. * @return a {@link java.util.List} */ @jakarta.annotation.Nullable @@ -46,7 +46,7 @@ public Map> getFieldDeserializers return deserializerMap; } /** - * Gets the remoteNetworks property value. Represent locations, such as branches, that are connected to Global Secure Access services through an IPsec tunnel. + * Gets the remoteNetworks property value. The locations, such as branches, that are connected to Global Secure Access services through an IPsec tunnel. * @return a {@link java.util.List} */ @jakarta.annotation.Nullable @@ -73,14 +73,14 @@ public void serialize(@jakarta.annotation.Nonnull final SerializationWriter writ writer.writeCollectionOfObjectValues("webCategories", this.getWebCategories()); } /** - * Sets the branches property value. Branches represent locations for connectivity. DEPRECATED AND TO BE RETIRED SOON. Use the remoteNetwork relationship and its associated APIs instead. + * Sets the branches property value. The locations for connectivity. DEPRECATED AND TO BE RETIRED SOON. Use the remoteNetwork relationship and its associated APIs instead. * @param value Value to set for the branches property. */ public void setBranches(@jakarta.annotation.Nullable final java.util.List value) { this.backingStore.set("branches", value); } /** - * Sets the remoteNetworks property value. Represent locations, such as branches, that are connected to Global Secure Access services through an IPsec tunnel. + * Sets the remoteNetworks property value. The locations, such as branches, that are connected to Global Secure Access services through an IPsec tunnel. * @param value Value to set for the remoteNetworks property. */ public void setRemoteNetworks(@jakarta.annotation.Nullable final java.util.List value) { diff --git a/src/main/java/com/microsoft/graph/beta/generated/models/networkaccess/Profile.java b/src/main/java/com/microsoft/graph/beta/generated/models/networkaccess/Profile.java index c0586217f7e..94c883b889c 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/models/networkaccess/Profile.java +++ b/src/main/java/com/microsoft/graph/beta/generated/models/networkaccess/Profile.java @@ -58,7 +58,7 @@ public Map> getFieldDeserializers return deserializerMap; } /** - * Gets the lastModifiedDateTime property value. Profile last modified time. + * Gets the lastModifiedDateTime property value. The date and time when the profile was last modified. * @return a {@link OffsetDateTime} */ @jakarta.annotation.Nullable @@ -66,7 +66,7 @@ public OffsetDateTime getLastModifiedDateTime() { return this.backingStore.get("lastModifiedDateTime"); } /** - * Gets the name property value. Profile name. + * Gets the name property value. The name of the profile. * @return a {@link String} */ @jakarta.annotation.Nullable @@ -74,7 +74,7 @@ public String getName() { return this.backingStore.get("name"); } /** - * Gets the policies property value. Traffic forwarding policies associated with this profile. + * Gets the policies property value. The traffic forwarding policies associated with this profile. * @return a {@link java.util.List} */ @jakarta.annotation.Nullable @@ -119,21 +119,21 @@ public void setDescription(@jakarta.annotation.Nullable final String value) { this.backingStore.set("description", value); } /** - * Sets the lastModifiedDateTime property value. Profile last modified time. + * Sets the lastModifiedDateTime property value. The date and time when the profile was last modified. * @param value Value to set for the lastModifiedDateTime property. */ public void setLastModifiedDateTime(@jakarta.annotation.Nullable final OffsetDateTime value) { this.backingStore.set("lastModifiedDateTime", value); } /** - * Sets the name property value. Profile name. + * Sets the name property value. The name of the profile. * @param value Value to set for the name property. */ public void setName(@jakarta.annotation.Nullable final String value) { this.backingStore.set("name", value); } /** - * Sets the policies property value. Traffic forwarding policies associated with this profile. + * Sets the policies property value. The traffic forwarding policies associated with this profile. * @param value Value to set for the policies property. */ public void setPolicies(@jakarta.annotation.Nullable final java.util.List value) { diff --git a/src/main/java/com/microsoft/graph/beta/generated/networkaccess/connectivity/branches/item/forwardingprofiles/item/policies/PoliciesRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/networkaccess/connectivity/branches/item/forwardingprofiles/item/policies/PoliciesRequestBuilder.java index 453010ce254..06b3fb15d4e 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/networkaccess/connectivity/branches/item/forwardingprofiles/item/policies/PoliciesRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/networkaccess/connectivity/branches/item/forwardingprofiles/item/policies/PoliciesRequestBuilder.java @@ -66,7 +66,7 @@ public PoliciesRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @ super(requestAdapter, "{+baseurl}/networkAccess/connectivity/branches/{branchSite%2Did}/forwardingProfiles/{forwardingProfile%2Did}/policies{?%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * Traffic forwarding policies associated with this profile. + * The traffic forwarding policies associated with this profile. * @return a {@link PolicyLinkCollectionResponse} * @throws ODataError When receiving a 4XX or 5XX status code * @deprecated @@ -78,7 +78,7 @@ public PolicyLinkCollectionResponse get() { return get(null); } /** - * Traffic forwarding policies associated with this profile. + * The traffic forwarding policies associated with this profile. * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link PolicyLinkCollectionResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -125,7 +125,7 @@ public PolicyLink post(@jakarta.annotation.Nonnull final PolicyLink body, @jakar return this.requestAdapter.send(requestInfo, errorMapping, PolicyLink::createFromDiscriminatorValue); } /** - * Traffic forwarding policies associated with this profile. + * The traffic forwarding policies associated with this profile. * @return a {@link RequestInformation} * @deprecated * The Branches API is deprecated and will stop returning data on March 20, 2024. Please use the new Remote Network API. as of 2022-06/PrivatePreview:NetworkAccess @@ -136,7 +136,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * Traffic forwarding policies associated with this profile. + * The traffic forwarding policies associated with this profile. * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} * @deprecated @@ -194,7 +194,7 @@ public PoliciesRequestBuilder withUrl(@jakarta.annotation.Nonnull final String r return new PoliciesRequestBuilder(rawUrl, requestAdapter); } /** - * Traffic forwarding policies associated with this profile. + * The traffic forwarding policies associated with this profile. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/networkaccess/connectivity/branches/item/forwardingprofiles/item/policies/item/PolicyLinkItemRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/networkaccess/connectivity/branches/item/forwardingprofiles/item/policies/item/PolicyLinkItemRequestBuilder.java index 3542d29c2d6..89c45b31bb7 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/networkaccess/connectivity/branches/item/forwardingprofiles/item/policies/item/PolicyLinkItemRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/networkaccess/connectivity/branches/item/forwardingprofiles/item/policies/item/PolicyLinkItemRequestBuilder.java @@ -73,7 +73,7 @@ public void delete(@jakarta.annotation.Nullable final java.util.function.Consume this.requestAdapter.sendPrimitive(requestInfo, errorMapping, Void.class); } /** - * Traffic forwarding policies associated with this profile. + * The traffic forwarding policies associated with this profile. * @return a {@link PolicyLink} * @throws ODataError When receiving a 4XX or 5XX status code * @deprecated @@ -85,7 +85,7 @@ public PolicyLink get() { return get(null); } /** - * Traffic forwarding policies associated with this profile. + * The traffic forwarding policies associated with this profile. * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link PolicyLink} * @throws ODataError When receiving a 4XX or 5XX status code @@ -158,7 +158,7 @@ public RequestInformation toDeleteRequestInformation(@jakarta.annotation.Nullabl return requestInfo; } /** - * Traffic forwarding policies associated with this profile. + * The traffic forwarding policies associated with this profile. * @return a {@link RequestInformation} * @deprecated * The Branches API is deprecated and will stop returning data on March 20, 2024. Please use the new Remote Network API. as of 2022-06/PrivatePreview:NetworkAccess @@ -169,7 +169,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * Traffic forwarding policies associated with this profile. + * The traffic forwarding policies associated with this profile. * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} * @deprecated @@ -233,7 +233,7 @@ public PolicyLinkItemRequestBuilder withUrl(@jakarta.annotation.Nonnull final St public class DeleteRequestConfiguration extends BaseRequestConfiguration { } /** - * Traffic forwarding policies associated with this profile. + * The traffic forwarding policies associated with this profile. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/networkaccess/connectivity/remotenetworks/RemoteNetworksRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/networkaccess/connectivity/remotenetworks/RemoteNetworksRequestBuilder.java index 456a443e655..25d9b05e657 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/networkaccess/connectivity/remotenetworks/RemoteNetworksRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/networkaccess/connectivity/remotenetworks/RemoteNetworksRequestBuilder.java @@ -60,7 +60,7 @@ public RemoteNetworksRequestBuilder(@jakarta.annotation.Nonnull final String raw super(requestAdapter, "{+baseurl}/networkAccess/connectivity/remoteNetworks{?%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * 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. * @return a {@link RemoteNetworkCollectionResponse} * @throws ODataError When receiving a 4XX or 5XX status code */ @@ -69,7 +69,7 @@ public RemoteNetworkCollectionResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RemoteNetworkCollectionResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -109,7 +109,7 @@ public RemoteNetwork post(@jakarta.annotation.Nonnull final RemoteNetwork body, return this.requestAdapter.send(requestInfo, errorMapping, RemoteNetwork::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -117,7 +117,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -163,7 +163,7 @@ public RemoteNetworksRequestBuilder withUrl(@jakarta.annotation.Nonnull final St return new RemoteNetworksRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/networkaccess/connectivity/remotenetworks/item/RemoteNetworkItemRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/networkaccess/connectivity/remotenetworks/item/RemoteNetworkItemRequestBuilder.java index 3a557817a0c..5e71f5f88d9 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/networkaccess/connectivity/remotenetworks/item/RemoteNetworkItemRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/networkaccess/connectivity/remotenetworks/item/RemoteNetworkItemRequestBuilder.java @@ -82,7 +82,7 @@ public void delete(@jakarta.annotation.Nullable final java.util.function.Consume this.requestAdapter.sendPrimitive(requestInfo, errorMapping, Void.class); } /** - * 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. * @return a {@link RemoteNetwork} * @throws ODataError When receiving a 4XX or 5XX status code */ @@ -91,7 +91,7 @@ public RemoteNetwork get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RemoteNetwork} * @throws ODataError When receiving a 4XX or 5XX status code @@ -149,7 +149,7 @@ public RequestInformation toDeleteRequestInformation(@jakarta.annotation.Nullabl return requestInfo; } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -157,7 +157,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -209,7 +209,7 @@ public RemoteNetworkItemRequestBuilder withUrl(@jakarta.annotation.Nonnull final public class DeleteRequestConfiguration extends BaseRequestConfiguration { } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/networkaccess/connectivity/remotenetworks/item/forwardingprofiles/item/policies/PoliciesRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/networkaccess/connectivity/remotenetworks/item/forwardingprofiles/item/policies/PoliciesRequestBuilder.java index 5c57be23387..09061bc705f 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/networkaccess/connectivity/remotenetworks/item/forwardingprofiles/item/policies/PoliciesRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/networkaccess/connectivity/remotenetworks/item/forwardingprofiles/item/policies/PoliciesRequestBuilder.java @@ -60,7 +60,7 @@ public PoliciesRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @ super(requestAdapter, "{+baseurl}/networkAccess/connectivity/remoteNetworks/{remoteNetwork%2Did}/forwardingProfiles/{forwardingProfile%2Did}/policies{?%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * Traffic forwarding policies associated with this profile. + * The traffic forwarding policies associated with this profile. * @return a {@link PolicyLinkCollectionResponse} * @throws ODataError When receiving a 4XX or 5XX status code */ @@ -69,7 +69,7 @@ public PolicyLinkCollectionResponse get() { return get(null); } /** - * Traffic forwarding policies associated with this profile. + * The traffic forwarding policies associated with this profile. * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link PolicyLinkCollectionResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -107,7 +107,7 @@ public PolicyLink post(@jakarta.annotation.Nonnull final PolicyLink body, @jakar return this.requestAdapter.send(requestInfo, errorMapping, PolicyLink::createFromDiscriminatorValue); } /** - * Traffic forwarding policies associated with this profile. + * The traffic forwarding policies associated with this profile. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -115,7 +115,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * Traffic forwarding policies associated with this profile. + * The traffic forwarding policies associated with this profile. * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -161,7 +161,7 @@ public PoliciesRequestBuilder withUrl(@jakarta.annotation.Nonnull final String r return new PoliciesRequestBuilder(rawUrl, requestAdapter); } /** - * Traffic forwarding policies associated with this profile. + * The traffic forwarding policies associated with this profile. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/networkaccess/connectivity/remotenetworks/item/forwardingprofiles/item/policies/item/PolicyLinkItemRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/networkaccess/connectivity/remotenetworks/item/forwardingprofiles/item/policies/item/PolicyLinkItemRequestBuilder.java index 129ddba57ea..5e95950b0aa 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/networkaccess/connectivity/remotenetworks/item/forwardingprofiles/item/policies/item/PolicyLinkItemRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/networkaccess/connectivity/remotenetworks/item/forwardingprofiles/item/policies/item/PolicyLinkItemRequestBuilder.java @@ -64,7 +64,7 @@ public void delete(@jakarta.annotation.Nullable final java.util.function.Consume this.requestAdapter.sendPrimitive(requestInfo, errorMapping, Void.class); } /** - * Traffic forwarding policies associated with this profile. + * The traffic forwarding policies associated with this profile. * @return a {@link PolicyLink} * @throws ODataError When receiving a 4XX or 5XX status code */ @@ -73,7 +73,7 @@ public PolicyLink get() { return get(null); } /** - * Traffic forwarding policies associated with this profile. + * The traffic forwarding policies associated with this profile. * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link PolicyLink} * @throws ODataError When receiving a 4XX or 5XX status code @@ -131,7 +131,7 @@ public RequestInformation toDeleteRequestInformation(@jakarta.annotation.Nullabl return requestInfo; } /** - * Traffic forwarding policies associated with this profile. + * The traffic forwarding policies associated with this profile. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -139,7 +139,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * Traffic forwarding policies associated with this profile. + * The traffic forwarding policies associated with this profile. * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -191,7 +191,7 @@ public PolicyLinkItemRequestBuilder withUrl(@jakarta.annotation.Nonnull final St public class DeleteRequestConfiguration extends BaseRequestConfiguration { } /** - * Traffic forwarding policies associated with this profile. + * The traffic forwarding policies associated with this profile. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/networkaccess/filteringprofiles/item/policies/PoliciesRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/networkaccess/filteringprofiles/item/policies/PoliciesRequestBuilder.java index d7b76158a24..1c171d804b0 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/networkaccess/filteringprofiles/item/policies/PoliciesRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/networkaccess/filteringprofiles/item/policies/PoliciesRequestBuilder.java @@ -60,7 +60,7 @@ public PoliciesRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @ super(requestAdapter, "{+baseurl}/networkAccess/filteringProfiles/{filteringProfile%2Did}/policies{?%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * Traffic forwarding policies associated with this profile. + * The traffic forwarding policies associated with this profile. * @return a {@link PolicyLinkCollectionResponse} * @throws ODataError When receiving a 4XX or 5XX status code */ @@ -69,7 +69,7 @@ public PolicyLinkCollectionResponse get() { return get(null); } /** - * Traffic forwarding policies associated with this profile. + * The traffic forwarding policies associated with this profile. * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link PolicyLinkCollectionResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -107,7 +107,7 @@ public PolicyLink post(@jakarta.annotation.Nonnull final PolicyLink body, @jakar return this.requestAdapter.send(requestInfo, errorMapping, PolicyLink::createFromDiscriminatorValue); } /** - * Traffic forwarding policies associated with this profile. + * The traffic forwarding policies associated with this profile. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -115,7 +115,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * Traffic forwarding policies associated with this profile. + * The traffic forwarding policies associated with this profile. * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -161,7 +161,7 @@ public PoliciesRequestBuilder withUrl(@jakarta.annotation.Nonnull final String r return new PoliciesRequestBuilder(rawUrl, requestAdapter); } /** - * Traffic forwarding policies associated with this profile. + * The traffic forwarding policies associated with this profile. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/networkaccess/filteringprofiles/item/policies/item/PolicyLinkItemRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/networkaccess/filteringprofiles/item/policies/item/PolicyLinkItemRequestBuilder.java index 9211b4419de..c3471180bc8 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/networkaccess/filteringprofiles/item/policies/item/PolicyLinkItemRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/networkaccess/filteringprofiles/item/policies/item/PolicyLinkItemRequestBuilder.java @@ -64,7 +64,7 @@ public void delete(@jakarta.annotation.Nullable final java.util.function.Consume this.requestAdapter.sendPrimitive(requestInfo, errorMapping, Void.class); } /** - * Traffic forwarding policies associated with this profile. + * The traffic forwarding policies associated with this profile. * @return a {@link PolicyLink} * @throws ODataError When receiving a 4XX or 5XX status code */ @@ -73,7 +73,7 @@ public PolicyLink get() { return get(null); } /** - * Traffic forwarding policies associated with this profile. + * The traffic forwarding policies associated with this profile. * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link PolicyLink} * @throws ODataError When receiving a 4XX or 5XX status code @@ -131,7 +131,7 @@ public RequestInformation toDeleteRequestInformation(@jakarta.annotation.Nullabl return requestInfo; } /** - * Traffic forwarding policies associated with this profile. + * The traffic forwarding policies associated with this profile. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -139,7 +139,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * Traffic forwarding policies associated with this profile. + * The traffic forwarding policies associated with this profile. * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -191,7 +191,7 @@ public PolicyLinkItemRequestBuilder withUrl(@jakarta.annotation.Nonnull final St public class DeleteRequestConfiguration extends BaseRequestConfiguration { } /** - * Traffic forwarding policies associated with this profile. + * The traffic forwarding policies associated with this profile. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/policies/crosstenantaccesspolicy/partners/item/identitysynchronization/IdentitySynchronizationRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/policies/crosstenantaccesspolicy/partners/item/identitysynchronization/IdentitySynchronizationRequestBuilder.java index 9ffe5488a9d..7f141e622cf 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/policies/crosstenantaccesspolicy/partners/item/identitysynchronization/IdentitySynchronizationRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/policies/crosstenantaccesspolicy/partners/item/identitysynchronization/IdentitySynchronizationRequestBuilder.java @@ -81,23 +81,23 @@ public CrossTenantIdentitySyncPolicyPartner get(@jakarta.annotation.Nullable fin return this.requestAdapter.send(requestInfo, errorMapping, CrossTenantIdentitySyncPolicyPartner::createFromDiscriminatorValue); } /** - * 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 * @return a {@link CrossTenantIdentitySyncPolicyPartner} * @throws ODataError When receiving a 4XX or 5XX status code - * @see Find more info here + * @see Find more info here */ @jakarta.annotation.Nullable public CrossTenantIdentitySyncPolicyPartner put(@jakarta.annotation.Nonnull final CrossTenantIdentitySyncPolicyPartner body) { return put(body, null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link CrossTenantIdentitySyncPolicyPartner} * @throws ODataError When receiving a 4XX or 5XX status code - * @see Find more info here + * @see Find more info here */ @jakarta.annotation.Nullable public CrossTenantIdentitySyncPolicyPartner put(@jakarta.annotation.Nonnull final CrossTenantIdentitySyncPolicyPartner body, @jakarta.annotation.Nullable final java.util.function.Consumer requestConfiguration) { @@ -148,7 +148,7 @@ public RequestInformation toGetRequestInformation(@jakarta.annotation.Nullable f return requestInfo; } /** - * 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 * @return a {@link RequestInformation} */ @@ -157,7 +157,7 @@ public RequestInformation toPutRequestInformation(@jakarta.annotation.Nonnull fi return toPutRequestInformation(body, null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} diff --git a/src/main/java/com/microsoft/graph/beta/generated/policies/federatedtokenvalidationpolicy/FederatedTokenValidationPolicyRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/policies/federatedtokenvalidationpolicy/FederatedTokenValidationPolicyRequestBuilder.java index 0920e5e3918..1a6e4fc2c67 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/policies/federatedtokenvalidationpolicy/FederatedTokenValidationPolicyRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/policies/federatedtokenvalidationpolicy/FederatedTokenValidationPolicyRequestBuilder.java @@ -55,21 +55,21 @@ public void delete(@jakarta.annotation.Nullable final java.util.function.Consume this.requestAdapter.sendPrimitive(requestInfo, errorMapping, Void.class); } /** - * Get a list of the federatedTokenValidationPolicy objects and their properties. + * Read the properties and relationships of a federatedTokenValidationPolicy object. * @return a {@link FederatedTokenValidationPolicy} * @throws ODataError When receiving a 4XX or 5XX status code - * @see Find more info here + * @see Find more info here */ @jakarta.annotation.Nullable public FederatedTokenValidationPolicy get() { return get(null); } /** - * Get a list of the federatedTokenValidationPolicy objects and their properties. + * Read the properties and relationships of a federatedTokenValidationPolicy object. * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link FederatedTokenValidationPolicy} * @throws ODataError When receiving a 4XX or 5XX status code - * @see Find more info here + * @see Find more info here */ @jakarta.annotation.Nullable public FederatedTokenValidationPolicy get(@jakarta.annotation.Nullable final java.util.function.Consumer requestConfiguration) { @@ -126,7 +126,7 @@ public RequestInformation toDeleteRequestInformation(@jakarta.annotation.Nullabl return requestInfo; } /** - * Get a list of the federatedTokenValidationPolicy objects and their properties. + * Read the properties and relationships of a federatedTokenValidationPolicy object. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -134,7 +134,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * Get a list of the federatedTokenValidationPolicy objects and their properties. + * Read the properties and relationships of a federatedTokenValidationPolicy object. * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -186,7 +186,7 @@ public FederatedTokenValidationPolicyRequestBuilder withUrl(@jakarta.annotation. public class DeleteRequestConfiguration extends BaseRequestConfiguration { } /** - * Get a list of the federatedTokenValidationPolicy objects and their properties. + * Read the properties and relationships of a federatedTokenValidationPolicy object. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/riskdetections/RiskDetectionsRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/riskdetections/RiskDetectionsRequestBuilder.java index 796fcc9564e..d756edcf8c8 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/riskdetections/RiskDetectionsRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/riskdetections/RiskDetectionsRequestBuilder.java @@ -51,21 +51,21 @@ public RiskDetectionsRequestBuilder(@jakarta.annotation.Nonnull final String raw super(requestAdapter, "{+baseurl}/riskDetections{?%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * Retrieve the properties of a riskDetection object. + * Retrieve the properties of a collection of riskDetection objects. * @return a {@link RiskDetectionCollectionResponse} * @throws ODataError When receiving a 4XX or 5XX status code - * @see Find more info here + * @see Find more info here */ @jakarta.annotation.Nullable public RiskDetectionCollectionResponse get() { return get(null); } /** - * Retrieve the properties of a riskDetection object. + * Retrieve the properties of a collection of riskDetection objects. * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RiskDetectionCollectionResponse} * @throws ODataError When receiving a 4XX or 5XX status code - * @see Find more info here + * @see Find more info here */ @jakarta.annotation.Nullable public RiskDetectionCollectionResponse get(@jakarta.annotation.Nullable final java.util.function.Consumer requestConfiguration) { @@ -100,7 +100,7 @@ public RiskDetection post(@jakarta.annotation.Nonnull final RiskDetection body, return this.requestAdapter.send(requestInfo, errorMapping, RiskDetection::createFromDiscriminatorValue); } /** - * Retrieve the properties of a riskDetection object. + * Retrieve the properties of a collection of riskDetection objects. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -108,7 +108,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * Retrieve the properties of a riskDetection object. + * Retrieve the properties of a collection of riskDetection objects. * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -154,7 +154,7 @@ public RiskDetectionsRequestBuilder withUrl(@jakarta.annotation.Nonnull final St return new RiskDetectionsRequestBuilder(rawUrl, requestAdapter); } /** - * Retrieve the properties of a riskDetection object. + * Retrieve the properties of a collection of riskDetection objects. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/serviceprincipals/item/claimspolicy/ClaimsPolicyRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/serviceprincipals/item/claimspolicy/ClaimsPolicyRequestBuilder.java index 7c167fc297a..e2ee66520c3 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/serviceprincipals/item/claimspolicy/ClaimsPolicyRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/serviceprincipals/item/claimspolicy/ClaimsPolicyRequestBuilder.java @@ -61,23 +61,23 @@ public CustomClaimsPolicy get(@jakarta.annotation.Nullable final java.util.funct return this.requestAdapter.send(requestInfo, errorMapping, CustomClaimsPolicy::createFromDiscriminatorValue); } /** - * Create a new customClaimsPolicy object if it doesn't exist, or replace an existing one. + * Update a customClaimsPolicy object. * @param body The request body * @return a {@link CustomClaimsPolicy} * @throws ODataError When receiving a 4XX or 5XX status code - * @see Find more info here + * @see Find more info here */ @jakarta.annotation.Nullable public CustomClaimsPolicy patch(@jakarta.annotation.Nonnull final CustomClaimsPolicy body) { return patch(body, null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link CustomClaimsPolicy} * @throws ODataError When receiving a 4XX or 5XX status code - * @see Find more info here + * @see Find more info here */ @jakarta.annotation.Nullable public CustomClaimsPolicy patch(@jakarta.annotation.Nonnull final CustomClaimsPolicy body, @jakarta.annotation.Nullable final java.util.function.Consumer requestConfiguration) { @@ -88,23 +88,23 @@ public CustomClaimsPolicy patch(@jakarta.annotation.Nonnull final CustomClaimsPo return this.requestAdapter.send(requestInfo, errorMapping, CustomClaimsPolicy::createFromDiscriminatorValue); } /** - * Create a new customClaimsPolicy object if it doesn't exist, or replace an existing one. + * Update a customClaimsPolicy object. * @param body The request body * @return a {@link CustomClaimsPolicy} * @throws ODataError When receiving a 4XX or 5XX status code - * @see Find more info here + * @see Find more info here */ @jakarta.annotation.Nullable public CustomClaimsPolicy put(@jakarta.annotation.Nonnull final CustomClaimsPolicy body) { return put(body, null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link CustomClaimsPolicy} * @throws ODataError When receiving a 4XX or 5XX status code - * @see Find more info here + * @see Find more info here */ @jakarta.annotation.Nullable public CustomClaimsPolicy put(@jakarta.annotation.Nonnull final CustomClaimsPolicy body, @jakarta.annotation.Nullable final java.util.function.Consumer requestConfiguration) { @@ -135,7 +135,7 @@ public RequestInformation toGetRequestInformation(@jakarta.annotation.Nullable f return requestInfo; } /** - * Create a new customClaimsPolicy object if it doesn't exist, or replace an existing one. + * Update a customClaimsPolicy object. * @param body The request body * @return a {@link RequestInformation} */ @@ -144,7 +144,7 @@ public RequestInformation toPatchRequestInformation(@jakarta.annotation.Nonnull return toPatchRequestInformation(body, null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} @@ -159,7 +159,7 @@ public RequestInformation toPatchRequestInformation(@jakarta.annotation.Nonnull return requestInfo; } /** - * Create a new customClaimsPolicy object if it doesn't exist, or replace an existing one. + * Update a customClaimsPolicy object. * @param body The request body * @return a {@link RequestInformation} */ @@ -168,7 +168,7 @@ public RequestInformation toPutRequestInformation(@jakarta.annotation.Nonnull fi return toPutRequestInformation(body, null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} diff --git a/src/main/java/com/microsoft/graph/beta/generated/sites/item/onenote/notebooks/NotebooksRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/sites/item/onenote/notebooks/NotebooksRequestBuilder.java index c28535d9893..9f6df73824b 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/sites/item/onenote/notebooks/NotebooksRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/sites/item/onenote/notebooks/NotebooksRequestBuilder.java @@ -70,7 +70,7 @@ public NotebooksRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, super(requestAdapter, "{+baseurl}/sites/{site%2Did}/onenote/notebooks{?%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * 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. * @return a {@link NotebookCollectionResponse} * @throws ODataError When receiving a 4XX or 5XX status code */ @@ -79,7 +79,7 @@ public NotebookCollectionResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link NotebookCollectionResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -127,7 +127,7 @@ public Notebook post(@jakarta.annotation.Nonnull final Notebook body, @jakarta.a return this.requestAdapter.send(requestInfo, errorMapping, Notebook::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -135,7 +135,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -181,7 +181,7 @@ public NotebooksRequestBuilder withUrl(@jakarta.annotation.Nonnull final String return new NotebooksRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/sites/item/onenote/notebooks/item/NotebookItemRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/sites/item/onenote/notebooks/item/NotebookItemRequestBuilder.java index aa0567769ef..a4443f100f4 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/sites/item/onenote/notebooks/item/NotebookItemRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/sites/item/onenote/notebooks/item/NotebookItemRequestBuilder.java @@ -82,7 +82,7 @@ public void delete(@jakarta.annotation.Nullable final java.util.function.Consume this.requestAdapter.sendPrimitive(requestInfo, errorMapping, Void.class); } /** - * 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. * @return a {@link Notebook} * @throws ODataError When receiving a 4XX or 5XX status code */ @@ -91,7 +91,7 @@ public Notebook get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link Notebook} * @throws ODataError When receiving a 4XX or 5XX status code @@ -149,7 +149,7 @@ public RequestInformation toDeleteRequestInformation(@jakarta.annotation.Nullabl return requestInfo; } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -157,7 +157,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -209,7 +209,7 @@ public NotebookItemRequestBuilder withUrl(@jakarta.annotation.Nonnull final Stri public class DeleteRequestConfiguration extends BaseRequestConfiguration { } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/sites/item/onenote/pages/PagesRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/sites/item/onenote/pages/PagesRequestBuilder.java index f08875701ce..9aea0d0d4e4 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/sites/item/onenote/pages/PagesRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/sites/item/onenote/pages/PagesRequestBuilder.java @@ -60,7 +60,7 @@ public PagesRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @jak super(requestAdapter, "{+baseurl}/sites/{site%2Did}/onenote/pages{?%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * 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. * @return a {@link OnenotePageCollectionResponse} * @throws ODataError When receiving a 4XX or 5XX status code */ @@ -69,7 +69,7 @@ public OnenotePageCollectionResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link OnenotePageCollectionResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -107,7 +107,7 @@ public OnenotePage post(@jakarta.annotation.Nonnull final OnenotePage body, @jak return this.requestAdapter.send(requestInfo, errorMapping, OnenotePage::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -115,7 +115,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -161,7 +161,7 @@ public PagesRequestBuilder withUrl(@jakarta.annotation.Nonnull final String rawU return new PagesRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/sites/item/onenote/pages/item/OnenotePageItemRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/sites/item/onenote/pages/item/OnenotePageItemRequestBuilder.java index 35866868d31..8a84c8a0297 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/sites/item/onenote/pages/item/OnenotePageItemRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/sites/item/onenote/pages/item/OnenotePageItemRequestBuilder.java @@ -109,7 +109,7 @@ public void delete(@jakarta.annotation.Nullable final java.util.function.Consume this.requestAdapter.sendPrimitive(requestInfo, errorMapping, Void.class); } /** - * 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. * @return a {@link OnenotePage} * @throws ODataError When receiving a 4XX or 5XX status code */ @@ -118,7 +118,7 @@ public OnenotePage get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link OnenotePage} * @throws ODataError When receiving a 4XX or 5XX status code @@ -176,7 +176,7 @@ public RequestInformation toDeleteRequestInformation(@jakarta.annotation.Nullabl return requestInfo; } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -184,7 +184,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -236,7 +236,7 @@ public OnenotePageItemRequestBuilder withUrl(@jakarta.annotation.Nonnull final S public class DeleteRequestConfiguration extends BaseRequestConfiguration { } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/sites/item/onenote/sectiongroups/SectionGroupsRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/sites/item/onenote/sectiongroups/SectionGroupsRequestBuilder.java index d8f972a2bd7..d0cb5839d03 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/sites/item/onenote/sectiongroups/SectionGroupsRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/sites/item/onenote/sectiongroups/SectionGroupsRequestBuilder.java @@ -60,7 +60,7 @@ public SectionGroupsRequestBuilder(@jakarta.annotation.Nonnull final String rawU super(requestAdapter, "{+baseurl}/sites/{site%2Did}/onenote/sectionGroups{?%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * 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. * @return a {@link SectionGroupCollectionResponse} * @throws ODataError When receiving a 4XX or 5XX status code */ @@ -69,7 +69,7 @@ public SectionGroupCollectionResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link SectionGroupCollectionResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -107,7 +107,7 @@ public SectionGroup post(@jakarta.annotation.Nonnull final SectionGroup body, @j return this.requestAdapter.send(requestInfo, errorMapping, SectionGroup::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -115,7 +115,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -161,7 +161,7 @@ public SectionGroupsRequestBuilder withUrl(@jakarta.annotation.Nonnull final Str return new SectionGroupsRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/sites/item/onenote/sectiongroups/item/SectionGroupItemRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/sites/item/onenote/sectiongroups/item/SectionGroupItemRequestBuilder.java index 16652af40b9..fbe2488606f 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/sites/item/onenote/sectiongroups/item/SectionGroupItemRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/sites/item/onenote/sectiongroups/item/SectionGroupItemRequestBuilder.java @@ -91,7 +91,7 @@ public void delete(@jakarta.annotation.Nullable final java.util.function.Consume this.requestAdapter.sendPrimitive(requestInfo, errorMapping, Void.class); } /** - * 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. * @return a {@link SectionGroup} * @throws ODataError When receiving a 4XX or 5XX status code */ @@ -100,7 +100,7 @@ public SectionGroup get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link SectionGroup} * @throws ODataError When receiving a 4XX or 5XX status code @@ -158,7 +158,7 @@ public RequestInformation toDeleteRequestInformation(@jakarta.annotation.Nullabl return requestInfo; } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -166,7 +166,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -218,7 +218,7 @@ public SectionGroupItemRequestBuilder withUrl(@jakarta.annotation.Nonnull final public class DeleteRequestConfiguration extends BaseRequestConfiguration { } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/sites/item/onenote/sections/SectionsRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/sites/item/onenote/sections/SectionsRequestBuilder.java index a1e688a0749..8876d4a8e94 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/sites/item/onenote/sections/SectionsRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/sites/item/onenote/sections/SectionsRequestBuilder.java @@ -60,7 +60,7 @@ public SectionsRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @ super(requestAdapter, "{+baseurl}/sites/{site%2Did}/onenote/sections{?%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * 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. * @return a {@link OnenoteSectionCollectionResponse} * @throws ODataError When receiving a 4XX or 5XX status code */ @@ -69,7 +69,7 @@ public OnenoteSectionCollectionResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link OnenoteSectionCollectionResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -107,7 +107,7 @@ public OnenoteSection post(@jakarta.annotation.Nonnull final OnenoteSection body return this.requestAdapter.send(requestInfo, errorMapping, OnenoteSection::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -115,7 +115,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -161,7 +161,7 @@ public SectionsRequestBuilder withUrl(@jakarta.annotation.Nonnull final String r return new SectionsRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/sites/item/onenote/sections/item/OnenoteSectionItemRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/sites/item/onenote/sections/item/OnenoteSectionItemRequestBuilder.java index dc169a9d2cb..1fff26b0e19 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/sites/item/onenote/sections/item/OnenoteSectionItemRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/sites/item/onenote/sections/item/OnenoteSectionItemRequestBuilder.java @@ -100,7 +100,7 @@ public void delete(@jakarta.annotation.Nullable final java.util.function.Consume this.requestAdapter.sendPrimitive(requestInfo, errorMapping, Void.class); } /** - * 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. * @return a {@link OnenoteSection} * @throws ODataError When receiving a 4XX or 5XX status code */ @@ -109,7 +109,7 @@ public OnenoteSection get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link OnenoteSection} * @throws ODataError When receiving a 4XX or 5XX status code @@ -167,7 +167,7 @@ public RequestInformation toDeleteRequestInformation(@jakarta.annotation.Nullabl return requestInfo; } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -175,7 +175,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -227,7 +227,7 @@ public OnenoteSectionItemRequestBuilder withUrl(@jakarta.annotation.Nonnull fina public class DeleteRequestConfiguration extends BaseRequestConfiguration { } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/sites/item/pages/PagesRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/sites/item/pages/PagesRequestBuilder.java index e096abdd61c..9539528430f 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/sites/item/pages/PagesRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/sites/item/pages/PagesRequestBuilder.java @@ -93,23 +93,23 @@ public BaseSitePageCollectionResponse get(@jakarta.annotation.Nullable final jav return this.requestAdapter.send(requestInfo, errorMapping, BaseSitePageCollectionResponse::createFromDiscriminatorValue); } /** - * 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 * @return a {@link BaseSitePage} * @throws ODataError When receiving a 4XX or 5XX status code - * @see Find more info here + * @see Find more info here */ @jakarta.annotation.Nullable public BaseSitePage post(@jakarta.annotation.Nonnull final BaseSitePage body) { return post(body, null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link BaseSitePage} * @throws ODataError When receiving a 4XX or 5XX status code - * @see Find more info here + * @see Find more info here */ @jakarta.annotation.Nullable public BaseSitePage post(@jakarta.annotation.Nonnull final BaseSitePage body, @jakarta.annotation.Nullable final java.util.function.Consumer requestConfiguration) { @@ -140,7 +140,7 @@ public RequestInformation toGetRequestInformation(@jakarta.annotation.Nullable f return requestInfo; } /** - * 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 * @return a {@link RequestInformation} */ @@ -149,7 +149,7 @@ public RequestInformation toPostRequestInformation(@jakarta.annotation.Nonnull f return toPostRequestInformation(body, null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} diff --git a/src/main/java/com/microsoft/graph/beta/generated/solutions/backuprestore/onedriveforbusinessprotectionpolicies/item/driveprotectionunits/item/DriveProtectionUnitItemRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/solutions/backuprestore/onedriveforbusinessprotectionpolicies/item/driveprotectionunits/item/DriveProtectionUnitItemRequestBuilder.java index 5607a315f9e..b6960e0a108 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/solutions/backuprestore/onedriveforbusinessprotectionpolicies/item/driveprotectionunits/item/DriveProtectionUnitItemRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/solutions/backuprestore/onedriveforbusinessprotectionpolicies/item/driveprotectionunits/item/DriveProtectionUnitItemRequestBuilder.java @@ -37,7 +37,7 @@ public DriveProtectionUnitItemRequestBuilder(@jakarta.annotation.Nonnull final S super(requestAdapter, "{+baseurl}/solutions/backupRestore/oneDriveForBusinessProtectionPolicies/{oneDriveForBusinessProtectionPolicy%2Did}/driveProtectionUnits/{driveProtectionUnit%2Did}{?%24expand,%24select}", rawUrl); } /** - * 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. * @return a {@link DriveProtectionUnit} * @throws ODataError When receiving a 4XX or 5XX status code */ @@ -46,7 +46,7 @@ public DriveProtectionUnit get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link DriveProtectionUnit} * @throws ODataError When receiving a 4XX or 5XX status code @@ -59,7 +59,7 @@ public DriveProtectionUnit get(@jakarta.annotation.Nullable final java.util.func return this.requestAdapter.send(requestInfo, errorMapping, DriveProtectionUnit::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -67,7 +67,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -89,7 +89,7 @@ public DriveProtectionUnitItemRequestBuilder withUrl(@jakarta.annotation.Nonnull return new DriveProtectionUnitItemRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/solutions/backuprestore/onedriveforbusinessrestoresessions/item/driverestoreartifacts/item/DriveRestoreArtifactItemRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/solutions/backuprestore/onedriveforbusinessrestoresessions/item/driverestoreartifacts/item/DriveRestoreArtifactItemRequestBuilder.java index f474f264e63..acb78c51b4d 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/solutions/backuprestore/onedriveforbusinessrestoresessions/item/driverestoreartifacts/item/DriveRestoreArtifactItemRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/solutions/backuprestore/onedriveforbusinessrestoresessions/item/driverestoreartifacts/item/DriveRestoreArtifactItemRequestBuilder.java @@ -64,7 +64,7 @@ public void delete(@jakarta.annotation.Nullable final java.util.function.Consume this.requestAdapter.sendPrimitive(requestInfo, errorMapping, Void.class); } /** - * 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. * @return a {@link DriveRestoreArtifact} * @throws ODataError When receiving a 4XX or 5XX status code */ @@ -73,7 +73,7 @@ public DriveRestoreArtifact get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link DriveRestoreArtifact} * @throws ODataError When receiving a 4XX or 5XX status code @@ -131,7 +131,7 @@ public RequestInformation toDeleteRequestInformation(@jakarta.annotation.Nullabl return requestInfo; } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -139,7 +139,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -191,7 +191,7 @@ public DriveRestoreArtifactItemRequestBuilder withUrl(@jakarta.annotation.Nonnul public class DeleteRequestConfiguration extends BaseRequestConfiguration { } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/teams/item/channels/item/messages/MessagesRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/teams/item/channels/item/messages/MessagesRequestBuilder.java index 3ae5ccb0c26..2715d51d5a7 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/teams/item/channels/item/messages/MessagesRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/teams/item/channels/item/messages/MessagesRequestBuilder.java @@ -93,23 +93,23 @@ public ChatMessageCollectionResponse get(@jakarta.annotation.Nullable final java return this.requestAdapter.send(requestInfo, errorMapping, ChatMessageCollectionResponse::createFromDiscriminatorValue); } /** - * Send a new chatMessage in the specified channel. + * Send a new chatMessage in the specified channel or a chat. * @param body The request body * @return a {@link ChatMessage} * @throws ODataError When receiving a 4XX or 5XX status code - * @see Find more info here + * @see Find more info here */ @jakarta.annotation.Nullable public ChatMessage post(@jakarta.annotation.Nonnull final ChatMessage body) { return post(body, null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link ChatMessage} * @throws ODataError When receiving a 4XX or 5XX status code - * @see Find more info here + * @see Find more info here */ @jakarta.annotation.Nullable public ChatMessage post(@jakarta.annotation.Nonnull final ChatMessage body, @jakarta.annotation.Nullable final java.util.function.Consumer requestConfiguration) { @@ -140,7 +140,7 @@ public RequestInformation toGetRequestInformation(@jakarta.annotation.Nullable f return requestInfo; } /** - * Send a new chatMessage in the specified channel. + * Send a new chatMessage in the specified channel or a chat. * @param body The request body * @return a {@link RequestInformation} */ @@ -149,7 +149,7 @@ public RequestInformation toPostRequestInformation(@jakarta.annotation.Nonnull f return toPostRequestInformation(body, null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} diff --git a/src/main/java/com/microsoft/graph/beta/generated/teams/item/schedule/openshifts/OpenShiftsRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/teams/item/schedule/openshifts/OpenShiftsRequestBuilder.java index 749d7dc9deb..ff7e3abc834 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/teams/item/schedule/openshifts/OpenShiftsRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/teams/item/schedule/openshifts/OpenShiftsRequestBuilder.java @@ -84,7 +84,7 @@ public OpenShiftCollectionResponse get(@jakarta.annotation.Nullable final java.u return this.requestAdapter.send(requestInfo, errorMapping, OpenShiftCollectionResponse::createFromDiscriminatorValue); } /** - * Create an instance of an openshift object. + * Create an instance of an openShift object. * @param body The request body * @return a {@link OpenShift} * @throws ODataError When receiving a 4XX or 5XX status code @@ -95,7 +95,7 @@ public OpenShift post(@jakarta.annotation.Nonnull final OpenShift body) { return post(body, null); } /** - * Create an instance of an openshift object. + * Create an instance of an openShift object. * @param body The request body * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link OpenShift} @@ -131,7 +131,7 @@ public RequestInformation toGetRequestInformation(@jakarta.annotation.Nullable f return requestInfo; } /** - * Create an instance of an openshift object. + * Create an instance of an openShift object. * @param body The request body * @return a {@link RequestInformation} */ @@ -140,7 +140,7 @@ public RequestInformation toPostRequestInformation(@jakarta.annotation.Nonnull f return toPostRequestInformation(body, null); } /** - * Create an instance of an openshift object. + * Create an instance of an openShift object. * @param body The request body * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} diff --git a/src/main/java/com/microsoft/graph/beta/generated/tenantrelationships/managedtenants/managementactions/item/microsoftgraphmanagedtenantsapply/MicrosoftGraphManagedTenantsApplyRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/tenantrelationships/managedtenants/managementactions/item/microsoftgraphmanagedtenantsapply/MicrosoftGraphManagedTenantsApplyRequestBuilder.java index 3871bdcb48b..6bc9d41bf80 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/tenantrelationships/managedtenants/managementactions/item/microsoftgraphmanagedtenantsapply/MicrosoftGraphManagedTenantsApplyRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/tenantrelationships/managedtenants/managementactions/item/microsoftgraphmanagedtenantsapply/MicrosoftGraphManagedTenantsApplyRequestBuilder.java @@ -36,7 +36,7 @@ public MicrosoftGraphManagedTenantsApplyRequestBuilder(@jakarta.annotation.Nonnu super(requestAdapter, "{+baseurl}/tenantRelationships/managedTenants/managementActions/{managementAction%2Did}/microsoft.graph.managedTenants.apply", rawUrl); } /** - * 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 * @return a {@link ManagementActionDeploymentStatus} * @throws ODataError When receiving a 4XX or 5XX status code @@ -47,7 +47,7 @@ public ManagementActionDeploymentStatus post(@jakarta.annotation.Nonnull final A return post(body, null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link ManagementActionDeploymentStatus} @@ -63,7 +63,7 @@ public ManagementActionDeploymentStatus post(@jakarta.annotation.Nonnull final A return this.requestAdapter.send(requestInfo, errorMapping, ManagementActionDeploymentStatus::createFromDiscriminatorValue); } /** - * 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 * @return a {@link RequestInformation} */ @@ -72,7 +72,7 @@ public RequestInformation toPostRequestInformation(@jakarta.annotation.Nonnull f return toPostRequestInformation(body, null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} diff --git a/src/main/java/com/microsoft/graph/beta/generated/tenantrelationships/multitenantorganization/MultiTenantOrganizationRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/tenantrelationships/multitenantorganization/MultiTenantOrganizationRequestBuilder.java index 87467d94fbc..2bfd9cbbefa 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/tenantrelationships/multitenantorganization/MultiTenantOrganizationRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/tenantrelationships/multitenantorganization/MultiTenantOrganizationRequestBuilder.java @@ -79,23 +79,23 @@ public MultiTenantOrganization get(@jakarta.annotation.Nullable final java.util. return this.requestAdapter.send(requestInfo, errorMapping, MultiTenantOrganization::createFromDiscriminatorValue); } /** - * 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 * @return a {@link MultiTenantOrganization} * @throws ODataError When receiving a 4XX or 5XX status code - * @see Find more info here + * @see Find more info here */ @jakarta.annotation.Nullable public MultiTenantOrganization patch(@jakarta.annotation.Nonnull final MultiTenantOrganization body) { return patch(body, null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link MultiTenantOrganization} * @throws ODataError When receiving a 4XX or 5XX status code - * @see Find more info here + * @see Find more info here */ @jakarta.annotation.Nullable public MultiTenantOrganization patch(@jakarta.annotation.Nonnull final MultiTenantOrganization body, @jakarta.annotation.Nullable final java.util.function.Consumer requestConfiguration) { @@ -126,7 +126,7 @@ public RequestInformation toGetRequestInformation(@jakarta.annotation.Nullable f return requestInfo; } /** - * 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 * @return a {@link RequestInformation} */ @@ -135,7 +135,7 @@ public RequestInformation toPatchRequestInformation(@jakarta.annotation.Nonnull return toPatchRequestInformation(body, null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} diff --git a/src/main/java/com/microsoft/graph/beta/generated/tenantrelationships/multitenantorganization/joinrequest/JoinRequestRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/tenantrelationships/multitenantorganization/joinrequest/JoinRequestRequestBuilder.java index 8cc4f40e206..933aba93d06 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/tenantrelationships/multitenantorganization/joinrequest/JoinRequestRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/tenantrelationships/multitenantorganization/joinrequest/JoinRequestRequestBuilder.java @@ -61,7 +61,7 @@ public MultiTenantOrganizationJoinRequestRecord get(@jakarta.annotation.Nullable return this.requestAdapter.send(requestInfo, errorMapping, MultiTenantOrganizationJoinRequestRecord::createFromDiscriminatorValue); } /** - * 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 * @return a {@link MultiTenantOrganizationJoinRequestRecord} * @throws ODataError When receiving a 4XX or 5XX status code @@ -72,7 +72,7 @@ public MultiTenantOrganizationJoinRequestRecord patch(@jakarta.annotation.Nonnul return patch(body, null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link MultiTenantOrganizationJoinRequestRecord} @@ -108,7 +108,7 @@ public RequestInformation toGetRequestInformation(@jakarta.annotation.Nullable f return requestInfo; } /** - * 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 * @return a {@link RequestInformation} */ @@ -117,7 +117,7 @@ public RequestInformation toPatchRequestInformation(@jakarta.annotation.Nonnull return toPatchRequestInformation(body, null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} diff --git a/src/main/java/com/microsoft/graph/beta/generated/users/item/authentication/hardwareoathmethods/HardwareOathMethodsRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/users/item/authentication/hardwareoathmethods/HardwareOathMethodsRequestBuilder.java index f189384f0f4..1a9ef7ba908 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/users/item/authentication/hardwareoathmethods/HardwareOathMethodsRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/users/item/authentication/hardwareoathmethods/HardwareOathMethodsRequestBuilder.java @@ -78,7 +78,7 @@ public HardwareOathMethodsRequestBuilder(@jakarta.annotation.Nonnull final Strin super(requestAdapter, "{+baseurl}/users/{user%2Did}/authentication/hardwareOathMethods{?%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * Get hardwareOathMethods from users + * The hardware OATH time-based one-time password (TOTP) devices assigned to a user for authentication. * @return a {@link HardwareOathAuthenticationMethodCollectionResponse} * @throws ODataError When receiving a 4XX or 5XX status code */ @@ -87,7 +87,7 @@ public HardwareOathAuthenticationMethodCollectionResponse get() { return get(null); } /** - * Get hardwareOathMethods from users + * The hardware OATH time-based one-time password (TOTP) devices assigned to a user for authentication. * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link HardwareOathAuthenticationMethodCollectionResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -125,7 +125,7 @@ public HardwareOathAuthenticationMethod post(@jakarta.annotation.Nonnull final H return this.requestAdapter.send(requestInfo, errorMapping, HardwareOathAuthenticationMethod::createFromDiscriminatorValue); } /** - * Get hardwareOathMethods from users + * The hardware OATH time-based one-time password (TOTP) devices assigned to a user for authentication. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -133,7 +133,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * Get hardwareOathMethods from users + * The hardware OATH time-based one-time password (TOTP) devices assigned to a user for authentication. * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -179,7 +179,7 @@ public HardwareOathMethodsRequestBuilder withUrl(@jakarta.annotation.Nonnull fin return new HardwareOathMethodsRequestBuilder(rawUrl, requestAdapter); } /** - * Get hardwareOathMethods from users + * The hardware OATH time-based one-time password (TOTP) devices assigned to a user for authentication. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/users/item/authentication/hardwareoathmethods/assignandactivate/AssignAndActivateRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/users/item/authentication/hardwareoathmethods/assignandactivate/AssignAndActivateRequestBuilder.java index 0a7e28d5e9a..94fb676ccb3 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/users/item/authentication/hardwareoathmethods/assignandactivate/AssignAndActivateRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/users/item/authentication/hardwareoathmethods/assignandactivate/AssignAndActivateRequestBuilder.java @@ -35,18 +35,20 @@ public AssignAndActivateRequestBuilder(@jakarta.annotation.Nonnull final String super(requestAdapter, "{+baseurl}/users/{user%2Did}/authentication/hardwareOathMethods/assignAndActivate", rawUrl); } /** - * 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 * @throws ODataError When receiving a 4XX or 5XX status code + * @see Find more info here */ public void post(@jakarta.annotation.Nonnull final AssignAndActivatePostRequestBody body) { post(body, null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @throws ODataError When receiving a 4XX or 5XX status code + * @see Find more info here */ public void post(@jakarta.annotation.Nonnull final AssignAndActivatePostRequestBody body, @jakarta.annotation.Nullable final java.util.function.Consumer requestConfiguration) { Objects.requireNonNull(body); @@ -56,7 +58,7 @@ public void post(@jakarta.annotation.Nonnull final AssignAndActivatePostRequestB this.requestAdapter.sendPrimitive(requestInfo, errorMapping, Void.class); } /** - * 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 * @return a {@link RequestInformation} */ @@ -65,7 +67,7 @@ public RequestInformation toPostRequestInformation(@jakarta.annotation.Nonnull f return toPostRequestInformation(body, null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} diff --git a/src/main/java/com/microsoft/graph/beta/generated/users/item/authentication/hardwareoathmethods/assignandactivatebyserialnumber/AssignAndActivateBySerialNumberRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/users/item/authentication/hardwareoathmethods/assignandactivatebyserialnumber/AssignAndActivateBySerialNumberRequestBuilder.java index 16e0edd9b35..3b2d93fe48f 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/users/item/authentication/hardwareoathmethods/assignandactivatebyserialnumber/AssignAndActivateBySerialNumberRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/users/item/authentication/hardwareoathmethods/assignandactivatebyserialnumber/AssignAndActivateBySerialNumberRequestBuilder.java @@ -35,18 +35,20 @@ public AssignAndActivateBySerialNumberRequestBuilder(@jakarta.annotation.Nonnull super(requestAdapter, "{+baseurl}/users/{user%2Did}/authentication/hardwareOathMethods/assignAndActivateBySerialNumber", rawUrl); } /** - * Invoke action assignAndActivateBySerialNumber + * Assign and activate a hardware token at the same time by hardware token serial number. * @param body The request body * @throws ODataError When receiving a 4XX or 5XX status code + * @see Find more info here */ public void post(@jakarta.annotation.Nonnull final AssignAndActivateBySerialNumberPostRequestBody body) { post(body, null); } /** - * Invoke action assignAndActivateBySerialNumber + * Assign and activate a hardware token at the same time by hardware token serial number. * @param body The request body * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @throws ODataError When receiving a 4XX or 5XX status code + * @see Find more info here */ public void post(@jakarta.annotation.Nonnull final AssignAndActivateBySerialNumberPostRequestBody body, @jakarta.annotation.Nullable final java.util.function.Consumer requestConfiguration) { Objects.requireNonNull(body); @@ -56,7 +58,7 @@ public void post(@jakarta.annotation.Nonnull final AssignAndActivateBySerialNumb this.requestAdapter.sendPrimitive(requestInfo, errorMapping, Void.class); } /** - * Invoke action assignAndActivateBySerialNumber + * Assign and activate a hardware token at the same time by hardware token serial number. * @param body The request body * @return a {@link RequestInformation} */ @@ -65,7 +67,7 @@ public RequestInformation toPostRequestInformation(@jakarta.annotation.Nonnull f return toPostRequestInformation(body, null); } /** - * Invoke action assignAndActivateBySerialNumber + * Assign and activate a hardware token at the same time by hardware token serial number. * @param body The request body * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} diff --git a/src/main/java/com/microsoft/graph/beta/generated/users/item/authentication/hardwareoathmethods/item/HardwareOathAuthenticationMethodItemRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/users/item/authentication/hardwareoathmethods/item/HardwareOathAuthenticationMethodItemRequestBuilder.java index 58c7acd7d66..8b2b3f2d8f9 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/users/item/authentication/hardwareoathmethods/item/HardwareOathAuthenticationMethodItemRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/users/item/authentication/hardwareoathmethods/item/HardwareOathAuthenticationMethodItemRequestBuilder.java @@ -82,7 +82,7 @@ public void delete(@jakarta.annotation.Nullable final java.util.function.Consume this.requestAdapter.sendPrimitive(requestInfo, errorMapping, Void.class); } /** - * Get hardwareOathMethods from users + * The hardware OATH time-based one-time password (TOTP) devices assigned to a user for authentication. * @return a {@link HardwareOathAuthenticationMethod} * @throws ODataError When receiving a 4XX or 5XX status code */ @@ -91,7 +91,7 @@ public HardwareOathAuthenticationMethod get() { return get(null); } /** - * Get hardwareOathMethods from users + * The hardware OATH time-based one-time password (TOTP) devices assigned to a user for authentication. * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link HardwareOathAuthenticationMethod} * @throws ODataError When receiving a 4XX or 5XX status code @@ -124,7 +124,7 @@ public RequestInformation toDeleteRequestInformation(@jakarta.annotation.Nullabl return requestInfo; } /** - * Get hardwareOathMethods from users + * The hardware OATH time-based one-time password (TOTP) devices assigned to a user for authentication. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -132,7 +132,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * Get hardwareOathMethods from users + * The hardware OATH time-based one-time password (TOTP) devices assigned to a user for authentication. * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -160,7 +160,7 @@ public HardwareOathAuthenticationMethodItemRequestBuilder withUrl(@jakarta.annot public class DeleteRequestConfiguration extends BaseRequestConfiguration { } /** - * Get hardwareOathMethods from users + * The hardware OATH time-based one-time password (TOTP) devices assigned to a user for authentication. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/users/item/authentication/hardwareoathmethods/item/activate/ActivateRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/users/item/authentication/hardwareoathmethods/item/activate/ActivateRequestBuilder.java index ba8330cfdb4..f5219f7e9c8 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/users/item/authentication/hardwareoathmethods/item/activate/ActivateRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/users/item/authentication/hardwareoathmethods/item/activate/ActivateRequestBuilder.java @@ -35,18 +35,20 @@ public ActivateRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @ super(requestAdapter, "{+baseurl}/users/{user%2Did}/authentication/hardwareOathMethods/{hardwareOathAuthenticationMethod%2Did}/activate", rawUrl); } /** - * 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 * @throws ODataError When receiving a 4XX or 5XX status code + * @see Find more info here */ public void post(@jakarta.annotation.Nonnull final ActivatePostRequestBody body) { post(body, null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @throws ODataError When receiving a 4XX or 5XX status code + * @see Find more info here */ public void post(@jakarta.annotation.Nonnull final ActivatePostRequestBody body, @jakarta.annotation.Nullable final java.util.function.Consumer requestConfiguration) { Objects.requireNonNull(body); @@ -56,7 +58,7 @@ public void post(@jakarta.annotation.Nonnull final ActivatePostRequestBody body, this.requestAdapter.sendPrimitive(requestInfo, errorMapping, Void.class); } /** - * 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 * @return a {@link RequestInformation} */ @@ -65,7 +67,7 @@ public RequestInformation toPostRequestInformation(@jakarta.annotation.Nonnull f return toPostRequestInformation(body, null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} diff --git a/src/main/java/com/microsoft/graph/beta/generated/users/item/authentication/hardwareoathmethods/item/deactivate/DeactivateRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/users/item/authentication/hardwareoathmethods/item/deactivate/DeactivateRequestBuilder.java index 0e96565b577..a5803e030a1 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/users/item/authentication/hardwareoathmethods/item/deactivate/DeactivateRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/users/item/authentication/hardwareoathmethods/item/deactivate/DeactivateRequestBuilder.java @@ -35,16 +35,18 @@ public DeactivateRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, super(requestAdapter, "{+baseurl}/users/{user%2Did}/authentication/hardwareOathMethods/{hardwareOathAuthenticationMethod%2Did}/deactivate", rawUrl); } /** - * Invoke action deactivate + * Deactive a hardware OATH token. It remains assigned to a user. * @throws ODataError When receiving a 4XX or 5XX status code + * @see Find more info here */ public void post() { post(null); } /** - * Invoke action deactivate + * Deactive a hardware OATH token. It remains assigned to a user. * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @throws ODataError When receiving a 4XX or 5XX status code + * @see Find more info here */ public void post(@jakarta.annotation.Nullable final java.util.function.Consumer requestConfiguration) { final RequestInformation requestInfo = toPostRequestInformation(requestConfiguration); @@ -53,7 +55,7 @@ public void post(@jakarta.annotation.Nullable final java.util.function.Consumer< this.requestAdapter.sendPrimitive(requestInfo, errorMapping, Void.class); } /** - * Invoke action deactivate + * Deactive a hardware OATH token. It remains assigned to a user. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -61,7 +63,7 @@ public RequestInformation toPostRequestInformation() { return toPostRequestInformation(null); } /** - * Invoke action deactivate + * Deactive a hardware OATH token. It remains assigned to a user. * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ diff --git a/src/main/java/com/microsoft/graph/beta/generated/users/item/authentication/hardwareoathmethods/item/device/DeviceRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/users/item/authentication/hardwareoathmethods/item/device/DeviceRequestBuilder.java index a426a9c5e44..e6eadc377b6 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/users/item/authentication/hardwareoathmethods/item/device/DeviceRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/users/item/authentication/hardwareoathmethods/item/device/DeviceRequestBuilder.java @@ -73,7 +73,7 @@ public void delete(@jakarta.annotation.Nullable final java.util.function.Consume this.requestAdapter.sendPrimitive(requestInfo, errorMapping, Void.class); } /** - * Get device from users + * Exposes the hardware OATH method in the directory. * @return a {@link HardwareOathTokenAuthenticationMethodDevice} * @throws ODataError When receiving a 4XX or 5XX status code */ @@ -82,7 +82,7 @@ public HardwareOathTokenAuthenticationMethodDevice get() { return get(null); } /** - * Get device from users + * Exposes the hardware OATH method in the directory. * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link HardwareOathTokenAuthenticationMethodDevice} * @throws ODataError When receiving a 4XX or 5XX status code @@ -140,7 +140,7 @@ public RequestInformation toDeleteRequestInformation(@jakarta.annotation.Nullabl return requestInfo; } /** - * Get device from users + * Exposes the hardware OATH method in the directory. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -148,7 +148,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * Get device from users + * Exposes the hardware OATH method in the directory. * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -200,7 +200,7 @@ public DeviceRequestBuilder withUrl(@jakarta.annotation.Nonnull final String raw public class DeleteRequestConfiguration extends BaseRequestConfiguration { } /** - * Get device from users + * Exposes the hardware OATH method in the directory. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/users/item/authentication/hardwareoathmethods/item/device/assignto/AssignToRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/users/item/authentication/hardwareoathmethods/item/device/assignto/AssignToRequestBuilder.java index 438e1a9a32d..ba97ce8bbd6 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/users/item/authentication/hardwareoathmethods/item/device/assignto/AssignToRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/users/item/authentication/hardwareoathmethods/item/device/assignto/AssignToRequestBuilder.java @@ -55,7 +55,7 @@ public AssignToRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @ super(requestAdapter, "{+baseurl}/users/{user%2Did}/authentication/hardwareOathMethods/{hardwareOathAuthenticationMethod%2Did}/device/assignTo{?%24expand,%24select}", rawUrl); } /** - * Get assignTo from users + * Assign the hardware OATH token to a user. * @return a {@link User} * @throws ODataError When receiving a 4XX or 5XX status code */ @@ -64,7 +64,7 @@ public User get() { return get(null); } /** - * Get assignTo from users + * Assign the hardware OATH token to a user. * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link User} * @throws ODataError When receiving a 4XX or 5XX status code @@ -77,7 +77,7 @@ public User get(@jakarta.annotation.Nullable final java.util.function.ConsumerFind more info here @@ -46,7 +46,7 @@ public DeltaGetResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -60,7 +60,7 @@ public DeltaGetResponse get(@jakarta.annotation.Nullable final java.util.functio return this.requestAdapter.send(requestInfo, errorMapping, DeltaGetResponse::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -68,7 +68,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -90,7 +90,7 @@ public DeltaRequestBuilder withUrl(@jakarta.annotation.Nonnull final String rawU return new DeltaRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/users/item/calendar/calendarview/item/exceptionoccurrences/delta/DeltaRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/users/item/calendar/calendarview/item/exceptionoccurrences/delta/DeltaRequestBuilder.java index fc96efaa33b..a51459e5d0f 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/users/item/calendar/calendarview/item/exceptionoccurrences/delta/DeltaRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/users/item/calendar/calendarview/item/exceptionoccurrences/delta/DeltaRequestBuilder.java @@ -36,7 +36,7 @@ public DeltaRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @jak super(requestAdapter, "{+baseurl}/users/{user%2Did}/calendar/calendarView/{event%2Did}/exceptionOccurrences/delta()?endDateTime={endDateTime}&startDateTime={startDateTime}{&%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * 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. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code * @see Find more info here @@ -46,7 +46,7 @@ public DeltaGetResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -60,7 +60,7 @@ public DeltaGetResponse get(@jakarta.annotation.Nullable final java.util.functio return this.requestAdapter.send(requestInfo, errorMapping, DeltaGetResponse::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -68,7 +68,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -90,7 +90,7 @@ public DeltaRequestBuilder withUrl(@jakarta.annotation.Nonnull final String rawU return new DeltaRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/users/item/calendar/calendarview/item/exceptionoccurrences/item/instances/delta/DeltaRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/users/item/calendar/calendarview/item/exceptionoccurrences/item/instances/delta/DeltaRequestBuilder.java index 9fd60b2c178..b8d716f4bb9 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/users/item/calendar/calendarview/item/exceptionoccurrences/item/instances/delta/DeltaRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/users/item/calendar/calendarview/item/exceptionoccurrences/item/instances/delta/DeltaRequestBuilder.java @@ -36,7 +36,7 @@ public DeltaRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @jak super(requestAdapter, "{+baseurl}/users/{user%2Did}/calendar/calendarView/{event%2Did}/exceptionOccurrences/{event%2Did1}/instances/delta()?endDateTime={endDateTime}&startDateTime={startDateTime}{&%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * 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. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code * @see Find more info here @@ -46,7 +46,7 @@ public DeltaGetResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -60,7 +60,7 @@ public DeltaGetResponse get(@jakarta.annotation.Nullable final java.util.functio return this.requestAdapter.send(requestInfo, errorMapping, DeltaGetResponse::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -68,7 +68,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -90,7 +90,7 @@ public DeltaRequestBuilder withUrl(@jakarta.annotation.Nonnull final String rawU return new DeltaRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/users/item/calendar/calendarview/item/instances/delta/DeltaRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/users/item/calendar/calendarview/item/instances/delta/DeltaRequestBuilder.java index 89f4081fe7e..281afa79d47 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/users/item/calendar/calendarview/item/instances/delta/DeltaRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/users/item/calendar/calendarview/item/instances/delta/DeltaRequestBuilder.java @@ -36,7 +36,7 @@ public DeltaRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @jak super(requestAdapter, "{+baseurl}/users/{user%2Did}/calendar/calendarView/{event%2Did}/instances/delta()?endDateTime={endDateTime}&startDateTime={startDateTime}{&%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * 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. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code * @see Find more info here @@ -46,7 +46,7 @@ public DeltaGetResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -60,7 +60,7 @@ public DeltaGetResponse get(@jakarta.annotation.Nullable final java.util.functio return this.requestAdapter.send(requestInfo, errorMapping, DeltaGetResponse::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -68,7 +68,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -90,7 +90,7 @@ public DeltaRequestBuilder withUrl(@jakarta.annotation.Nonnull final String rawU return new DeltaRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/users/item/calendar/calendarview/item/instances/item/exceptionoccurrences/delta/DeltaRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/users/item/calendar/calendarview/item/instances/item/exceptionoccurrences/delta/DeltaRequestBuilder.java index 079f955f439..00a9a42c114 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/users/item/calendar/calendarview/item/instances/item/exceptionoccurrences/delta/DeltaRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/users/item/calendar/calendarview/item/instances/item/exceptionoccurrences/delta/DeltaRequestBuilder.java @@ -36,7 +36,7 @@ public DeltaRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @jak super(requestAdapter, "{+baseurl}/users/{user%2Did}/calendar/calendarView/{event%2Did}/instances/{event%2Did1}/exceptionOccurrences/delta()?endDateTime={endDateTime}&startDateTime={startDateTime}{&%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * 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. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code * @see Find more info here @@ -46,7 +46,7 @@ public DeltaGetResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -60,7 +60,7 @@ public DeltaGetResponse get(@jakarta.annotation.Nullable final java.util.functio return this.requestAdapter.send(requestInfo, errorMapping, DeltaGetResponse::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -68,7 +68,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -90,7 +90,7 @@ public DeltaRequestBuilder withUrl(@jakarta.annotation.Nonnull final String rawU return new DeltaRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/users/item/calendar/events/delta/DeltaRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/users/item/calendar/events/delta/DeltaRequestBuilder.java index fdea1598a0b..89500737ebf 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/users/item/calendar/events/delta/DeltaRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/users/item/calendar/events/delta/DeltaRequestBuilder.java @@ -36,7 +36,7 @@ public DeltaRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @jak super(requestAdapter, "{+baseurl}/users/{user%2Did}/calendar/events/delta()?endDateTime={endDateTime}&startDateTime={startDateTime}{&%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * 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. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code * @see Find more info here @@ -46,7 +46,7 @@ public DeltaGetResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -60,7 +60,7 @@ public DeltaGetResponse get(@jakarta.annotation.Nullable final java.util.functio return this.requestAdapter.send(requestInfo, errorMapping, DeltaGetResponse::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -68,7 +68,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -90,7 +90,7 @@ public DeltaRequestBuilder withUrl(@jakarta.annotation.Nonnull final String rawU return new DeltaRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/users/item/calendar/events/item/exceptionoccurrences/delta/DeltaRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/users/item/calendar/events/item/exceptionoccurrences/delta/DeltaRequestBuilder.java index 39ca4aa7d26..c5fd04845e2 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/users/item/calendar/events/item/exceptionoccurrences/delta/DeltaRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/users/item/calendar/events/item/exceptionoccurrences/delta/DeltaRequestBuilder.java @@ -36,7 +36,7 @@ public DeltaRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @jak super(requestAdapter, "{+baseurl}/users/{user%2Did}/calendar/events/{event%2Did}/exceptionOccurrences/delta()?endDateTime={endDateTime}&startDateTime={startDateTime}{&%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * 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. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code * @see Find more info here @@ -46,7 +46,7 @@ public DeltaGetResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -60,7 +60,7 @@ public DeltaGetResponse get(@jakarta.annotation.Nullable final java.util.functio return this.requestAdapter.send(requestInfo, errorMapping, DeltaGetResponse::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -68,7 +68,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -90,7 +90,7 @@ public DeltaRequestBuilder withUrl(@jakarta.annotation.Nonnull final String rawU return new DeltaRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/users/item/calendar/events/item/exceptionoccurrences/item/instances/delta/DeltaRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/users/item/calendar/events/item/exceptionoccurrences/item/instances/delta/DeltaRequestBuilder.java index d430aa8cda8..fd9b2cc23bd 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/users/item/calendar/events/item/exceptionoccurrences/item/instances/delta/DeltaRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/users/item/calendar/events/item/exceptionoccurrences/item/instances/delta/DeltaRequestBuilder.java @@ -36,7 +36,7 @@ public DeltaRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @jak super(requestAdapter, "{+baseurl}/users/{user%2Did}/calendar/events/{event%2Did}/exceptionOccurrences/{event%2Did1}/instances/delta()?endDateTime={endDateTime}&startDateTime={startDateTime}{&%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * 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. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code * @see Find more info here @@ -46,7 +46,7 @@ public DeltaGetResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -60,7 +60,7 @@ public DeltaGetResponse get(@jakarta.annotation.Nullable final java.util.functio return this.requestAdapter.send(requestInfo, errorMapping, DeltaGetResponse::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -68,7 +68,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -90,7 +90,7 @@ public DeltaRequestBuilder withUrl(@jakarta.annotation.Nonnull final String rawU return new DeltaRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/users/item/calendar/events/item/instances/delta/DeltaRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/users/item/calendar/events/item/instances/delta/DeltaRequestBuilder.java index c52da4a029a..822eff08253 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/users/item/calendar/events/item/instances/delta/DeltaRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/users/item/calendar/events/item/instances/delta/DeltaRequestBuilder.java @@ -36,7 +36,7 @@ public DeltaRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @jak super(requestAdapter, "{+baseurl}/users/{user%2Did}/calendar/events/{event%2Did}/instances/delta()?endDateTime={endDateTime}&startDateTime={startDateTime}{&%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * 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. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code * @see Find more info here @@ -46,7 +46,7 @@ public DeltaGetResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -60,7 +60,7 @@ public DeltaGetResponse get(@jakarta.annotation.Nullable final java.util.functio return this.requestAdapter.send(requestInfo, errorMapping, DeltaGetResponse::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -68,7 +68,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -90,7 +90,7 @@ public DeltaRequestBuilder withUrl(@jakarta.annotation.Nonnull final String rawU return new DeltaRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/users/item/calendar/events/item/instances/item/exceptionoccurrences/delta/DeltaRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/users/item/calendar/events/item/instances/item/exceptionoccurrences/delta/DeltaRequestBuilder.java index a2b30248a4d..cbf267cfd17 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/users/item/calendar/events/item/instances/item/exceptionoccurrences/delta/DeltaRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/users/item/calendar/events/item/instances/item/exceptionoccurrences/delta/DeltaRequestBuilder.java @@ -36,7 +36,7 @@ public DeltaRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @jak super(requestAdapter, "{+baseurl}/users/{user%2Did}/calendar/events/{event%2Did}/instances/{event%2Did1}/exceptionOccurrences/delta()?endDateTime={endDateTime}&startDateTime={startDateTime}{&%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * 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. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code * @see Find more info here @@ -46,7 +46,7 @@ public DeltaGetResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -60,7 +60,7 @@ public DeltaGetResponse get(@jakarta.annotation.Nullable final java.util.functio return this.requestAdapter.send(requestInfo, errorMapping, DeltaGetResponse::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -68,7 +68,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -90,7 +90,7 @@ public DeltaRequestBuilder withUrl(@jakarta.annotation.Nonnull final String rawU return new DeltaRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/users/item/calendargroups/item/calendars/item/calendarview/delta/DeltaRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/users/item/calendargroups/item/calendars/item/calendarview/delta/DeltaRequestBuilder.java index 89ff0af0a34..2044e027c2e 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/users/item/calendargroups/item/calendars/item/calendarview/delta/DeltaRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/users/item/calendargroups/item/calendars/item/calendarview/delta/DeltaRequestBuilder.java @@ -36,7 +36,7 @@ public DeltaRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @jak super(requestAdapter, "{+baseurl}/users/{user%2Did}/calendarGroups/{calendarGroup%2Did}/calendars/{calendar%2Did}/calendarView/delta()?endDateTime={endDateTime}&startDateTime={startDateTime}{&%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * 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. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code * @see Find more info here @@ -46,7 +46,7 @@ public DeltaGetResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -60,7 +60,7 @@ public DeltaGetResponse get(@jakarta.annotation.Nullable final java.util.functio return this.requestAdapter.send(requestInfo, errorMapping, DeltaGetResponse::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -68,7 +68,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -90,7 +90,7 @@ public DeltaRequestBuilder withUrl(@jakarta.annotation.Nonnull final String rawU return new DeltaRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/users/item/calendargroups/item/calendars/item/calendarview/item/exceptionoccurrences/delta/DeltaRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/users/item/calendargroups/item/calendars/item/calendarview/item/exceptionoccurrences/delta/DeltaRequestBuilder.java index ffe24342364..6a5571794cd 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/users/item/calendargroups/item/calendars/item/calendarview/item/exceptionoccurrences/delta/DeltaRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/users/item/calendargroups/item/calendars/item/calendarview/item/exceptionoccurrences/delta/DeltaRequestBuilder.java @@ -36,7 +36,7 @@ public DeltaRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @jak super(requestAdapter, "{+baseurl}/users/{user%2Did}/calendarGroups/{calendarGroup%2Did}/calendars/{calendar%2Did}/calendarView/{event%2Did}/exceptionOccurrences/delta()?endDateTime={endDateTime}&startDateTime={startDateTime}{&%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * 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. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code * @see Find more info here @@ -46,7 +46,7 @@ public DeltaGetResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -60,7 +60,7 @@ public DeltaGetResponse get(@jakarta.annotation.Nullable final java.util.functio return this.requestAdapter.send(requestInfo, errorMapping, DeltaGetResponse::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -68,7 +68,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -90,7 +90,7 @@ public DeltaRequestBuilder withUrl(@jakarta.annotation.Nonnull final String rawU return new DeltaRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/users/item/calendargroups/item/calendars/item/calendarview/item/exceptionoccurrences/item/instances/delta/DeltaRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/users/item/calendargroups/item/calendars/item/calendarview/item/exceptionoccurrences/item/instances/delta/DeltaRequestBuilder.java index 01165d96873..c358d4fd2b5 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/users/item/calendargroups/item/calendars/item/calendarview/item/exceptionoccurrences/item/instances/delta/DeltaRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/users/item/calendargroups/item/calendars/item/calendarview/item/exceptionoccurrences/item/instances/delta/DeltaRequestBuilder.java @@ -36,7 +36,7 @@ public DeltaRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @jak super(requestAdapter, "{+baseurl}/users/{user%2Did}/calendarGroups/{calendarGroup%2Did}/calendars/{calendar%2Did}/calendarView/{event%2Did}/exceptionOccurrences/{event%2Did1}/instances/delta()?endDateTime={endDateTime}&startDateTime={startDateTime}{&%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * 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. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code * @see Find more info here @@ -46,7 +46,7 @@ public DeltaGetResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -60,7 +60,7 @@ public DeltaGetResponse get(@jakarta.annotation.Nullable final java.util.functio return this.requestAdapter.send(requestInfo, errorMapping, DeltaGetResponse::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -68,7 +68,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -90,7 +90,7 @@ public DeltaRequestBuilder withUrl(@jakarta.annotation.Nonnull final String rawU return new DeltaRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/users/item/calendargroups/item/calendars/item/calendarview/item/instances/delta/DeltaRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/users/item/calendargroups/item/calendars/item/calendarview/item/instances/delta/DeltaRequestBuilder.java index 3e9c95dcdcf..23d8854fd2a 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/users/item/calendargroups/item/calendars/item/calendarview/item/instances/delta/DeltaRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/users/item/calendargroups/item/calendars/item/calendarview/item/instances/delta/DeltaRequestBuilder.java @@ -36,7 +36,7 @@ public DeltaRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @jak super(requestAdapter, "{+baseurl}/users/{user%2Did}/calendarGroups/{calendarGroup%2Did}/calendars/{calendar%2Did}/calendarView/{event%2Did}/instances/delta()?endDateTime={endDateTime}&startDateTime={startDateTime}{&%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * 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. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code * @see Find more info here @@ -46,7 +46,7 @@ public DeltaGetResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -60,7 +60,7 @@ public DeltaGetResponse get(@jakarta.annotation.Nullable final java.util.functio return this.requestAdapter.send(requestInfo, errorMapping, DeltaGetResponse::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -68,7 +68,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -90,7 +90,7 @@ public DeltaRequestBuilder withUrl(@jakarta.annotation.Nonnull final String rawU return new DeltaRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/users/item/calendargroups/item/calendars/item/calendarview/item/instances/item/exceptionoccurrences/delta/DeltaRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/users/item/calendargroups/item/calendars/item/calendarview/item/instances/item/exceptionoccurrences/delta/DeltaRequestBuilder.java index c5a1fc9be34..7f79bdf2e03 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/users/item/calendargroups/item/calendars/item/calendarview/item/instances/item/exceptionoccurrences/delta/DeltaRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/users/item/calendargroups/item/calendars/item/calendarview/item/instances/item/exceptionoccurrences/delta/DeltaRequestBuilder.java @@ -36,7 +36,7 @@ public DeltaRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @jak super(requestAdapter, "{+baseurl}/users/{user%2Did}/calendarGroups/{calendarGroup%2Did}/calendars/{calendar%2Did}/calendarView/{event%2Did}/instances/{event%2Did1}/exceptionOccurrences/delta()?endDateTime={endDateTime}&startDateTime={startDateTime}{&%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * 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. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code * @see Find more info here @@ -46,7 +46,7 @@ public DeltaGetResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -60,7 +60,7 @@ public DeltaGetResponse get(@jakarta.annotation.Nullable final java.util.functio return this.requestAdapter.send(requestInfo, errorMapping, DeltaGetResponse::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -68,7 +68,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -90,7 +90,7 @@ public DeltaRequestBuilder withUrl(@jakarta.annotation.Nonnull final String rawU return new DeltaRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/users/item/calendargroups/item/calendars/item/events/delta/DeltaRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/users/item/calendargroups/item/calendars/item/events/delta/DeltaRequestBuilder.java index 4f575a20549..827bc4abe51 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/users/item/calendargroups/item/calendars/item/events/delta/DeltaRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/users/item/calendargroups/item/calendars/item/events/delta/DeltaRequestBuilder.java @@ -36,7 +36,7 @@ public DeltaRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @jak super(requestAdapter, "{+baseurl}/users/{user%2Did}/calendarGroups/{calendarGroup%2Did}/calendars/{calendar%2Did}/events/delta()?endDateTime={endDateTime}&startDateTime={startDateTime}{&%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * 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. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code * @see Find more info here @@ -46,7 +46,7 @@ public DeltaGetResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -60,7 +60,7 @@ public DeltaGetResponse get(@jakarta.annotation.Nullable final java.util.functio return this.requestAdapter.send(requestInfo, errorMapping, DeltaGetResponse::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -68,7 +68,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -90,7 +90,7 @@ public DeltaRequestBuilder withUrl(@jakarta.annotation.Nonnull final String rawU return new DeltaRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/users/item/calendargroups/item/calendars/item/events/item/exceptionoccurrences/delta/DeltaRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/users/item/calendargroups/item/calendars/item/events/item/exceptionoccurrences/delta/DeltaRequestBuilder.java index eabc288ec32..69ba1a275fe 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/users/item/calendargroups/item/calendars/item/events/item/exceptionoccurrences/delta/DeltaRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/users/item/calendargroups/item/calendars/item/events/item/exceptionoccurrences/delta/DeltaRequestBuilder.java @@ -36,7 +36,7 @@ public DeltaRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @jak super(requestAdapter, "{+baseurl}/users/{user%2Did}/calendarGroups/{calendarGroup%2Did}/calendars/{calendar%2Did}/events/{event%2Did}/exceptionOccurrences/delta()?endDateTime={endDateTime}&startDateTime={startDateTime}{&%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * 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. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code * @see Find more info here @@ -46,7 +46,7 @@ public DeltaGetResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -60,7 +60,7 @@ public DeltaGetResponse get(@jakarta.annotation.Nullable final java.util.functio return this.requestAdapter.send(requestInfo, errorMapping, DeltaGetResponse::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -68,7 +68,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -90,7 +90,7 @@ public DeltaRequestBuilder withUrl(@jakarta.annotation.Nonnull final String rawU return new DeltaRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/users/item/calendargroups/item/calendars/item/events/item/exceptionoccurrences/item/instances/delta/DeltaRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/users/item/calendargroups/item/calendars/item/events/item/exceptionoccurrences/item/instances/delta/DeltaRequestBuilder.java index b94de0528e4..e2565ce1b43 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/users/item/calendargroups/item/calendars/item/events/item/exceptionoccurrences/item/instances/delta/DeltaRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/users/item/calendargroups/item/calendars/item/events/item/exceptionoccurrences/item/instances/delta/DeltaRequestBuilder.java @@ -36,7 +36,7 @@ public DeltaRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @jak super(requestAdapter, "{+baseurl}/users/{user%2Did}/calendarGroups/{calendarGroup%2Did}/calendars/{calendar%2Did}/events/{event%2Did}/exceptionOccurrences/{event%2Did1}/instances/delta()?endDateTime={endDateTime}&startDateTime={startDateTime}{&%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * 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. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code * @see Find more info here @@ -46,7 +46,7 @@ public DeltaGetResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -60,7 +60,7 @@ public DeltaGetResponse get(@jakarta.annotation.Nullable final java.util.functio return this.requestAdapter.send(requestInfo, errorMapping, DeltaGetResponse::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -68,7 +68,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -90,7 +90,7 @@ public DeltaRequestBuilder withUrl(@jakarta.annotation.Nonnull final String rawU return new DeltaRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/users/item/calendargroups/item/calendars/item/events/item/instances/delta/DeltaRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/users/item/calendargroups/item/calendars/item/events/item/instances/delta/DeltaRequestBuilder.java index 170b3db9dbe..b5035b2c4a4 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/users/item/calendargroups/item/calendars/item/events/item/instances/delta/DeltaRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/users/item/calendargroups/item/calendars/item/events/item/instances/delta/DeltaRequestBuilder.java @@ -36,7 +36,7 @@ public DeltaRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @jak super(requestAdapter, "{+baseurl}/users/{user%2Did}/calendarGroups/{calendarGroup%2Did}/calendars/{calendar%2Did}/events/{event%2Did}/instances/delta()?endDateTime={endDateTime}&startDateTime={startDateTime}{&%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * 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. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code * @see Find more info here @@ -46,7 +46,7 @@ public DeltaGetResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -60,7 +60,7 @@ public DeltaGetResponse get(@jakarta.annotation.Nullable final java.util.functio return this.requestAdapter.send(requestInfo, errorMapping, DeltaGetResponse::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -68,7 +68,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -90,7 +90,7 @@ public DeltaRequestBuilder withUrl(@jakarta.annotation.Nonnull final String rawU return new DeltaRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/users/item/calendargroups/item/calendars/item/events/item/instances/item/exceptionoccurrences/delta/DeltaRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/users/item/calendargroups/item/calendars/item/events/item/instances/item/exceptionoccurrences/delta/DeltaRequestBuilder.java index 326ee17a55d..fd25de7debe 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/users/item/calendargroups/item/calendars/item/events/item/instances/item/exceptionoccurrences/delta/DeltaRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/users/item/calendargroups/item/calendars/item/events/item/instances/item/exceptionoccurrences/delta/DeltaRequestBuilder.java @@ -36,7 +36,7 @@ public DeltaRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @jak super(requestAdapter, "{+baseurl}/users/{user%2Did}/calendarGroups/{calendarGroup%2Did}/calendars/{calendar%2Did}/events/{event%2Did}/instances/{event%2Did1}/exceptionOccurrences/delta()?endDateTime={endDateTime}&startDateTime={startDateTime}{&%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * 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. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code * @see Find more info here @@ -46,7 +46,7 @@ public DeltaGetResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -60,7 +60,7 @@ public DeltaGetResponse get(@jakarta.annotation.Nullable final java.util.functio return this.requestAdapter.send(requestInfo, errorMapping, DeltaGetResponse::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -68,7 +68,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -90,7 +90,7 @@ public DeltaRequestBuilder withUrl(@jakarta.annotation.Nonnull final String rawU return new DeltaRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/users/item/calendars/item/calendarview/delta/DeltaRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/users/item/calendars/item/calendarview/delta/DeltaRequestBuilder.java index 207bd27fe1f..04f5d39c192 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/users/item/calendars/item/calendarview/delta/DeltaRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/users/item/calendars/item/calendarview/delta/DeltaRequestBuilder.java @@ -36,7 +36,7 @@ public DeltaRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @jak super(requestAdapter, "{+baseurl}/users/{user%2Did}/calendars/{calendar%2Did}/calendarView/delta()?endDateTime={endDateTime}&startDateTime={startDateTime}{&%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * 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. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code * @see Find more info here @@ -46,7 +46,7 @@ public DeltaGetResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -60,7 +60,7 @@ public DeltaGetResponse get(@jakarta.annotation.Nullable final java.util.functio return this.requestAdapter.send(requestInfo, errorMapping, DeltaGetResponse::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -68,7 +68,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -90,7 +90,7 @@ public DeltaRequestBuilder withUrl(@jakarta.annotation.Nonnull final String rawU return new DeltaRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/users/item/calendars/item/calendarview/item/exceptionoccurrences/delta/DeltaRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/users/item/calendars/item/calendarview/item/exceptionoccurrences/delta/DeltaRequestBuilder.java index a76eca48054..963243b0226 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/users/item/calendars/item/calendarview/item/exceptionoccurrences/delta/DeltaRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/users/item/calendars/item/calendarview/item/exceptionoccurrences/delta/DeltaRequestBuilder.java @@ -36,7 +36,7 @@ public DeltaRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @jak super(requestAdapter, "{+baseurl}/users/{user%2Did}/calendars/{calendar%2Did}/calendarView/{event%2Did}/exceptionOccurrences/delta()?endDateTime={endDateTime}&startDateTime={startDateTime}{&%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * 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. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code * @see Find more info here @@ -46,7 +46,7 @@ public DeltaGetResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -60,7 +60,7 @@ public DeltaGetResponse get(@jakarta.annotation.Nullable final java.util.functio return this.requestAdapter.send(requestInfo, errorMapping, DeltaGetResponse::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -68,7 +68,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -90,7 +90,7 @@ public DeltaRequestBuilder withUrl(@jakarta.annotation.Nonnull final String rawU return new DeltaRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/users/item/calendars/item/calendarview/item/exceptionoccurrences/item/instances/delta/DeltaRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/users/item/calendars/item/calendarview/item/exceptionoccurrences/item/instances/delta/DeltaRequestBuilder.java index 4701cec2af7..9364e036789 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/users/item/calendars/item/calendarview/item/exceptionoccurrences/item/instances/delta/DeltaRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/users/item/calendars/item/calendarview/item/exceptionoccurrences/item/instances/delta/DeltaRequestBuilder.java @@ -36,7 +36,7 @@ public DeltaRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @jak super(requestAdapter, "{+baseurl}/users/{user%2Did}/calendars/{calendar%2Did}/calendarView/{event%2Did}/exceptionOccurrences/{event%2Did1}/instances/delta()?endDateTime={endDateTime}&startDateTime={startDateTime}{&%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * 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. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code * @see Find more info here @@ -46,7 +46,7 @@ public DeltaGetResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -60,7 +60,7 @@ public DeltaGetResponse get(@jakarta.annotation.Nullable final java.util.functio return this.requestAdapter.send(requestInfo, errorMapping, DeltaGetResponse::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -68,7 +68,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -90,7 +90,7 @@ public DeltaRequestBuilder withUrl(@jakarta.annotation.Nonnull final String rawU return new DeltaRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/users/item/calendars/item/calendarview/item/instances/delta/DeltaRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/users/item/calendars/item/calendarview/item/instances/delta/DeltaRequestBuilder.java index 7984c6f7f57..4145b5d6122 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/users/item/calendars/item/calendarview/item/instances/delta/DeltaRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/users/item/calendars/item/calendarview/item/instances/delta/DeltaRequestBuilder.java @@ -36,7 +36,7 @@ public DeltaRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @jak super(requestAdapter, "{+baseurl}/users/{user%2Did}/calendars/{calendar%2Did}/calendarView/{event%2Did}/instances/delta()?endDateTime={endDateTime}&startDateTime={startDateTime}{&%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * 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. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code * @see Find more info here @@ -46,7 +46,7 @@ public DeltaGetResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -60,7 +60,7 @@ public DeltaGetResponse get(@jakarta.annotation.Nullable final java.util.functio return this.requestAdapter.send(requestInfo, errorMapping, DeltaGetResponse::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -68,7 +68,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -90,7 +90,7 @@ public DeltaRequestBuilder withUrl(@jakarta.annotation.Nonnull final String rawU return new DeltaRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/users/item/calendars/item/calendarview/item/instances/item/exceptionoccurrences/delta/DeltaRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/users/item/calendars/item/calendarview/item/instances/item/exceptionoccurrences/delta/DeltaRequestBuilder.java index 99b9883262b..42e6ac33944 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/users/item/calendars/item/calendarview/item/instances/item/exceptionoccurrences/delta/DeltaRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/users/item/calendars/item/calendarview/item/instances/item/exceptionoccurrences/delta/DeltaRequestBuilder.java @@ -36,7 +36,7 @@ public DeltaRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @jak super(requestAdapter, "{+baseurl}/users/{user%2Did}/calendars/{calendar%2Did}/calendarView/{event%2Did}/instances/{event%2Did1}/exceptionOccurrences/delta()?endDateTime={endDateTime}&startDateTime={startDateTime}{&%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * 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. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code * @see Find more info here @@ -46,7 +46,7 @@ public DeltaGetResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -60,7 +60,7 @@ public DeltaGetResponse get(@jakarta.annotation.Nullable final java.util.functio return this.requestAdapter.send(requestInfo, errorMapping, DeltaGetResponse::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -68,7 +68,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -90,7 +90,7 @@ public DeltaRequestBuilder withUrl(@jakarta.annotation.Nonnull final String rawU return new DeltaRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/users/item/calendars/item/events/delta/DeltaRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/users/item/calendars/item/events/delta/DeltaRequestBuilder.java index 0bbff8a7d93..05342f1566d 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/users/item/calendars/item/events/delta/DeltaRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/users/item/calendars/item/events/delta/DeltaRequestBuilder.java @@ -36,7 +36,7 @@ public DeltaRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @jak super(requestAdapter, "{+baseurl}/users/{user%2Did}/calendars/{calendar%2Did}/events/delta()?endDateTime={endDateTime}&startDateTime={startDateTime}{&%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * 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. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code * @see Find more info here @@ -46,7 +46,7 @@ public DeltaGetResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -60,7 +60,7 @@ public DeltaGetResponse get(@jakarta.annotation.Nullable final java.util.functio return this.requestAdapter.send(requestInfo, errorMapping, DeltaGetResponse::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -68,7 +68,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -90,7 +90,7 @@ public DeltaRequestBuilder withUrl(@jakarta.annotation.Nonnull final String rawU return new DeltaRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/users/item/calendars/item/events/item/exceptionoccurrences/delta/DeltaRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/users/item/calendars/item/events/item/exceptionoccurrences/delta/DeltaRequestBuilder.java index dec7e5fb8df..5bea2e35b47 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/users/item/calendars/item/events/item/exceptionoccurrences/delta/DeltaRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/users/item/calendars/item/events/item/exceptionoccurrences/delta/DeltaRequestBuilder.java @@ -36,7 +36,7 @@ public DeltaRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @jak super(requestAdapter, "{+baseurl}/users/{user%2Did}/calendars/{calendar%2Did}/events/{event%2Did}/exceptionOccurrences/delta()?endDateTime={endDateTime}&startDateTime={startDateTime}{&%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * 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. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code * @see Find more info here @@ -46,7 +46,7 @@ public DeltaGetResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -60,7 +60,7 @@ public DeltaGetResponse get(@jakarta.annotation.Nullable final java.util.functio return this.requestAdapter.send(requestInfo, errorMapping, DeltaGetResponse::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -68,7 +68,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -90,7 +90,7 @@ public DeltaRequestBuilder withUrl(@jakarta.annotation.Nonnull final String rawU return new DeltaRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/users/item/calendars/item/events/item/exceptionoccurrences/item/instances/delta/DeltaRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/users/item/calendars/item/events/item/exceptionoccurrences/item/instances/delta/DeltaRequestBuilder.java index a465b8b2147..b56675f3f0e 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/users/item/calendars/item/events/item/exceptionoccurrences/item/instances/delta/DeltaRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/users/item/calendars/item/events/item/exceptionoccurrences/item/instances/delta/DeltaRequestBuilder.java @@ -36,7 +36,7 @@ public DeltaRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @jak super(requestAdapter, "{+baseurl}/users/{user%2Did}/calendars/{calendar%2Did}/events/{event%2Did}/exceptionOccurrences/{event%2Did1}/instances/delta()?endDateTime={endDateTime}&startDateTime={startDateTime}{&%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * 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. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code * @see Find more info here @@ -46,7 +46,7 @@ public DeltaGetResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -60,7 +60,7 @@ public DeltaGetResponse get(@jakarta.annotation.Nullable final java.util.functio return this.requestAdapter.send(requestInfo, errorMapping, DeltaGetResponse::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -68,7 +68,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -90,7 +90,7 @@ public DeltaRequestBuilder withUrl(@jakarta.annotation.Nonnull final String rawU return new DeltaRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/users/item/calendars/item/events/item/instances/delta/DeltaRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/users/item/calendars/item/events/item/instances/delta/DeltaRequestBuilder.java index faf4224dcdf..5768d6a6176 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/users/item/calendars/item/events/item/instances/delta/DeltaRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/users/item/calendars/item/events/item/instances/delta/DeltaRequestBuilder.java @@ -36,7 +36,7 @@ public DeltaRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @jak super(requestAdapter, "{+baseurl}/users/{user%2Did}/calendars/{calendar%2Did}/events/{event%2Did}/instances/delta()?endDateTime={endDateTime}&startDateTime={startDateTime}{&%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * 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. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code * @see Find more info here @@ -46,7 +46,7 @@ public DeltaGetResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -60,7 +60,7 @@ public DeltaGetResponse get(@jakarta.annotation.Nullable final java.util.functio return this.requestAdapter.send(requestInfo, errorMapping, DeltaGetResponse::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -68,7 +68,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -90,7 +90,7 @@ public DeltaRequestBuilder withUrl(@jakarta.annotation.Nonnull final String rawU return new DeltaRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/users/item/calendars/item/events/item/instances/item/exceptionoccurrences/delta/DeltaRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/users/item/calendars/item/events/item/instances/item/exceptionoccurrences/delta/DeltaRequestBuilder.java index a7d1e5944e8..35277985d06 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/users/item/calendars/item/events/item/instances/item/exceptionoccurrences/delta/DeltaRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/users/item/calendars/item/events/item/instances/item/exceptionoccurrences/delta/DeltaRequestBuilder.java @@ -36,7 +36,7 @@ public DeltaRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @jak super(requestAdapter, "{+baseurl}/users/{user%2Did}/calendars/{calendar%2Did}/events/{event%2Did}/instances/{event%2Did1}/exceptionOccurrences/delta()?endDateTime={endDateTime}&startDateTime={startDateTime}{&%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * 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. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code * @see Find more info here @@ -46,7 +46,7 @@ public DeltaGetResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -60,7 +60,7 @@ public DeltaGetResponse get(@jakarta.annotation.Nullable final java.util.functio return this.requestAdapter.send(requestInfo, errorMapping, DeltaGetResponse::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -68,7 +68,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -90,7 +90,7 @@ public DeltaRequestBuilder withUrl(@jakarta.annotation.Nonnull final String rawU return new DeltaRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/users/item/calendarview/delta/DeltaRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/users/item/calendarview/delta/DeltaRequestBuilder.java index 159f726afa4..b2438cb8d08 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/users/item/calendarview/delta/DeltaRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/users/item/calendarview/delta/DeltaRequestBuilder.java @@ -36,7 +36,7 @@ public DeltaRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @jak super(requestAdapter, "{+baseurl}/users/{user%2Did}/calendarView/delta()?endDateTime={endDateTime}&startDateTime={startDateTime}{&%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * 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. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code * @see Find more info here @@ -46,7 +46,7 @@ public DeltaGetResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -60,7 +60,7 @@ public DeltaGetResponse get(@jakarta.annotation.Nullable final java.util.functio return this.requestAdapter.send(requestInfo, errorMapping, DeltaGetResponse::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -68,7 +68,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -90,7 +90,7 @@ public DeltaRequestBuilder withUrl(@jakarta.annotation.Nonnull final String rawU return new DeltaRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/users/item/calendarview/item/exceptionoccurrences/delta/DeltaRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/users/item/calendarview/item/exceptionoccurrences/delta/DeltaRequestBuilder.java index 7acf7239834..b6a4212c1a1 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/users/item/calendarview/item/exceptionoccurrences/delta/DeltaRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/users/item/calendarview/item/exceptionoccurrences/delta/DeltaRequestBuilder.java @@ -36,7 +36,7 @@ public DeltaRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @jak super(requestAdapter, "{+baseurl}/users/{user%2Did}/calendarView/{event%2Did}/exceptionOccurrences/delta()?endDateTime={endDateTime}&startDateTime={startDateTime}{&%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * 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. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code * @see Find more info here @@ -46,7 +46,7 @@ public DeltaGetResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -60,7 +60,7 @@ public DeltaGetResponse get(@jakarta.annotation.Nullable final java.util.functio return this.requestAdapter.send(requestInfo, errorMapping, DeltaGetResponse::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -68,7 +68,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -90,7 +90,7 @@ public DeltaRequestBuilder withUrl(@jakarta.annotation.Nonnull final String rawU return new DeltaRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/users/item/calendarview/item/exceptionoccurrences/item/instances/delta/DeltaRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/users/item/calendarview/item/exceptionoccurrences/item/instances/delta/DeltaRequestBuilder.java index ade14f38948..fe40edc0120 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/users/item/calendarview/item/exceptionoccurrences/item/instances/delta/DeltaRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/users/item/calendarview/item/exceptionoccurrences/item/instances/delta/DeltaRequestBuilder.java @@ -36,7 +36,7 @@ public DeltaRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @jak super(requestAdapter, "{+baseurl}/users/{user%2Did}/calendarView/{event%2Did}/exceptionOccurrences/{event%2Did1}/instances/delta()?endDateTime={endDateTime}&startDateTime={startDateTime}{&%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * 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. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code * @see Find more info here @@ -46,7 +46,7 @@ public DeltaGetResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -60,7 +60,7 @@ public DeltaGetResponse get(@jakarta.annotation.Nullable final java.util.functio return this.requestAdapter.send(requestInfo, errorMapping, DeltaGetResponse::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -68,7 +68,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -90,7 +90,7 @@ public DeltaRequestBuilder withUrl(@jakarta.annotation.Nonnull final String rawU return new DeltaRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/users/item/calendarview/item/instances/delta/DeltaRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/users/item/calendarview/item/instances/delta/DeltaRequestBuilder.java index 6e6121ff3d4..451a1caa902 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/users/item/calendarview/item/instances/delta/DeltaRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/users/item/calendarview/item/instances/delta/DeltaRequestBuilder.java @@ -36,7 +36,7 @@ public DeltaRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @jak super(requestAdapter, "{+baseurl}/users/{user%2Did}/calendarView/{event%2Did}/instances/delta()?endDateTime={endDateTime}&startDateTime={startDateTime}{&%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * 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. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code * @see Find more info here @@ -46,7 +46,7 @@ public DeltaGetResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -60,7 +60,7 @@ public DeltaGetResponse get(@jakarta.annotation.Nullable final java.util.functio return this.requestAdapter.send(requestInfo, errorMapping, DeltaGetResponse::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -68,7 +68,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -90,7 +90,7 @@ public DeltaRequestBuilder withUrl(@jakarta.annotation.Nonnull final String rawU return new DeltaRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/users/item/calendarview/item/instances/item/exceptionoccurrences/delta/DeltaRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/users/item/calendarview/item/instances/item/exceptionoccurrences/delta/DeltaRequestBuilder.java index 4e29d610e59..62a5879c336 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/users/item/calendarview/item/instances/item/exceptionoccurrences/delta/DeltaRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/users/item/calendarview/item/instances/item/exceptionoccurrences/delta/DeltaRequestBuilder.java @@ -36,7 +36,7 @@ public DeltaRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @jak super(requestAdapter, "{+baseurl}/users/{user%2Did}/calendarView/{event%2Did}/instances/{event%2Did1}/exceptionOccurrences/delta()?endDateTime={endDateTime}&startDateTime={startDateTime}{&%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * 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. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code * @see Find more info here @@ -46,7 +46,7 @@ public DeltaGetResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -60,7 +60,7 @@ public DeltaGetResponse get(@jakarta.annotation.Nullable final java.util.functio return this.requestAdapter.send(requestInfo, errorMapping, DeltaGetResponse::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -68,7 +68,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -90,7 +90,7 @@ public DeltaRequestBuilder withUrl(@jakarta.annotation.Nonnull final String rawU return new DeltaRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/users/item/cloudpcs/item/retrievereviewstatus/RetrieveReviewStatusRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/users/item/cloudpcs/item/retrievereviewstatus/RetrieveReviewStatusRequestBuilder.java index f53f3d83d40..ea233edc208 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/users/item/cloudpcs/item/retrievereviewstatus/RetrieveReviewStatusRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/users/item/cloudpcs/item/retrievereviewstatus/RetrieveReviewStatusRequestBuilder.java @@ -36,19 +36,21 @@ public RetrieveReviewStatusRequestBuilder(@jakarta.annotation.Nonnull final Stri super(requestAdapter, "{+baseurl}/users/{user%2Did}/cloudPCs/{cloudPC%2Did}/retrieveReviewStatus()", rawUrl); } /** - * Invoke function retrieveReviewStatus + * Get the review status of a Cloud PC. * @return a {@link CloudPcReviewStatus} * @throws ODataError When receiving a 4XX or 5XX status code + * @see Find more info here */ @jakarta.annotation.Nullable public CloudPcReviewStatus get() { return get(null); } /** - * Invoke function retrieveReviewStatus + * Get the review status of a Cloud PC. * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link CloudPcReviewStatus} * @throws ODataError When receiving a 4XX or 5XX status code + * @see Find more info here */ @jakarta.annotation.Nullable public CloudPcReviewStatus get(@jakarta.annotation.Nullable final java.util.function.Consumer requestConfiguration) { @@ -58,7 +60,7 @@ public CloudPcReviewStatus get(@jakarta.annotation.Nullable final java.util.func return this.requestAdapter.send(requestInfo, errorMapping, CloudPcReviewStatus::createFromDiscriminatorValue); } /** - * Invoke function retrieveReviewStatus + * Get the review status of a Cloud PC. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -66,7 +68,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * Invoke function retrieveReviewStatus + * Get the review status of a Cloud PC. * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ diff --git a/src/main/java/com/microsoft/graph/beta/generated/users/item/cloudpcs/item/retrievesnapshots/RetrieveSnapshotsRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/users/item/cloudpcs/item/retrievesnapshots/RetrieveSnapshotsRequestBuilder.java index 9f047b35f32..bbbb0e378f3 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/users/item/cloudpcs/item/retrievesnapshots/RetrieveSnapshotsRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/users/item/cloudpcs/item/retrievesnapshots/RetrieveSnapshotsRequestBuilder.java @@ -36,19 +36,21 @@ public RetrieveSnapshotsRequestBuilder(@jakarta.annotation.Nonnull final String super(requestAdapter, "{+baseurl}/users/{user%2Did}/cloudPCs/{cloudPC%2Did}/retrieveSnapshots(){?%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * Invoke function retrieveSnapshots + * List all cloudPcSnapshot resources for a Cloud PC. * @return a {@link RetrieveSnapshotsGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code + * @see Find more info here */ @jakarta.annotation.Nullable public RetrieveSnapshotsGetResponse get() { return get(null); } /** - * Invoke function retrieveSnapshots + * List all cloudPcSnapshot resources for a Cloud PC. * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RetrieveSnapshotsGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code + * @see Find more info here */ @jakarta.annotation.Nullable public RetrieveSnapshotsGetResponse get(@jakarta.annotation.Nullable final java.util.function.Consumer requestConfiguration) { @@ -58,7 +60,7 @@ public RetrieveSnapshotsGetResponse get(@jakarta.annotation.Nullable final java. return this.requestAdapter.send(requestInfo, errorMapping, RetrieveSnapshotsGetResponse::createFromDiscriminatorValue); } /** - * Invoke function retrieveSnapshots + * List all cloudPcSnapshot resources for a Cloud PC. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -66,7 +68,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * Invoke function retrieveSnapshots + * List all cloudPcSnapshot resources for a Cloud PC. * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -88,7 +90,7 @@ public RetrieveSnapshotsRequestBuilder withUrl(@jakarta.annotation.Nonnull final return new RetrieveSnapshotsRequestBuilder(rawUrl, requestAdapter); } /** - * Invoke function retrieveSnapshots + * List all cloudPcSnapshot resources for a Cloud PC. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/users/item/cloudpcs/item/setreviewstatus/SetReviewStatusRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/users/item/cloudpcs/item/setreviewstatus/SetReviewStatusRequestBuilder.java index 6128d5270ed..e61eedad9cb 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/users/item/cloudpcs/item/setreviewstatus/SetReviewStatusRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/users/item/cloudpcs/item/setreviewstatus/SetReviewStatusRequestBuilder.java @@ -35,18 +35,20 @@ public SetReviewStatusRequestBuilder(@jakarta.annotation.Nonnull final String ra super(requestAdapter, "{+baseurl}/users/{user%2Did}/cloudPCs/{cloudPC%2Did}/setReviewStatus", rawUrl); } /** - * 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 * @throws ODataError When receiving a 4XX or 5XX status code + * @see Find more info here */ public void post(@jakarta.annotation.Nonnull final SetReviewStatusPostRequestBody body) { post(body, null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @throws ODataError When receiving a 4XX or 5XX status code + * @see Find more info here */ public void post(@jakarta.annotation.Nonnull final SetReviewStatusPostRequestBody body, @jakarta.annotation.Nullable final java.util.function.Consumer requestConfiguration) { Objects.requireNonNull(body); @@ -56,7 +58,7 @@ public void post(@jakarta.annotation.Nonnull final SetReviewStatusPostRequestBod this.requestAdapter.sendPrimitive(requestInfo, errorMapping, Void.class); } /** - * 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 * @return a {@link RequestInformation} */ @@ -65,7 +67,7 @@ public RequestInformation toPostRequestInformation(@jakarta.annotation.Nonnull f return toPostRequestInformation(body, null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} diff --git a/src/main/java/com/microsoft/graph/beta/generated/users/item/events/delta/DeltaRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/users/item/events/delta/DeltaRequestBuilder.java index 4db2c061ba1..28d5a614994 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/users/item/events/delta/DeltaRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/users/item/events/delta/DeltaRequestBuilder.java @@ -36,7 +36,7 @@ public DeltaRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @jak super(requestAdapter, "{+baseurl}/users/{user%2Did}/events/delta()?endDateTime={endDateTime}&startDateTime={startDateTime}{&%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * 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. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code * @see Find more info here @@ -46,7 +46,7 @@ public DeltaGetResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -60,7 +60,7 @@ public DeltaGetResponse get(@jakarta.annotation.Nullable final java.util.functio return this.requestAdapter.send(requestInfo, errorMapping, DeltaGetResponse::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -68,7 +68,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -90,7 +90,7 @@ public DeltaRequestBuilder withUrl(@jakarta.annotation.Nonnull final String rawU return new DeltaRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/users/item/events/item/exceptionoccurrences/delta/DeltaRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/users/item/events/item/exceptionoccurrences/delta/DeltaRequestBuilder.java index e77c67c01a1..9afebcf528c 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/users/item/events/item/exceptionoccurrences/delta/DeltaRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/users/item/events/item/exceptionoccurrences/delta/DeltaRequestBuilder.java @@ -36,7 +36,7 @@ public DeltaRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @jak super(requestAdapter, "{+baseurl}/users/{user%2Did}/events/{event%2Did}/exceptionOccurrences/delta()?endDateTime={endDateTime}&startDateTime={startDateTime}{&%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * 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. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code * @see Find more info here @@ -46,7 +46,7 @@ public DeltaGetResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -60,7 +60,7 @@ public DeltaGetResponse get(@jakarta.annotation.Nullable final java.util.functio return this.requestAdapter.send(requestInfo, errorMapping, DeltaGetResponse::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -68,7 +68,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -90,7 +90,7 @@ public DeltaRequestBuilder withUrl(@jakarta.annotation.Nonnull final String rawU return new DeltaRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/users/item/events/item/exceptionoccurrences/item/instances/delta/DeltaRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/users/item/events/item/exceptionoccurrences/item/instances/delta/DeltaRequestBuilder.java index 487915d19b7..8511f5d6a01 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/users/item/events/item/exceptionoccurrences/item/instances/delta/DeltaRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/users/item/events/item/exceptionoccurrences/item/instances/delta/DeltaRequestBuilder.java @@ -36,7 +36,7 @@ public DeltaRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @jak super(requestAdapter, "{+baseurl}/users/{user%2Did}/events/{event%2Did}/exceptionOccurrences/{event%2Did1}/instances/delta()?endDateTime={endDateTime}&startDateTime={startDateTime}{&%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * 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. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code * @see Find more info here @@ -46,7 +46,7 @@ public DeltaGetResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -60,7 +60,7 @@ public DeltaGetResponse get(@jakarta.annotation.Nullable final java.util.functio return this.requestAdapter.send(requestInfo, errorMapping, DeltaGetResponse::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -68,7 +68,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -90,7 +90,7 @@ public DeltaRequestBuilder withUrl(@jakarta.annotation.Nonnull final String rawU return new DeltaRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/users/item/events/item/instances/delta/DeltaRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/users/item/events/item/instances/delta/DeltaRequestBuilder.java index c2fc636142f..d9b18e69d1d 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/users/item/events/item/instances/delta/DeltaRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/users/item/events/item/instances/delta/DeltaRequestBuilder.java @@ -36,7 +36,7 @@ public DeltaRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @jak super(requestAdapter, "{+baseurl}/users/{user%2Did}/events/{event%2Did}/instances/delta()?endDateTime={endDateTime}&startDateTime={startDateTime}{&%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * 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. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code * @see Find more info here @@ -46,7 +46,7 @@ public DeltaGetResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -60,7 +60,7 @@ public DeltaGetResponse get(@jakarta.annotation.Nullable final java.util.functio return this.requestAdapter.send(requestInfo, errorMapping, DeltaGetResponse::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -68,7 +68,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -90,7 +90,7 @@ public DeltaRequestBuilder withUrl(@jakarta.annotation.Nonnull final String rawU return new DeltaRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/users/item/events/item/instances/item/exceptionoccurrences/delta/DeltaRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/users/item/events/item/instances/item/exceptionoccurrences/delta/DeltaRequestBuilder.java index b81a637a37f..1da6c7caa1f 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/users/item/events/item/instances/item/exceptionoccurrences/delta/DeltaRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/users/item/events/item/instances/item/exceptionoccurrences/delta/DeltaRequestBuilder.java @@ -36,7 +36,7 @@ public DeltaRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @jak super(requestAdapter, "{+baseurl}/users/{user%2Did}/events/{event%2Did}/instances/{event%2Did1}/exceptionOccurrences/delta()?endDateTime={endDateTime}&startDateTime={startDateTime}{&%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * 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. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code * @see Find more info here @@ -46,7 +46,7 @@ public DeltaGetResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -60,7 +60,7 @@ public DeltaGetResponse get(@jakarta.annotation.Nullable final java.util.functio return this.requestAdapter.send(requestInfo, errorMapping, DeltaGetResponse::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -68,7 +68,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -90,7 +90,7 @@ public DeltaRequestBuilder withUrl(@jakarta.annotation.Nonnull final String rawU return new DeltaRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/users/item/mailfolders/item/childfolders/item/messages/delta/DeltaRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/users/item/mailfolders/item/childfolders/item/messages/delta/DeltaRequestBuilder.java index a9acfa7df7f..dea9fa714c0 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/users/item/mailfolders/item/childfolders/item/messages/delta/DeltaRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/users/item/mailfolders/item/childfolders/item/messages/delta/DeltaRequestBuilder.java @@ -36,7 +36,7 @@ public DeltaRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @jak super(requestAdapter, "{+baseurl}/users/{user%2Did}/mailFolders/{mailFolder%2Did}/childFolders/{mailFolder%2Did1}/messages/delta(){?%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top,changeType*}", rawUrl); } /** - * 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. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code * @see Find more info here @@ -46,7 +46,7 @@ public DeltaGetResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -60,7 +60,7 @@ public DeltaGetResponse get(@jakarta.annotation.Nullable final java.util.functio return this.requestAdapter.send(requestInfo, errorMapping, DeltaGetResponse::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -68,7 +68,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -90,7 +90,7 @@ public DeltaRequestBuilder withUrl(@jakarta.annotation.Nonnull final String rawU return new DeltaRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/users/item/mailfolders/item/messages/delta/DeltaRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/users/item/mailfolders/item/messages/delta/DeltaRequestBuilder.java index 015d958f82d..e65a00c370b 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/users/item/mailfolders/item/messages/delta/DeltaRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/users/item/mailfolders/item/messages/delta/DeltaRequestBuilder.java @@ -36,7 +36,7 @@ public DeltaRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @jak super(requestAdapter, "{+baseurl}/users/{user%2Did}/mailFolders/{mailFolder%2Did}/messages/delta(){?%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top,changeType*}", rawUrl); } /** - * 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. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code * @see Find more info here @@ -46,7 +46,7 @@ public DeltaGetResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -60,7 +60,7 @@ public DeltaGetResponse get(@jakarta.annotation.Nullable final java.util.functio return this.requestAdapter.send(requestInfo, errorMapping, DeltaGetResponse::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -68,7 +68,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -90,7 +90,7 @@ public DeltaRequestBuilder withUrl(@jakarta.annotation.Nonnull final String rawU return new DeltaRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/users/item/messages/delta/DeltaRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/users/item/messages/delta/DeltaRequestBuilder.java index 17131c42bf6..9910d1790f3 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/users/item/messages/delta/DeltaRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/users/item/messages/delta/DeltaRequestBuilder.java @@ -36,7 +36,7 @@ public DeltaRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @jak super(requestAdapter, "{+baseurl}/users/{user%2Did}/messages/delta(){?%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top,changeType*}", rawUrl); } /** - * 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. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code * @see Find more info here @@ -46,7 +46,7 @@ public DeltaGetResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link DeltaGetResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -60,7 +60,7 @@ public DeltaGetResponse get(@jakarta.annotation.Nullable final java.util.functio return this.requestAdapter.send(requestInfo, errorMapping, DeltaGetResponse::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -68,7 +68,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -90,7 +90,7 @@ public DeltaRequestBuilder withUrl(@jakarta.annotation.Nonnull final String rawU return new DeltaRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/users/item/onenote/notebooks/NotebooksRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/users/item/onenote/notebooks/NotebooksRequestBuilder.java index 50004655514..6bf49bdbe97 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/users/item/onenote/notebooks/NotebooksRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/users/item/onenote/notebooks/NotebooksRequestBuilder.java @@ -70,7 +70,7 @@ public NotebooksRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, super(requestAdapter, "{+baseurl}/users/{user%2Did}/onenote/notebooks{?%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * 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. * @return a {@link NotebookCollectionResponse} * @throws ODataError When receiving a 4XX or 5XX status code */ @@ -79,7 +79,7 @@ public NotebookCollectionResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link NotebookCollectionResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -127,7 +127,7 @@ public Notebook post(@jakarta.annotation.Nonnull final Notebook body, @jakarta.a return this.requestAdapter.send(requestInfo, errorMapping, Notebook::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -135,7 +135,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -181,7 +181,7 @@ public NotebooksRequestBuilder withUrl(@jakarta.annotation.Nonnull final String return new NotebooksRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/users/item/onenote/notebooks/item/NotebookItemRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/users/item/onenote/notebooks/item/NotebookItemRequestBuilder.java index ca42c6da534..3f8448c51fc 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/users/item/onenote/notebooks/item/NotebookItemRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/users/item/onenote/notebooks/item/NotebookItemRequestBuilder.java @@ -82,7 +82,7 @@ public void delete(@jakarta.annotation.Nullable final java.util.function.Consume this.requestAdapter.sendPrimitive(requestInfo, errorMapping, Void.class); } /** - * 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. * @return a {@link Notebook} * @throws ODataError When receiving a 4XX or 5XX status code */ @@ -91,7 +91,7 @@ public Notebook get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link Notebook} * @throws ODataError When receiving a 4XX or 5XX status code @@ -149,7 +149,7 @@ public RequestInformation toDeleteRequestInformation(@jakarta.annotation.Nullabl return requestInfo; } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -157,7 +157,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -209,7 +209,7 @@ public NotebookItemRequestBuilder withUrl(@jakarta.annotation.Nonnull final Stri public class DeleteRequestConfiguration extends BaseRequestConfiguration { } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/users/item/onenote/pages/PagesRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/users/item/onenote/pages/PagesRequestBuilder.java index 5a8f81130e7..99441209a3e 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/users/item/onenote/pages/PagesRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/users/item/onenote/pages/PagesRequestBuilder.java @@ -60,7 +60,7 @@ public PagesRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @jak super(requestAdapter, "{+baseurl}/users/{user%2Did}/onenote/pages{?%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * 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. * @return a {@link OnenotePageCollectionResponse} * @throws ODataError When receiving a 4XX or 5XX status code */ @@ -69,7 +69,7 @@ public OnenotePageCollectionResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link OnenotePageCollectionResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -107,7 +107,7 @@ public OnenotePage post(@jakarta.annotation.Nonnull final OnenotePage body, @jak return this.requestAdapter.send(requestInfo, errorMapping, OnenotePage::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -115,7 +115,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -161,7 +161,7 @@ public PagesRequestBuilder withUrl(@jakarta.annotation.Nonnull final String rawU return new PagesRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/users/item/onenote/pages/item/OnenotePageItemRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/users/item/onenote/pages/item/OnenotePageItemRequestBuilder.java index df39a30a334..67f5046f0ed 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/users/item/onenote/pages/item/OnenotePageItemRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/users/item/onenote/pages/item/OnenotePageItemRequestBuilder.java @@ -109,7 +109,7 @@ public void delete(@jakarta.annotation.Nullable final java.util.function.Consume this.requestAdapter.sendPrimitive(requestInfo, errorMapping, Void.class); } /** - * 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. * @return a {@link OnenotePage} * @throws ODataError When receiving a 4XX or 5XX status code */ @@ -118,7 +118,7 @@ public OnenotePage get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link OnenotePage} * @throws ODataError When receiving a 4XX or 5XX status code @@ -176,7 +176,7 @@ public RequestInformation toDeleteRequestInformation(@jakarta.annotation.Nullabl return requestInfo; } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -184,7 +184,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -236,7 +236,7 @@ public OnenotePageItemRequestBuilder withUrl(@jakarta.annotation.Nonnull final S public class DeleteRequestConfiguration extends BaseRequestConfiguration { } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/users/item/onenote/sectiongroups/SectionGroupsRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/users/item/onenote/sectiongroups/SectionGroupsRequestBuilder.java index d994d6ad467..0ecf0566d98 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/users/item/onenote/sectiongroups/SectionGroupsRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/users/item/onenote/sectiongroups/SectionGroupsRequestBuilder.java @@ -60,7 +60,7 @@ public SectionGroupsRequestBuilder(@jakarta.annotation.Nonnull final String rawU super(requestAdapter, "{+baseurl}/users/{user%2Did}/onenote/sectionGroups{?%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * 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. * @return a {@link SectionGroupCollectionResponse} * @throws ODataError When receiving a 4XX or 5XX status code */ @@ -69,7 +69,7 @@ public SectionGroupCollectionResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link SectionGroupCollectionResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -107,7 +107,7 @@ public SectionGroup post(@jakarta.annotation.Nonnull final SectionGroup body, @j return this.requestAdapter.send(requestInfo, errorMapping, SectionGroup::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -115,7 +115,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -161,7 +161,7 @@ public SectionGroupsRequestBuilder withUrl(@jakarta.annotation.Nonnull final Str return new SectionGroupsRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/users/item/onenote/sectiongroups/item/SectionGroupItemRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/users/item/onenote/sectiongroups/item/SectionGroupItemRequestBuilder.java index cfdf58dddd1..779f9334c79 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/users/item/onenote/sectiongroups/item/SectionGroupItemRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/users/item/onenote/sectiongroups/item/SectionGroupItemRequestBuilder.java @@ -91,7 +91,7 @@ public void delete(@jakarta.annotation.Nullable final java.util.function.Consume this.requestAdapter.sendPrimitive(requestInfo, errorMapping, Void.class); } /** - * 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. * @return a {@link SectionGroup} * @throws ODataError When receiving a 4XX or 5XX status code */ @@ -100,7 +100,7 @@ public SectionGroup get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link SectionGroup} * @throws ODataError When receiving a 4XX or 5XX status code @@ -158,7 +158,7 @@ public RequestInformation toDeleteRequestInformation(@jakarta.annotation.Nullabl return requestInfo; } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -166,7 +166,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -218,7 +218,7 @@ public SectionGroupItemRequestBuilder withUrl(@jakarta.annotation.Nonnull final public class DeleteRequestConfiguration extends BaseRequestConfiguration { } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/users/item/onenote/sections/SectionsRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/users/item/onenote/sections/SectionsRequestBuilder.java index 0f0704321e6..0cdee552262 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/users/item/onenote/sections/SectionsRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/users/item/onenote/sections/SectionsRequestBuilder.java @@ -60,7 +60,7 @@ public SectionsRequestBuilder(@jakarta.annotation.Nonnull final String rawUrl, @ super(requestAdapter, "{+baseurl}/users/{user%2Did}/onenote/sections{?%24count,%24expand,%24filter,%24orderby,%24search,%24select,%24skip,%24top}", rawUrl); } /** - * 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. * @return a {@link OnenoteSectionCollectionResponse} * @throws ODataError When receiving a 4XX or 5XX status code */ @@ -69,7 +69,7 @@ public OnenoteSectionCollectionResponse get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link OnenoteSectionCollectionResponse} * @throws ODataError When receiving a 4XX or 5XX status code @@ -107,7 +107,7 @@ public OnenoteSection post(@jakarta.annotation.Nonnull final OnenoteSection body return this.requestAdapter.send(requestInfo, errorMapping, OnenoteSection::createFromDiscriminatorValue); } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -115,7 +115,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -161,7 +161,7 @@ public SectionsRequestBuilder withUrl(@jakarta.annotation.Nonnull final String r return new SectionsRequestBuilder(rawUrl, requestAdapter); } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/users/item/onenote/sections/item/OnenoteSectionItemRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/users/item/onenote/sections/item/OnenoteSectionItemRequestBuilder.java index 0de028bf052..51676f4dfab 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/users/item/onenote/sections/item/OnenoteSectionItemRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/users/item/onenote/sections/item/OnenoteSectionItemRequestBuilder.java @@ -100,7 +100,7 @@ public void delete(@jakarta.annotation.Nullable final java.util.function.Consume this.requestAdapter.sendPrimitive(requestInfo, errorMapping, Void.class); } /** - * 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. * @return a {@link OnenoteSection} * @throws ODataError When receiving a 4XX or 5XX status code */ @@ -109,7 +109,7 @@ public OnenoteSection get() { return get(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link OnenoteSection} * @throws ODataError When receiving a 4XX or 5XX status code @@ -167,7 +167,7 @@ public RequestInformation toDeleteRequestInformation(@jakarta.annotation.Nullabl return requestInfo; } /** - * 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. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -175,7 +175,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * 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 requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -227,7 +227,7 @@ public OnenoteSectionItemRequestBuilder withUrl(@jakarta.annotation.Nonnull fina public class DeleteRequestConfiguration extends BaseRequestConfiguration { } /** - * 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. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters { diff --git a/src/main/java/com/microsoft/graph/beta/generated/users/item/presence/PresenceRequestBuilder.java b/src/main/java/com/microsoft/graph/beta/generated/users/item/presence/PresenceRequestBuilder.java index 1294023c5f3..a24a3464409 100644 --- a/src/main/java/com/microsoft/graph/beta/generated/users/item/presence/PresenceRequestBuilder.java +++ b/src/main/java/com/microsoft/graph/beta/generated/users/item/presence/PresenceRequestBuilder.java @@ -100,21 +100,21 @@ public void delete(@jakarta.annotation.Nullable final java.util.function.Consume this.requestAdapter.sendPrimitive(requestInfo, errorMapping, Void.class); } /** - * Set a presence status message for a user. An optional expiration date and time can be supplied. + * Get a user's presence information. * @return a {@link Presence} * @throws ODataError When receiving a 4XX or 5XX status code - * @see Find more info here + * @see Find more info here */ @jakarta.annotation.Nullable public Presence get() { return get(null); } /** - * Set a presence status message for a user. An optional expiration date and time can be supplied. + * Get a user's presence information. * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link Presence} * @throws ODataError When receiving a 4XX or 5XX status code - * @see Find more info here + * @see Find more info here */ @jakarta.annotation.Nullable public Presence get(@jakarta.annotation.Nullable final java.util.function.Consumer requestConfiguration) { @@ -169,7 +169,7 @@ public RequestInformation toDeleteRequestInformation(@jakarta.annotation.Nullabl return requestInfo; } /** - * Set a presence status message for a user. An optional expiration date and time can be supplied. + * Get a user's presence information. * @return a {@link RequestInformation} */ @jakarta.annotation.Nonnull @@ -177,7 +177,7 @@ public RequestInformation toGetRequestInformation() { return toGetRequestInformation(null); } /** - * Set a presence status message for a user. An optional expiration date and time can be supplied. + * Get a user's presence information. * @param requestConfiguration Configuration for the request such as headers, query parameters, and middleware options. * @return a {@link RequestInformation} */ @@ -229,7 +229,7 @@ public PresenceRequestBuilder withUrl(@jakarta.annotation.Nonnull final String r public class DeleteRequestConfiguration extends BaseRequestConfiguration { } /** - * Set a presence status message for a user. An optional expiration date and time can be supplied. + * Get a user's presence information. */ @jakarta.annotation.Generated("com.microsoft.kiota") public class GetQueryParameters implements QueryParameters {