cancel
Showing results for 
Search instead for 
Did you mean: 
Reply

How production, test and development environments are created

When production, test and development environments are created:

 

1. Does one create three solutions within the same environment?

or

 

2. Create three separate environments?

 

If it is option 2, then are different Dataverse tables built for each environment?.

 

Thanks in advance. 

3 ACCEPTED SOLUTIONS

Accepted Solutions

3 environments.
When moving from test to prod do this as a managed solution.

 

Please Accept as Solution if it solves your question. Or just give it a Thumbs Up if it is helpful because this can help others.

LinkedIn: https://www.linkedin.com/in/charlie-phipps-%F0%9F%91%A8%E2%80%8D%F0%9F%92%BB-91338715b/
YouTube: https://www.youtube.com/channel/UChmFBGU1YKIU91sNMQ7buGg
Twitter: https://twitter.com/phipps0218

View solution in original post

timl
Super User
Super User

@HamidBee 

>> Okay If I've understood correctly. You create a test environment. In the test environment you create a solution. In that solution you create the app and similarly you create a production environment with a solution so that the apps could be moved from one environment to another. But if the App was built using a dataverse table in the test environment what happens to the table when it is moved into the production environment?. Do we need to make copies of it?.

 

To clarify your statement above, the typical workflow would look like this.

You create 3 separate environments - development, test, and production environments.

 

In your development environment, you would create a solution. In this solution, you would create/define your table. Within this solution, you can also create model driven or canvas apps that are based on that table.

 

Once your development task is complete, you would export this solution and import it into your test environment.

You would publish this solution in order to apply the changes to the test environment.

 

If the users are happy with your work, you would import the solution into your live environment and publish the changes.

 

Effectively, the process is based on a single working solution, rather than separate solutions in each environment. A solution contains only the items/table changes that you add to it. It doesn't contain the schema of all tables and objects in Dataverse.

 

If you were to publish a solution with table changes that are not in the target Dataverse database, the publish process will add those table changes.

 

Hopefully, that provides some clarification.

View solution in original post

timl
Super User
Super User

Hi @HamidBee 

Let's say you're in the test phase and you're using a single environment. It isn't possible to publish the changes in the test solution to the current environment, and to also publish changes in your development solution to the same environment because the changes in both solutions would overwrite each other. In other words, you can't concurrently develop and test in the same environment. Therefore, moving from environment to environment is the correct approach.

View solution in original post

11 REPLIES 11

3 environments.
When moving from test to prod do this as a managed solution.

 

Please Accept as Solution if it solves your question. Or just give it a Thumbs Up if it is helpful because this can help others.

LinkedIn: https://www.linkedin.com/in/charlie-phipps-%F0%9F%91%A8%E2%80%8D%F0%9F%92%BB-91338715b/
YouTube: https://www.youtube.com/channel/UChmFBGU1YKIU91sNMQ7buGg
Twitter: https://twitter.com/phipps0218

Every environment has it own Dataverse

 

So, I think that you have 3 environments with 3 dataverse tables

 

If you need additional help please tag me in your reply and please like my reply.
If my reply provided you with a solution, pleased mark it as a solution ✔️!

Best regards,

Gonçalo Nogueira

Check my LinkedIn!

My website!

My blog!

@Nogueira1306 , @phipps0218 Okay If I've understood correctly. You create a test environment. In the test environment you create a solution. In that solution you create the app and similarly you create a production environment with a solution so that the apps could be moved from one environment to another. But if the App was built using a dataverse table in the test environment what happens to the table when it is moved into the production environment?. Do we need to make copies of it?.

Yes. You need to create the table in the other enviroment. But you cna import/export the solution and the solution will contain the table

 

If you need additional help please tag me in your reply and please like my reply.
If my reply provided you with a solution, pleased mark it as a solution ✔️!

Best regards,

Gonçalo Nogueira

Check my LinkedIn!

My website!

My blog!

Okay just to confirm, Are you saying that when a solution is exported the dataverse in that environment is also exported with it?. @timl any help here would be greatly appreciated. 

timl
Super User
Super User

@HamidBee 

>> Okay If I've understood correctly. You create a test environment. In the test environment you create a solution. In that solution you create the app and similarly you create a production environment with a solution so that the apps could be moved from one environment to another. But if the App was built using a dataverse table in the test environment what happens to the table when it is moved into the production environment?. Do we need to make copies of it?.

 

To clarify your statement above, the typical workflow would look like this.

You create 3 separate environments - development, test, and production environments.

 

In your development environment, you would create a solution. In this solution, you would create/define your table. Within this solution, you can also create model driven or canvas apps that are based on that table.

 

Once your development task is complete, you would export this solution and import it into your test environment.

You would publish this solution in order to apply the changes to the test environment.

 

If the users are happy with your work, you would import the solution into your live environment and publish the changes.

 

Effectively, the process is based on a single working solution, rather than separate solutions in each environment. A solution contains only the items/table changes that you add to it. It doesn't contain the schema of all tables and objects in Dataverse.

 

If you were to publish a solution with table changes that are not in the target Dataverse database, the publish process will add those table changes.

 

Hopefully, that provides some clarification.

Hi @timl. Thank you for adding onto the discussion. I just have one follow up question. Where you wrote:

 

"A solution contains only the items/table changes that you add to it. It doesn't contain the schema of all tables and objects in Dataverse."

 

Does that still mean that any table in the solution is exported to wherever the solution is exported to and any table outside of the solution is not exported?. Also are tables in the solution also saved in dataverse?.

 

Also, I'm just curious, why can we not have the solutions all in one environment, would it be considered bad practise?. If so, why?.

 

Thanks in advance. 

timl
Super User
Super User

@HamidBee 

>> Does that still mean that any table in the solution is exported to wherever the solution is exported to and any table outside of the solution is not exported?. Also are tables in the solution also saved in dataverse?.

Yes, that's correct for both of those questions

 

>>Also, I'm just curious, why can we not have the solutions all in one environment, would it be considered bad practise?.

 

I'm not sure I understand the intent of this question, but if we imagine a solution as a container or 'vehicle' for moving objects and changes between environments, then it's necessary to import the solution into all target environments in order for us to publish the changes that are contained in the solution.  Is that the answer you're looking for, or did I misunderstand the question?

 

Thanks for clarifying the first part. For the second question what I mean is assume I have an environment and in that environment I have created three solutions. Solution one is a development solution, two is a test solution and three is a production solution. So all these solutions are in one environment. As I progress through the stages I copy the contents of the solution to the next environment. So instead of moving from environment to environment I move from solution to solution. Is this possible? If yes, should we do this?. If no, why is it not something we should do?.

 

Thanks in advance. 

Helpful resources

Announcements

Community will be READ ONLY July 16th, 5p PDT -July 22nd

Dear Community Members,   We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd.   During this period, members will not be able to Kudo, Comment, or Reply to any posts.   On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities.   What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!

Summer of Solutions | Week 4 Results | Results posted on July 24th

We are excited to announce the Summer of Solutions Challenge!   This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions in the Forums to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**   Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersNumber of SolutionsSuper UsersNumber of Solutions @anandm08  23 @WarrenBelz  31 @DBO_DV  10 @Amik  19 AmínAA 6 @mmbr1606  12 @rzuber  4 @happyume  7 @Giraldoj  3@ANB 6 (tie)   @SpongYe  6 (tie)     Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersSolutionsSuper UsersSolutions @anandm08  10@WarrenBelz 25 @DBO_DV  6@mmbr1606 14 @AmínAA 4 @Amik  12 @royg  3 @ANB  10 @AllanDeCastro  2 @SunilPashikanti  5 @Michaelfp  2 @FLMike  5 @eduardo_izzo  2   Meekou 2   @rzuber  2   @Velegandla  2     @PowerPlatform-P  2   @Micaiah  2     Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Week 3:Community MembersSolutionsSuper UsersSolutionsPower Apps anandm0861WarrenBelz86DBO_DV25Amik66Michaelfp13mmbr160647Giraldoj13FLMike31AmínAA13SpongYe27     Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Week 4:Community MembersSolutionsSuper UsersSolutionsPower Apps DBO-DV21WarranBelz26Giraldoj7mmbr160618Muzammmil_0695067Amik14samfawzi_acml6FLMike12tzuber6ANB8   SunilPashikanti8

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners.    The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights.    Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.    

Updates to Transitions in the Power Platform Communities

We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for.  We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer.   Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together.   Here's to new beginnings and endless possibilities!   If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport.   To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages

Top Solution Authors
Top Kudoed Authors
Users online (4,442)