Skip to main content

Microsoft Power Apps and Oracle


Gartner Sales Force

Recently I was demonstrating a Microsoft Power Apps solution and I was asked what options are available for handling data in Oracle along with Power Apps. Can Oracle be migrated to Power Apps and Dataverse? Can Power Apps access data stored in Oracle?  Can I use Power Apps to replace Oracle Forms?

Like Oracle, Power Apps offers both a front end user interface and a database (Dataverse).  This post introduces some options on how Oracle data can fit with Power Apps as well as some migration paths to get to Power Apps from Oracle. Microsoft offers a Power Apps connector for Oracle 

First, a reminder that there are two kinds of Power Apps: model-driven apps and canvas apps. Model driven apps store their data in Dataverse, the repository used by Power Apps and Dynamics 365 apps such as Sales, Marketing, Customer Service and others. Model-driven apps give a more complete low code environment for solution development, and are tightly integrated with the Microsoft Cloud. There is no option to designate Oracle as your repository for model-driven apps in lieu of Dataverse.  Therefore you could migrate Oracle data to Dataverse or set up replication between the two databases.  

Canvas apps can connect to hundreds of data sources, including Oracle.  The Oracle Database connection can list tables, create, read, update, and delete table rows in an Oracle database as well as supporting full delegation of filtering, sorting, and other functions.  The Oracle Database connection does not currently support  triggers or stored procedures.

Another approach is to use an integration platform like these:

Integration would allow you to have two databases and synchronize data between them.  The integration platforms provide orchestration of the data movement, enhanced error handling, and sometimes pre-built data maps for some data sources.  

Integration provides additional flexibility even if you are planning to migrate in the long run.  It allows you to run both systems concurrently and move over gradually rather than all at once.

Popular posts from this blog

Key Concepts for Microsoft Dynamics 365: Tenant, Instance, App and Solution

To understand Microsoft Dynamics 365 (formerly Dynamics CRM), you need to learn some new terms and concepts that may be a bit different from what you know from databases and solutions that are hosted on premises. This post introduces some of the key terms and how these concepts are important for planning your implementation. While Dynamics 365 is available on premises, it is most commonly deployed on the Microsoft cloud.  This blog post discusses only cloud implementations. Microsoft has multiple clouds such as commercial and government community clouds. We start with a Microsoft tenant .  A tenant is the account you create in the Microsoft Online Services environment (such as Office 365) when you sign up for a subscription. A tenant contains uniquely identified domains, users, security groups, and subscriptions.  Your tenant has a domain name of .onmicrosoft.com such as acme.onmicrosoft.com.  User accounts belong to a tenant, and subscriptions are assigned to user accoun

Understanding Dynamics 365 and Office 365 Admin Roles

Managing Dynamics 365 instances If you run Microsoft Dynamics 365 (formerly Dynamics CRM) in the Microsoft cloud, you need to understand how your Dynamics instances relate to Office 365 and choose which of your administrators receives which roles and permissions to manage Dynamics 365. In on premises deployments, your network administrator would create and delete user accounts.  The Dynamics 365 admin would then assign permissions to users in Dynamics 365. This post explains three administrator roles: Office 365 Global Administrator Dynamics 365 System Administrator Dynamics 365 Service Administrator You may think that the Dynamics 365 system administrator would have power to do all the actions needed to manage Dynamics 365, but this is not the case. What's different in Microsoft cloud deployments is that licenses and user accounts are managed in Office 365 by an Office 365 Global Administrator.  This role is analogous to a network administrator for an on premises

Replacing Microsoft InfoPath with Power Apps

Source:  https://powerapps.microsoft.com/en-us/infopath/ Microsoft has offered a number of forms automation products over the years, and the most long running was InfoPath which was released as part of Office 2003.  InfoPath is a powerful and flexible product that stores user data in XML while offering form features such as rules, data validation, scripting, and integration with SharePoint.  The popularity of SharePoint resulted in many organizations standardizing on InfoPath for forms, especially internal forms which are hosted on an intranet such as employee reviews, leave and payment requests, and human resources forms. Microsoft has discontinued InfoPath, with mainstream support ending July 13th, 2021, and extended support ending July 14th, 2026. Microsoft has named Power Apps as the successor to InfoPath .  Power Apps has much in common with InfoPath.  Both products include integration with SharePoint.  Both are geared toward the citizen developer and do not require advan