Finance | Project Operations, Human Resources, ...

Relation between two fields is not working when inserting records via x++

(0) Share

Report

Posted on by ..

2,011

Hi,

I have a parent table (TableX) with mandatory (Field1) which is also an index with allow duplicate No.
This Field1 has an EDT, which has TableRelations and TableReferences Nodes filled for it.

Now I created a new table(TableY) which has Field1(same Edt). Field1 in this table is not unique and not mandatory. It also has ignoreEdtRelation = true.
I also created a relation between these two tables on TableY based on Field1.

When I open the form for TableY, and try to fill Field1 with a value that doesn't exist in TableX, it doesn't allow me. it only allows empty value or an existing value from TableX -- which is the expected behaviour because of the relation.

However, If i try to insert a record for TableY by code, where I fill Field1 with a value that doesn't exist in TableX -- it allows me to do so... why is that? how can i prevent that and make it work like it works from the UI?

I have the same question (0)

All responses (4)

Answers (0)

Sort by

Martin Dráb 240,198 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Didn't you forget to call validateWrite() method and check its result before inserting the (potentially invalid) record?

Was this reply helpful? Yes No
.. 2,011 on at

Like (0)

Report
Copy link

Link copied!

Hi Martin,

I'm calling validateWrite before adding to the recordInsertList and it's not working--- but do you mean i need to put this validation inside the validateWrite or should it work by itself?

Was this reply helpful? Yes No
Bharani Preetham Pe... 3,634 Moderator on at

Like (0)

Report
Copy link

Link copied!

Ideally if you call validatewrite() then if there is some relation, it should give error even without giving code in validation if it is defined at table level. If it is not working means have you written code like skipdatamethods(true); something like this? Can you send your code?

Was this reply helpful? Yes No
Suggested answer

Martin Dráb 240,198 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

The system doesn't automatically make extra SQL statements to check the validity on saving. If the values come from an unreliable source, your code normally should validate them before using them.

When you already have in your table buffer, you can validate them with validateField(), which checks the related table too. That's the method that forms call when you modify a value of a field (even before saving the record).

If you wish, you call validateField() from validateWrite() as well.

Was this reply helpful? Yes No