Developers can implement plug-ins and register them using the Plug-in Registration tool for each of the CRUD operation supporting the virtual table. Full CRUD operation is now supported for custom virtual table data provider. If a data provider cannot be found for your external data source, you can develop a custom virtual table data provider for more information, see Virtual table data providers. An Azure Cosmos DB (formerly Microsoft Document DB) provider is available from AppSource.This provider supports create, read (retrieve, retrieve multiple), update and delete operations. An OData v4 provider is included with the service and is installed by default.The following data providers ship with Dataverse: Each virtual table type is associated with a virtual table data provider and (optionally) some configuration information from an associated virtual table data source. Instead during runtime, when a record is required, its state is dynamically retrieved from the associated external system. Virtual tables, data providers and data sourcesĪ virtual table is a definition of a table in the Dataverse platform without the associated physical tables for records created in the Dataverse database. For more information about managing virtual tables from the user interface, see Create and edit virtual tables that contain data from an external data source. This section discusses the implications of virtual tables for developers.
0 Comments
Leave a Reply. |