# Breaking Changes for Google Drive plugin

### 2.0.0 <a href="#id-2-0-0" id="id-2-0-0"></a>

12 Sep 2023

#### DateTime values now contain time zone offsets <a href="#datetime-values-now-contain-time-zone-offsets" id="datetime-values-now-contain-time-zone-offsets"></a>

**What breaks?**

Certain properties have been replaced by new properties in the Google API. The old properties, if used in your solution, will show up as validation errors.

**Why?**

Google Drive changed their API to work with DateTimeOffsets rather than DateTime types. All affected properties were marked as obsolete and replaced by new, similar named properties - all new properties were post-fixed by 'DateTimeOffset'. I.e. 'CreatedTime' was replaced with 'CreatedTimeDateTimeOffset'.

**How to fix it**

Replace all obsolete properties with their corresponding 'DateTimeOffset' post-fixed versions.

> E.g. Take the solution below The Google Drive CreateComment function is executed and then the result is used later down in the User Function. The expression using the result now needs to change from using the `CreatedTime` property to using the new property, `CreatedTimeDateTimeOffset`.
>
> *Before:* `=CreateComment.CreatedTime`
>
> *After:* `=CreateComment.CreatedTimeDateTimeOffset`


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.linx.software/releasenotes/plugins/googledrive/breaking-changes.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.