There is no documentation about this scenario, but we will add such.
I set up custom fields on SiteA for ProviderA. When I switch to SiteA ProviderB, the custom fields automatically appear there as well. Is this expected behavior?
Yes, it is expected behavior, because a custom field is valid for the whole type not only for a provider. So every provider for events will use the existent custom fields.
If an event is created on SiteA for ProviderB, does this event get persisted in the database for SiteA or SiteB?
The event for ProviderB is persisted in the database for SiteB together with the data of the custom fields for events defined in SiteA.
If SiteB does not contain the custom fields defined in SiteA for ProviderB, where does this metadata go?
If you create a custom field in SiteA then the metadata about this field will be persisted in the database for SiteA. Though the data of the custom field will be persisted as a table column in SiteA and SiteB as well. In order for SiteB to see the data stored in its database you have to create a custom field with the same name and type in SiteB.
When I create an event on SiteA for ProviderB, the event does not show up on SiteB for ProviderB. This previously worked and I was able to create and share content across sites. Can anyone else reproduce this behavior?
Would you make sure that the ProviderB for SiteA and ProviderB for SiteB share the same application name?
the Telerik team
Explore the entire Telerik portfolio by downloading the Ultimate Collection trial package. Get now >>