+5hi,
We use a view in a detail tab where we combine two tables, a record can be added in the row. We use an instead of trigger to insert the records in het underlying tables. After adding the record, the message “saved data can not be displayed on this screen”, but surprise, the new record is shown!
Because of the two tables, two primary keys are added in this view, can this be the problem? Should I create a dummy primary key for this view?
Anybody an idea how to fix this?
Best answer by Tejo van de Bor
Support says it is working in 2024.1 so this issue is 2022.2 related. Will try myself when we level up to SQL2019.
+23Hi Tejo,
I believe the primary key can indeed result and prevent this behavior. Try and have a primary key from the List to Shipment package measurements that enforces a strong relationship. E.g. Shipment_id ↔ Shipment_id
+5hi
+5Support says it is working in 2024.1 so this issue is 2022.2 related. Will try myself when we level up to SQL2019.
+23Hey Tejo,
Great! Be sure to start preparing to upgrade as 2022.2 will go out of support after this month
+5Edit: Support could reproduce the same error in 2024.1, now waiting for hotfix or workaround.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
