Issue with Extended Text (2009 R2 Classic)

beboelke · 2018-01-17

In 2009 R2 Classic when attempting to use Extended Text I encounter this the error shown in the image. However, the debugger will not trap the error, nor can you catch it using "breakpoint on triggers". There are no fields in either of the Extended Text table named code, and there is not a table in the database named "Standard Text" as reference in the error message. Any pointers are appreciated!

Slawek_Guzek · 2018-01-17

You have not entered anything in the Type field therefore the conditional relation on No. field points to the Standard Text table, where the PK filed, Code, is only 10 characters long.

The errors arising from relation constraints enforcement cannot be caught by the debugger as those are tested and enforced internally in the client, no C/AL code is involved.

You should have in your system table 7 Standard Text, it is a part of standard NAV database.

Slawek_Guzek · 2018-01-17

You have not entered anything in the Type field therefore the conditional relation on No. field points to the Standard Text table, where the PK filed, Code, is only 10 characters long.

The errors arising from relation constraints enforcement cannot be caught by the debugger as those are tested and enforced internally in the client, no C/AL code is involved.

You should have in your system table 7 Standard Text, it is a part of standard NAV database.

Issue with Extended Text (2009 R2 Classic)

Best Answer

Answers

Categories