Each maker at a company has a separate Common Data Service environment. You are customizing a canvas app. You create two new entities in your environment.
You are leaving for a vacation. Another maker will continue customizing the app in your absence.
You need to transfer the work to the other maker and ensure that you can work on the updated app when you return from your vacation.
What should you export?
To ensure that another maker can continue customizing the app in your absence and that you can work on the updated app when you return, you should export an unmanaged solution that includes all customizations. An unmanaged solution allows for ongoing editing and updating of the app and its components, including the newly created entities. This flexibility is necessary for both makers to apply further modifications as needed. In contrast, a managed solution would not allow for further editing, and exporting just the app would not include the newly created entities.
Answer A, Unmanaged. Correct
Answer A is the correct one.
According to the Microsoft Power Apps documentation, when leaving for vacation and transferring work to another maker, you should export an unmanaged solution that includes all customizations . This will allow the other maker to continue customizing the app in your absence. When you return from vacation, you can import the updated solution back into your environment and continue working on the app.
Unmanaged of Course. They told that he needs to work on the updated app. if the solution is managed it can not be edited.
Anser A is the correct one
Answer is correct
The best option to transfer your work to another maker and ensure you can both work on the app later is: **A. an unmanaged solution that includes all customizations** Here's why the other options are not ideal: * **B. Default solution:** This solution contains the base functionality of the app and shouldn't be modified. Exporting it wouldn't include your customizations. * **C. Managed solution:** While it includes customizations, a managed solution restricts further editing unless you're both designated as co-owners. * **D. The app:** Exporting just the app wouldn't include the newly created entities needed for customization. An unmanaged solution captures all your customizations, including the entities, and allows the other maker to continue working on them. Upon your return, you can both import the latest unmanaged solution into your respective environments to work on the updated app.
An unmanaged solution that includes all customizations
You should export a managed solution that includes all customizations because this will allow the other maker to continue customizing the app, but will also track their changes and allow you to manage them through the solution's metadata. When you return from vacation, you will be able to work on the updated app by importing the managed solution into your Common Data Service environment.
A is correct
Answer A
Not D. But A or C,not sure
A for me "Another maker will continue customizing the app in your absence."
correct answer is No --> https://docs.microsoft.com/en-us/ai-builder/model-types
The AI Builder was not mentioned in this question. It's only a "canvas app". ;-)
Why it shouldn't be -> D. the app ?
"You create two new entities in your environment." So answer A should be correct, in the unmanaged solution you can export both entities and app if you want, for the other Maker to edit.
There's nothing mentioned about a solution, it's just about the App. In addition, each maker has it's own environment and there's no mention of App makers owning multiple environments (which is requirement to work with solutions). I would therefore go with answer D.
Forget my previous statement, it's possible to export this as unmanaged and import it into another user's environment (regardless of the environment type). More importantly, you will have to work with a solution in order to include the new dataverse entities. So: Answer A.