当使用格式previous_event_id + _R + date生成周期性ID时 [英] When recurring id is generated with format previous_event_id+_R+date

查看:91
本文介绍了当使用格式previous_event_id + _R + date生成周期性ID时的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

通常,这是Google生成的重复事件ID的格式: qmjtng94k5mgge24890nmoasts(26个字符的字母数字)

Normally, this is the format of a recurring event ID generated by Google: qmjtng94k5mgge24890nmoasts (26 character alphanumeric)

在某些情况下,我们看到生成的重复事件ID的格式为: qmjtng94k5mgge24890nmoasts_R20160823T180000

In some cases, we see that the recurring event ID generated is of the format: qmjtng94k5mgge24890nmoasts_R20160823T180000

我想知道何时生成这种事件ID? 具体来说,何时使用下划线,大写R,日期后缀和相同的先前eventId前缀生成重复发生的事件ID?

I want to know when this kind of event Id is generated ? Specifically, when is a recurring event ID generated with the underscore, capital R, date suffix and the same previous eventId prefix?

推荐答案

使用下划线,大写R和日期后缀生成重复事件ID时-表示您编辑了现有重复事件并选择了在保存更改(例如,更改标题)期间选择"关注事件"选项. "date"后缀表示您的更改将应用​​于现有系列中从该日期开始的所有事件.

When recurring event ID generated with the underscore, capital R and date suffix - it means that you edited the existing recurrent event and selected the option "Following events" during saving your changes (e.g. changed the title). The "date" suffix means that your changes are applied to all events starting from that date in the existing series.

注意:如果您更改了重复模式并选择了后续事件"选项,它将生成具有完全唯一ID(无下划线,大写R和日期后缀)的全新系列.

Note: if you changed the recurrent pattern and selected the option "Following events", it will generate the brand-new series with completely unique ID (without underscore, capital R and date suffix).

这篇关于当使用格式previous_event_id + _R + date生成周期性ID时的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆