When I try to enter Data in a Contact Related DataTable which was created by our Partner I get the following error:
Field: FieldName1 <– FieldName2
Table: Customer <– Contact
Type: Date <– Text
The error only happens for Contacts which have a Customer or Vendor connected to it. The two fields are for completely different purposes and are not related in any way so I dont know why the System insists that they should have the same type. When I delete one of the problematic fields, the error just takes another SOD created field and shows me that in the error message
We also dont have any field transfer between the two Tables activated.
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…
I did not post the complete error, sorry:
The following fields must have the same type:
Field: Gegründet am <– Dummyfeld Gruppe Einstellung
Table: Customer <– Contact
Type: Date <– Text
Internal session ID:
281b68a5-d71d-4cc9-a431-47e7e75aeaba
Application Insights session ID:
e1e11cb8-4236-471f-a7a1-83db77bf35ac
Client activity id:
58541f0e-df42-48c2-a32b-623583dd202c
Time stamp on error:
2025-07-15T11:51:03.3124920Z
User telemetry id:
c086b4cb-11b5-44e4-89ae-71be42e1893c
AL call stack:
"CustVendBank-Update"(CodeUnit 5055).CustCopyFieldsFromCont line 9 – Base Application by Microsoft version 26.1.33404.36353
"CustVendBank-Update"(CodeUnit 5055).UpdateCustomer line 13 – Base Application by Microsoft version 26.1.33404.36353
"CustVendBank-Update"(CodeUnit 5055).OnRun(Trigger) line 17 – Base Application by Microsoft version 26.1.33404.36353
Contact(Table 5050).DoModify line 13 – Base Application by Microsoft version 26.1.33404.36353
Contact(Table 5050).OnModify(Trigger) line 9 – Base Application by Microsoft version 26.1.33404.36353
"Contact Comm. Method"(Table 50007)."Main Number – OnValidate"(Trigger) line 28 -Partner Base Extension by Partner version 22.5.25.22