• Solutions are used to transport apps and components from one environment to another.
  
  
• They are ideal for implementing application lifecycle management practices by moving items from Dev and then into Test and then introduced into Production instance.
  
  
• They can be exported to a zip file and imported across environments, even in different tenants.
  
  
• They contain existing items as they are a container with references.
  
  

• There are two types of solutions – managed and unmanaged.
  
  
  • Managed solutions cannot be edited, whereas an unmanaged solution can be edited.
    
    
  • Managed solutions are typically a base solution, such as Sensei IQ coming from Sensei and then you as a client would create an unmanaged solution to do your own customizations.
    
    
• There are two out of the box solutions:
  
  
  • Common Data Service Default Solution, which is available in case you need to make customizations; however it is highly recommended to create your own solution to make customizations.
    
    
  • Default Solution contains all components in the system which is useful when viewing all items in your system but not to make changes.
    
    
• Each solution uses a Publisher which provides a unique prefix to all objects.
  
  
  Tip: You can then easily identify where that object came from by viewing the publisher prefix in the name.
  
  
• Solutions have a lifecycle with choices of create, update, upgrade, or patch, when you make updates to your solution.
  

• Using Solutions allows you to layer in changes effectively.
  
  
• Managed solutions are the base configuration and then unmanaged solutions lay on top of that.
  
  
  Important: If there is a conflicting change in both managed solution and unmanaged solution, the unmanaged one will take precedence.
  

• Sensei IQ uses a few managed solutions.
  
  
  • Kaizen solution contains all items that are not dependent on a schedule execution tool such as issues, risks, key dates, etc.
    
    
  • IQ Atsumeru solution is schedule execution tool independent and has its own project table (sensei_project).
    
    
  • IQ PFTW solution relies on the Project for the web entity from Microsoft.
    
    
    Important: Both IQ Atsumeru and IQ PFTW solutions have a dependency on the base Kaizen solution.
    
    
  • Sensei Controls that stores all Power Apps Component Framework controls and other custom codes.
    
    
    Important: These solutions are delivered to each client using a Continuous Integration/Continuous Deployment process using Azure DevOps and can be managed by the client from the Sensei Hub. Clients can then create their own unmanaged solution for any customizations they want to make. Our recommendation is to call this solution Sensei IQ Enhancements with a publisher prefix of iq.
    

• Solutions can be exported and imported using a simple zip file format.
  
  
• To export your solution, click within your solution name and choose the Export button from the ribbon. This will give you some prompts about if you want it managed or unmanaged and a version number and the result will be a zip file.
  
  
• To import this solution in another environment, go to Solutions then choose Import from the ribbon and choose the location on the local disk where you stored the zip file. There is no need to extract the zip file during this entire process.
  
  

Learn how all these solution elements fit together:

_{Disclaimer: The instructional video contained herein is an excerpt from a recorded live virtual instructor-led training session. Some images contained therein may appear different from (or not available) in your organization’s Sensei IQ instance due to specific custom configurations and/or continuous solution updates. Ensure that you are already an enabled user in the Sensei.IQ for Project application and check out the What’s New page. Contact your system administrator for any assistance.}