Add the Field No. field to the New Fields list. Then make sure that those two fields has the same number (Gegrundet am and Dummy Gruppe Einstellung). You might have to shuffle numbers around a bit.
This is because Microsoft sometimes triggers an automated field transfer, but they’re not very good at matching what fields can be transferred.
The Field No. of both fields were identical (No. 50519) so I assumed you maybe meant that they should not be of the same No. which also would make more sense to me
Therefore I changed one of the fields then to the No. 50518 but the next error wanted to do a field transfer to a another field with the same No. on the Contact Card which I overlooked. I corrected that also and found 3 more fields which had the same No. in Customer and Contact Table.
After publishing it finally worked. Thank you 🙂
It seems very laborius to always manually make sure that the field No. in two linked Tables are not the Same. Is there any way around that? Maybe when entering a new field the system could check for such things and skip a problematic No. itself.
I also noticed that when I change the No. for a field, the placement on page is lost, because the subtable filters on the field No. The Data is still there in the Table but kind of “lost in space” until a new field is created with the same No. of the changed field. It would be more secure if the SOD also changed the data in the subtable
Yes, I ment they should have different numbers… The Simple Object Designer tries to get this right, but sometimes, depending on field creations, deletions etc.. it is possible to confuse it.
I’ll check the placement bug…