Skip to main content

An attempt was made to add a duplicate entry FS300200. In default UI 2025R2.

  • September 10, 2026
  • 2 replies
  • 17 views

Hi there,

 

Im also met this strange behaviour, and im confused why this happends. 
Part 1. Story + Default UI

 

This issue caused by FSAppoinmentDet.LineRef. For some reason, in default UI while i inserting rows in Details whithout saving everything is good.
 

 

Case 2. If i insert 1 line. Save Doc. Trying to insert next line(without page refresh.). 

As you see here, line ref duplicated and it`s obvious that i will recieve this error here.

If i repeat this case, but with page refresh(ctr + r). Ref nbr on row init defaults as expected. 


I got this behaviour if i publish 2 cusomization. This customizations don`t interferring with events of insert or defaultings. in both i have only row selected( Events.RowSelected<FSAppointment> e ).
In case if 1 of those was published everything ok. You can assume, that i partially find source of issue. 

Part 2. MUI

If i repeat any of cases from previous part, everything will work as expected. without any errors.
I understand thats it`s two different Web application architectural patterns.

 

But maybe something also unpredicted here? 

Same customizations works in MUI but broking in default ui?

Can someone explain me this behaviour of old UI?

 

2 replies

Forum|alt.badge.img+4
  • Captain II
  • September 10, 2026

Temporarily remove the code inside both RowSelected<FSAppointment> events.

If the issue still happens, the problem is likely related to the two customizations working together.

If the issue goes away, something in the RowSelected code is causing it.

Change the order of the two customization projects and publish again.
If the issue changes or disappears, the order in which the customizations are loaded may be causing the problem.

Debug FSAppointmentDet.LineRef when adding the second line after Save.
Check whether LineRef is getting the wrong value.
Also check whether the defaulting logic is running at all.


darylbowman
Captain II
Forum|alt.badge.img+17
  • September 10, 2026

If you provide the code in both RowSelected handlers, we may be able to help. RowSelected is usually not the correct place to be running code because it fires many times in a graph’s lifecycle.