Small and medium business | Business Central, N...

How to Fix: The record in table Item Journal Template already exists. Identification fields and values: Name='PROD. ORDE'

(0) Share

Report

Posted on by Crystal Analyst

Dear BC Community

Explanation:

We have been using backend development to do frontend customization as the BC Customization functions does not hide all the fields that we require and this confuses new users. We have been editing Item Card, Suppliers List, Released Production Order cards etc. to give it a cleaner, neat look. We have not done any customization on Tables, we are using the original systems tables which are connected to our customized cards.

When opening the Released Production Order Card, populating the required fields, and try to open the "Production Journal" from the Lines functions we get the following error:

The record in table Item Journal Template already exists. Identification fields and values: Name='PROD. ORDE'

What could be the reason for this?

Thank-you for your assistance in advanced.

I have the same question (0)

All responses (6)

Answers (0)

Suggested answer

Nitin Verma 21,698 Moderator on at

Like (0)

Report

Hi,

Are you trying to create a New Item journal template? If yes, choose another name except 'PROD. ORDE'.

Was this reply helpful? Yes No
Suggested answer

Inge M. Bruvik 1,105 Moderator on at

Like (2)

Report

If you have a customization you should go back to your developers with this case. There is probably some bug in the code making the system trying to create something that is already there.

Give them a hint about if rec.insert then else :)

Was this reply helpful? Yes No
Alfredo_Iorio 1,262 on at

Like (0)

Report

This seems a programming error but it is unlikely caused by a hidden field.

BC uses the item journal template to post consumption, capacity or output when posting a production journal or when you change a production order status.

The error suggests that BC is trying to create a new record in that table when you open the production journal. Instead. It should pick up an existing record from either of these:

I would make a copy of your production environment in a sandbox, disable the extension and see if the error still appears.

If not, check the development.

Was this reply helpful? Yes No
Crystal Analyst 55 on at

Like (2)

Report

Thank-you for your feedback. I managed to get it fixed with your recommendations.

Was this reply helpful? Yes No
Crystal Analyst 55 on at

Like (0)

Report

Thank-you I appreciate the assistance.

Was this reply helpful? Yes No
Suggested answer

Inge M. Bruvik 1,105 Moderator on at

Like (0)

Report

[quote user="Crystal Analyst"]
Thank-you for your feedback. I managed to get it fixed with your recommendations.
[/quote]
Please click "Yes" to indicate that your question was answered. That helps other forum users.

Was this reply helpful? Yes No