I think that we shouldn’t allow to have the same name for different points in a control.
Because in an inspection of that control, it will only appear 1 of the points because the key (name) would be the same.
If you are agree, we could limit this with an sql constraint.
The name of quality control is translatable so it can not be enforced to be unique.
Another point is that we do not enforce such constraint without a technical requirement.
I mean the name of the control points, and this field is not translatable:
Regarding the technical requirement, I think that it can cause confusion, bacause you have 2 points at the control and in the inspection you will only be able to add 1 of them (always the last added at the control).
If you think that is not enough, I understand.
Ha you are talking about the dict schema.
So yes there should be a unique internal name per control.
I created an issue: Do not allow duplicated point names per quality control