Breaking Changes for Cryptography plugin

2.0.0

12 Sep 2023

DateTime values now contain time zone offsets

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.

Obsolete properties

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, similarly named properties - all new properties were post-fixed by 'DateTimeOffset'. For example, '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:

Example 1

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

Last updated