如果进行多次自定义，我们应该如何在同一屏幕上放置字段或控件 [英] How should we place fields or controls for same screen if multiple customization
问题描述
我有一个场景，其中同一屏幕在不同的自定义中被多次自定义.一种定制是由我完成的，而另一种则是由不同的人完成的.
I have a scenario where the same screen is being customized multiple times in different customization. One customization is done by me and others are by different people.
现在，我遇到了将控件放在表单上的问题.
Now, I am running into an issue of putting my controls on the form.
定制级别会有所不同吗?在这种情况下，在表单上创建自定义字段或控件的最佳实践是什么?
Does the level of customization will make difference? What are the best practices of creating custom fields or controls on the form in such scenario?
例如，请参见下面的屏幕截图-
For Example, see below screenshot--
推荐答案
这确实是个案.不同的自定义，需要不同的方法.为简便起见，我们将配置称为C1和C2.
It's really a case by case matter. Different customizations, different approach required. For sake of brevity let's call configuration C1 and C2.
-
在最佳情况下，C1和C2可以很好地发布 设置水平.一切都很好，无事可做.
Best case scenario, C1 and C2 publish fine without having to set levels. All good, nothing to do.
发布时遇到冲突，在将C1级X和C2级X + 1设置为不同级别后，它可以很好地发布.很好，只需要设置级别即可.
You have a conflict when publishing, after setting different levels C1 Level X and C2 Level X+1 it publish fine. All good, just need to set levels.
使用级别进行发布时发生冲突，在交换级别设置C1级别X + 1和C2级别X后，它可以很好地发布.很好，只需要设置级别即可.
You have a conflict when publishing with levels, after swapping levels setting C1 Level X+1 and C2 Level X it publish fine. All good, just need to set levels.
检查合并两个定制的可能性，这通常是业务/管理决策，而不是技术问题.如果可能的话，一切都很好，只需合并自定义项即可.
Examine possibility of merging both customization, this usually is more a business/management decision than a technical issue. If possible, all good, just merge customizations.
您遇到的冲突无法通过级别或合并自定义项来解决.您将必须找到一种解决方法，这是逐案处理的，解决方法将在很大程度上取决于控件的自定义位置/位置.
You have a conflict that can't be fixed by levels or merging customizations. You'll have to find a workaround, this is a case by case matter and workaround will depend heavily on what/where the controls are customized.
您可能会遇到麻烦的一种情况是删除/重新创建容器"控件.避免删除现有容器并重新实现它们.添加一个新的就可以了，如果2个自定义项使用它，您只需要调整级别即可.容器控件是自定义中的父节点，红色为图片，绿色为子级，不易发生冲突:
One scenario where you could run into trouble is when you delete/recreate a 'container' control. Avoid removing existing containers and re-implementing them. Adding new one is fine, you'll just have to adjust level if 2 customization use it. Container controls are the parent node in customization, in red in picture, the green ones are the child and are less prone to conflict:
这篇关于如果进行多次自定义，我们应该如何在同一屏幕上放置字段或控件的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
