You create functionality for a company. The functionality includes a Microsoft Dataverse table with a form for data entry. The functionality will be distributed to other lines of business in the company, each with its own Dataverse environment.
New forms must not be created in order for updates to the functionality to work correctly.
You need to package the new functionality for distribution.
What should you do?
A managed solution is used to deploy to environments other than a development environment, such as test or production environments, ensuring that the distributed functionality remains consistent and tamper-proof. To prevent the creation of new forms, you'd need to disable form creation on the table by configuring the managed properties. This ensures that the updates to the functionality will work correctly without interference from additional forms.
In my opinion it must be C ("use unmanaged solution and include..."), because you can not add or include forms to a managed solution. First you have to put it in an unmanaged solution and then export it as a managed solution.
I agree
I believe the given answer is correct. You do not have to put it in an unmanaged solution first, you can create the solution as a managed solution from the start.
I tested and I was wrong. You have to select an unmanaged solution first then export as a managed solution. I agree that the answer is probably C.
C is correct. package up in unmanaged solution and export as managed. you can't package anything in managed solution
I am going to go controversial here and say I agree with the given answer of 'B'. This is about packaging, your developing functionality so you would already be in the DEV environment and would already be using an unmanaged solution. You package it using a managed solution, because all environments outside of DEV should be managed.
D is the only one that makes sense, B is not good enough, if you don't disable creating new forms, then you can create unmanaged forms for an entity regardless if it was imported in managed solution or not and the question clearily stated that it should not be possible. Therefore D with 100% certainty
We need to package the solution and make sure that no new forms are created. A managed solution will prevent anyone from creating new forms and adding them to the solution. So the answer is B.
I am quite confused. I took a sample test from the Microsoft ESI portal and one of the questions regarded adding the said table to an unmanaged solution in the PROD environment and then creating a new form. Although this is an example of bad procedure, it does put into perspective that just importing as a managed solution would not prevent users from creating new forms. Answer D would make more sense to me, since you can always disable the form restriction from the original unmanaged solution & upload a patch.
Manage properties could be used to restrict creation of new forms https://learn.microsoft.com/en-us/power-apps/maker/model-driven-apps/managed-properties-views It could be also a patch solution but we don't have too much context, so I would say D..
per chat gpt: Managed solutions are typically used for distribution to other environments. Including only the needed form in the managed solution ensures that the required components are packaged for distribution. Disabling the ability to create new forms for the table is not necessary if you include the needed form in the managed solution.
It must be B.
C : all changes should be made in the unmanaged solution the managed solution is exported only for deployment
There are several mentions in this discussion about a Production environment. There is no mention of this in the question.
The answer is B. Because managed solutions are used for finished solutions, and then you can distribute it to other environments. Unmanaged solutions are used during the development phase when you are actively building/customizing solutions.
In the Power Platform, components are packaged in unmanaged solutions and then exported as managed solutions for distribution. So, the corrected answer is: C. Use an unmanaged solution and include only the needed form.
This is about distribution settings (so I assume that you have created an unmanaged soulution in dev. and are about to package it for managed export.). You can set settings for entities to be non-customizable. Therefore i would vote for D. Use a managed solution and disable the ability to create new forms for the table. but what if such a solution defines standard tables like contact, account non customisable? Blocking all dev. teams...?
seems B
Every new created solution is default unmanaged, then add components, export and import managed or unmanaged It depends how the enviroments are setup, some work with everything unmanaged, some managed. Ms promotes using managed solutiions. I go for B, stating that what is meant here is the export and import as a managed solution, knowing that the new created soltion unmanaged is as default
D since you can disable creation of new forms on the entity with the Manged Properties on a solution.
It's D as it delivers all the requirements in the brief. Configure the 'Managed properties' of the solution: https://learn.microsoft.com/en-us/power-platform/alm/managed-properties-alm