Struct google_analytics3::ManagementCustomDimensionPatchCall [] [src]

pub struct ManagementCustomDimensionPatchCall<'a, C, A> where C: 'a, A: 'a { /* fields omitted */ }

Updates an existing custom dimension. This method supports patch semantics.

A builder for the customDimensions.patch method supported by a management resource. It is not used directly, but through a ManagementMethods instance.

Example

Instantiate a resource method builder

use analytics3::CustomDimension;
 
// As the method needs a request, you would usually fill it with the desired information
// into the respective structure. Some of the parts shown here might not be applicable !
// Values shown here are possibly random and not representative !
let mut req = CustomDimension::default();
 
// You can configure optional parameters by calling the respective setters at will, and
// execute the final call using `doit()`.
// Values shown here are possibly random and not representative !
let result = hub.management().custom_dimensions_patch(req, "accountId", "webPropertyId", "customDimensionId")
             .ignore_custom_data_source_links(true)
             .doit();

Methods

impl<'a, C, A> ManagementCustomDimensionPatchCall<'a, C, A> where C: BorrowMut<Client>, A: GetToken
[src]

Perform the operation you have build so far.

Sets the request property to the given value.

Even though the property as already been set when instantiating this call, we provide this method for API completeness.

Account ID for the custom dimension to update.

Sets the account id path property to the given value.

Even though the property as already been set when instantiating this call, we provide this method for API completeness.

Web property ID for the custom dimension to update.

Sets the web property id path property to the given value.

Even though the property as already been set when instantiating this call, we provide this method for API completeness.

Custom dimension ID for the custom dimension to update.

Sets the custom dimension id path property to the given value.

Even though the property as already been set when instantiating this call, we provide this method for API completeness.

Force the update and ignore any warnings related to the custom dimension being linked to a custom data source / data set.

Sets the ignore custom data source links query property to the given value.

The delegate implementation is consulted whenever there is an intermediate result, or if something goes wrong while executing the actual API request.

It should be used to handle progress information, and to implement a certain level of resilience.

Sets the delegate property to the given value.

Set any additional parameter of the query string used in the request. It should be used to set parameters which are not yet available through their own setters.

Please note that this method must not be used to set any of the known paramters which have their own setter method. If done anyway, the request will fail.

Additional Parameters

  • quotaUser (query-string) - Available to use for quota purposes for server-side applications. Can be any arbitrary string assigned to a user, but should not exceed 40 characters. Overrides userIp if both are provided.
  • oauth_token (query-string) - OAuth 2.0 token for the current user.
  • key (query-string) - API key. Your API key identifies your project and provides you with API access, quota, and reports. Required unless you provide an OAuth 2.0 token.
  • prettyPrint (query-boolean) - Returns response with indentations and line breaks.
  • userIp (query-string) - IP address of the site where the request originates. Use this if you want to enforce per-user limits.
  • fields (query-string) - Selector specifying which fields to include in a partial response.
  • alt (query-string) - Data format for the response.

Identifies the authorization scope for the method you are building.

Use this method to actively specify which scope should be used, instead the default Scope variant Scope::Edit.

The scope will be added to a set of scopes. This is important as one can maintain access tokens for more than one scope.

Usually there is more than one suitable scope to authorize an operation, some of which may encompass more rights than others. For example, for listing resources, a read-only scope will be sufficient, a read-write scope will do as well.

Trait Implementations

impl<'a, C, A> CallBuilder for ManagementCustomDimensionPatchCall<'a, C, A>
[src]