Unable to create a new customer on RTC

iqbalmad

Hi guys,

On the customer card, i have defined number series which can be both manual and automatic.
This works fine on navision classic.

However if i try to create a new customer (manual one) on RTC, it gives me an error - "No. already exists".

Can you advise please?

Thanks

mohana_cse06

iqbalmad wrote:

Hi guys,

On the customer card, i have defined number series which can be both manual and automatic.
This works fine on navision classic.

However if i try to create a new customer (manual one) on RTC, it gives me an error - "No. already exists".

Can you advise please?

Thanks

The No. which you are tring to create is already exists in Customer table.
try with different No.

iqbalmad

hi mohana..

i have eight years experience in NAV.. dnt you think i would have checked if the customer no. exists already!!!

mohana_cse06

iqbalmad wrote:

hi mohana..

i have eight years experience in NAV.. dnt you think i would have checked if the customer no. exists already!!!

Sorry, if you felt bad with my solution

Belias

iqbalmad wrote:

hi mohana..

i have eight years experience in NAV.. dnt you think i would have checked if the customer no. exists already!!!

how could we know it? :-k anyway, back to your problem...

it seems a custom error. (otherwise, as you know, nav should have said "The record already exists.")
If it works in classic client, try to check:
- if the RTC is reffering to the same database as the classic client
- if there's some custom ISSERVICETIER instruction, and what does it do in that "IF"

if you still get the error, try to create a new and fresh page, based on customer no. and try to insert a new record in that page. If you get the error, there's some wrong code in the table (but i guess not, if the FORM works), otherwise double check the properties and the code in the page.

frost_amo

Such problem can appear because of different behavior of classic forms and RTC pages. I suggest you to check is there any customization in OnInsert trigger of the Customer table... and if it is, it can be the reason of such error.
Unfortunatelly I cannot suggest any concrete solution, because it depends on customizations you have.