Having issues copying event from one SP19 on-prem calendar to a second calendar (creating a new item on that second calendar)

Before delving into the workflow nittygritty, is there a specific reason for there to exist two separate calendars? Sharepoint Calendars are essentially just lists of events and work similar to them, you can also create multiple views for them that filter on specific metadata on the columns. Wouldn’t it be significantly simpler to simply use a filtered view of Calendar A that only shows the events that require VTC rather than duplicate the data across separate calendars? Keeping the same data across multiple separate calendars requires extra maintenance to keep the two synchronized, it increases storage space requirements, and so on, basically it adds an extra layer of complexity that I’m not sure you really need.

As far as your workflow errors go, you haven’t quite provided sufficient information here to nail down the issue. Like what error message does it throw? On which workflow action does it error?

​@BobR Reason for the two calendars:

• Calendar A holds room reservations which may or may not require the use VTC
• Calendar B will allow users to request VTCs - where the VTC coordinators will assign a dial in number (not necessarily requiring a conference/meeting room)
• Calendar B will also receive direct VTC requests to include the Calendar A requests (as there are only a handful of numbers to be used at any given time). Intent is for Calendar B to hold all the different views of the different assigned numbers to facilitate assigning of dial in numbers

I use the create list item action for Calendar B - which basically has the same fields as calendar A

• date/time variable is used for the start and end date
• yes/no variable is used for “Recurrence”, “All Day Request”, and other yes/no questions

Is there a trick when copying/creating an event from one calendar to the next for recurring and non-recurring events?

Recurring events can be messy through workflow, the reason being that all separate occurences in a series of events share the same ID and metadata, Nintex basically just sees the entire series as a single event. I’m not sure if Nintex even supports creating events with recurrence through workflow. If you search the internet you might find some methods to extract individual occurrences from a series in workflow, but I never got any of them to work and all of them are quite advanced.

I would definitely investigate if it isn’t possible to just use a single calendar, perhaps with different content types on the calendar, rather than splitting it. There’s not really much of a limit on number of views on a list or calendar, I’ve got lists with hundreds of views. If you absolutely must use separate calendars, try using the same columns across both by storing them as site columns, and then use the Copy Item action in workflow. Copy Item copies items between different lists and brings along metadata between matching columns, as long as the source list and destination list are on the same site. It might work to also carry across recurrence information, likely better than Create Item. Note that content types need to match between the two calendars for Copy Item to work.

​@BobR - thanks for the response. I was able to use the create item and copy over All day events and single events to the second calendar.  However, to your point, the recurring event is an issue. Although I created a yes/no variable for the “Recurrence” field - I am unable to update the “recurrence” field on Calendar B as it states it’s the wrong type.

The problem with using the single calendar is that I have 10+ different conference rooms and given there is a max on calendar overlays (10), it made sense to create individual calendars and thus each of these calendars may have meetings with VTCs---thus the need to transfer those specific events to another calendar just hosting VTC events.

I see that I’ll have to find some other solution for the recurring events. Thank You.

Recurrence is a complicated column. If queried or shown in the views it just looks like a yes/no boolean, but it contains a lot more information internally about the kind of recurrence. Is it weekly, daily, the first Friday of the month, whatever. Just writing Yes to a recurrence column will make Sharepoint throw an error, it needs the recurrence details to construct the individual occurences, and I don’t think it’s even possible to write those details in Workflow with Create Item.