web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Pages / 'Opportunities' table ...
Power Pages
Answered

'Opportunities' table is missing from un-managed Dev environment (but exists in live)

(0) ShareShare
ReportReport
Posted on by 65
I am looking for some best practice advice.
 
I am using Power Pages (Dataverse) to create a public facing site, and i also create an Power Apps Admin portal in the same solution. 
 
I want to add some CRM features to the admin app and maybe the portal at a later date. Lets consider adding the 'Opportunities' table / views / Forms to the power Apps app.
 
In the live, managed App, i can add an opportuity to a contact, and i can browse the list of tables in 'make.powerpages' and find the 'Opportunities' table BUT in my Dev environment those tables don't exist. I need those tables in the Dev environment so that i can test flows etc. 
 
I want to tread carefully around this becuase i can't see how functionality has managed to get into Live becuase the only way that I update that site is by Solution Export, from the dev site? I would expect that the live site is a mirror of the dev site?
 
Any ideas why these two site would differ in this way? What is the best way to make sure that those tables are avilable in my un-managed, dev environment?
Categories:
I have the same question (0)
  • Suggested answer
    surya narayanan Profile Picture
    102 on at
    Hi,
     
    Best Practices as per my knowledge. Kindly check the below.

    1. Mirror Dynamics 365 Apps Across Environments
    If you plan to use standard CRM tables like Opportunity, Lead, Quote, etc., install the same Dynamics 365 app (e.g., Sales) in Dev.
    This ensures you can work with the same schema and forms.
     
    2. Add CRM Tables to Your Dev Solution Explicitly
    In Dev, go to your unmanaged solution.
    Use "Add Existing > Table" to add Opportunity, selecting all relevant assets (views, forms, columns, relationships).
    This way, when you export and import to Live, you ensure they’re part of the deployment.
     
    3. Manage Your Power Pages and Power Apps from the Same Solution
    This is good! Just make sure you manage dependencies carefully.
    When you deploy the managed solution to Live, ensure all needed tables and web roles/permissions are included.
     
    4. Use Environment Variables and ALM Pipelines (Optional)
    Consider setting up ALM (Application Lifecycle Management) using Power Platform Pipelines.
    This automates deployments and ensures consistent configuration between Dev, Test/UAT, and Live.
     
  • Verified answer
    Fubar Profile Picture
    8,361 Super User 2025 Season 2 on at
    In you installed an actual 'developer' instance (i.e. in the admin center it says the type = Developer, it is not just a non-production instance that you are calling dev), then the Dynamics 365 tables will not be present. You would need to add Sales etc to the instance.
     
    However, I would generally not recommend using an environment of type "developer" for actual development work but a non-production instance instead (as the developer environment also has additional restrictions, and so will not be 100% the same as your production environment etc).

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Forum hierarchy changes are complete!

In our never-ending quest to improve we are simplifying the forum hierarchy…

Ajay Kumar Gannamaneni – Community Spotlight

We are honored to recognize Ajay Kumar Gannamaneni as our Community Spotlight for December…

Leaderboard > Power Pages

#1
Fubar Profile Picture

Fubar 78 Super User 2025 Season 2

#2
Jerry-IN Profile Picture

Jerry-IN 75

#3
sannavajjala87 Profile Picture

sannavajjala87 31

Last 30 days Overall leaderboard