Skip to main content

I built a custom app in a sandbox. I used #Zapier to connect my new Calendar Hold object to a Google calendar. It worked beautifully. It allows me to create/edit an event in Google and it automatically creates/edits a corresponding Calendar Hold record in SF.

 

I used #GearSet to deploy ( #Deployment Issues) my custom app to my production account. The calendar Hold object deployed successfully, and I can create a record manually.  Everything seemed fine until I tried to connect Zapier. The object Calendar Hold is not available in Zapier. All I have listed is Share: Calendar Hold. I tried using that instead, but it requires a parent and there are none. When Zapier was connected to the sandbox, both Calendar Hold and Share: Calendar Hold were present.

 

I'm not sure what the Share: Calendar Hold object is for or how it was created. When I run my comparisons in Gearset, the Calendar Hold objects are supposedly identical in the sandbox and production environments. 

 

Neither Zapier nor Gearset support knows how to help with this issue (they've both been great with other things). Is there something I can do in the Object Manager to fix this? Is my best bet to rebuild this object? 

 

Thank you!

 

This is a screenshot of Zapier connected to the sandbox. You can see both Calendar Hold and Share: Calendar Hold

Strange deployment involving Share: object

 

This is Zapier connected to production. 

 

Screen Shot 2021-09-09 at 3.45.58 PM.png

2 answers
0/9000