Skip to main content
Solved

Another process has added the 'INReplenishmentOrder' record. Please try again.


In screen Prepare Replenishment when pressing process this error Another process has added the 'INReplenishmentOrder' record. Please try again appears I have no customization at this screen.

Best answer by Vignesh Ponnusamy

Hi @mostafaahmed83,

In this scenario, you can start with the following troubleshooting steps

  • You can enable logging in the Request Profiler(SM205070), reproduce the issue, and check the trace to identify the possible root cause of the issue
  • Using the customization project test in your local instance 
  • Test without any customization to confirm it the issue is caused the customization or not

If the issue is caused by the customization project, you can debug by commenting the possible code that could be causing the issue. This is will help you narrow down to the exact method/code that’s causing the issue. Good Luck.!

View original
Did this topic help you find an answer to your question?

6 replies

Sagar Greytrix
Captain II
Forum|alt.badge.img+3

Hi @mostafaahmed83 ,

I have got This forum to answer your question. @Laura02, explained better for this issue.

Hope, it will help!

Regards,

Sagar


It is processes form does not contain save.


Vignesh Ponnusamy
Acumatica Moderator
Forum|alt.badge.img+5

Hi @mostafaahmed83, Can you please more details about the issue like,

  • Steps to reproduce the issue along with few screenshots
  • Does the issue occur all the time? If not share the specific scenario/step when it fails
  • Is the issue reproducible in local using SalesDemo data?

Being able to reproduce the issue will help us check this further. Thanks.!


1- it is occur on preparing every time.

2- It occurs all the time.

3-no it is on our live version.

We have many customizations on Sales order screen.


Vignesh Ponnusamy
Acumatica Moderator
Forum|alt.badge.img+5

Hi @mostafaahmed83,

In this scenario, you can start with the following troubleshooting steps

  • You can enable logging in the Request Profiler(SM205070), reproduce the issue, and check the trace to identify the possible root cause of the issue
  • Using the customization project test in your local instance 
  • Test without any customization to confirm it the issue is caused the customization or not

If the issue is caused by the customization project, you can debug by commenting the possible code that could be causing the issue. This is will help you narrow down to the exact method/code that’s causing the issue. Good Luck.!


Forum|alt.badge.img+8
  • Captain II
  • 362 replies
  • November 29, 2023

Hi @mostafaahmed83

 

Have you got any automation schedules which run in the screen?

 

I ran into the same issue when running an automation with my Shipments.

 

Hope this helps,

 

Aleks


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings