简体   繁体   English

如何从多个解决方案合并Dynamics CRM功能区更改

[英]How Dynamics CRM Ribbon changes are merged from multiple solutions

We have two development teams working on seperate modules of the dynamics crm in different solutions, team A develops customizations in solution A, exports a managed Solution A, this managed solution will be imported on team B's dynamics development organization on regular basis, team B also develops customizations in unmanaged solution B and exports it as a managed solution when it will be given to customer. 我们有两个开发团队在不同解决方案中的动态CRM的单独模块上工作,团队A在解决方案A中开发自定义项,导出托管的解决方案A,此托管解决方案将定期导入到团队B的动力学开发组织中,团队B也在非托管解决方案B中开发自定义项,并在将其提供给客户时将其作为托管解决方案导出。

When everything is ready Customer can either import only managed solution A or managed solution B on top of managed solution A. 一切准备就绪后,客户只能导入托管解决方案A或托管解决方案B之上的托管解决方案B。

But Both solution A and solution B includes changes to the ribbons. 但是解决方案A和解决方案B都包含对功能区的更改。 I am wondering how these changes are merged. 我想知道这些更改如何合并。 Because in the above scenario team A's managed solution is imported into the development environment of team B. At this point Team B might have some unmanaged changes to the ribbon as well. 因为在上述场景中,团队A的托管解决方案已导入到团队B的开发环境中。此时,团队B可能还会对功能区进行一些非托管的更改。

I am wondering how does dynamics CRM merges these changes. 我想知道Dynamics CRM如何合并这些更改。 And I am wondering if there can be a case where changes in solution A can be overwritten by Solution B. Even though they are completely mutually exclusive. 我想知道是否存在解决方案A的更改可以被解决方案B覆盖的情况,即使它们是完全互斥的。

From what I deduce from customizations.xml, when I import a managed solution, I don't see any ribbon changes related to that solution in the customizations.xml any more when I just export an unmanaged solution that only contains application ribbon. 根据我从customizations.xml推论得出的结论,当我导入托管解决方案时,当我仅导出仅包含应用程序功能区的非托管解决方案时,我再也看不到与该解决方案相关的功能区更改。 Which makes me think that when I import a managed solution, those changes in the managed solution are merged into the application ribbon. 这使我认为,当导入托管解决方案时,托管解决方案中的那些更改将合并到应用程序功能区中。

Any information would be appreciated. 任何信息,将不胜感激。

As far as I've researched, entity ribbon changes are shipped along entities and they are merged automatically. 据我研究,实体功能区更改是随实体一起提供的,它们会自动合并。 Global Application ribbon and custom group changes are shipped under client extensions in the solution, as far as I've researched they are also automatically merged when to managed solutions are imported one after another. 根据我的研究,全局应用程序功能区和自定义组更改在解决方案的客户端扩展中提供,据我研究,它们在被托管的解决方案一个接一个地导入时也会自动合并。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

相关问题 Dynamics CRM 2011:托管解决方案或部署从DEV到PRD的更改 - Dynamics CRM 2011: Managed Solutions or deploying changes from DEV to PRD 从Microsoft Dynamics CRM 2015中的新SubArea删除应用程序功能区 - Remove Application Ribbon from new SubArea in Microsoft Dynamics CRM 2015 如何在ms动态CRM中的功能区中添加示例按钮 - How to add a sample Button inside Ribbon in ms dynamics CRM 如何在Microsoft Dynamics CRM中自定义“菜单”选项卡(功能区/命令栏)? - How to customize Menu tab (Ribbon/command bar) in Microsoft Dynamics CRM? Dynamics CRM 2016:功能区上有额外按钮的错误,如何修复? - Dynamics CRM 2016 : bug with extra buttons on the ribbon, how to fix it? 如何在Dynamics CRM 2016中基于表单禁用功能区按钮? - How to disable ribbon button based on Form in Dynamics CRM 2016? 如何将带有自定义服务器端处理程序的功能区按钮添加到Dynamics CRM Web? - How to add ribbon button with custom serverside handler to Dynamics CRM web? Dynamics CRM功能区操作顺序顺序 - Dynamics CRM Ribbon Action Sequence Order Dynamics CRM CrmServiceClient - 如何连接到多个组织? - Dynamics CRM CrmServiceClient - how to connect to multiple organisations? Dynamics CRM 2011部署/解决方案最佳实践 - Dynamics CRM 2011 deployment/solutions best practice
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM