cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Instance with the same key already exists....(PaymentData)

Former Member
0 Likes
1,958

Hello there,

I have a problem with the node element PaymentData. I don´t understand this message.  If I remove it, it functions. It also works with any other element. Anyone who can help? Thank you!

Best Regards,

Rufat

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Likes

Hi Again

If the payment data is already available then you should get this error. hope you are aware of the action codes. 01 is for create. i.e. it will try to create a new node instance with the provided data. if you use 04 then system either create or change the existing node instance. i.e. when a node is available with the same key, it will change/modify that instance. otherwise, it will create a new node instance.

Best regards,

Hari

Former Member
0 Likes

Hi Hari,

thank you for your great support!!!

How can the payment data be already available if I haven´t created a supplier instance who hasn´t payment data? I have tried the same request with ManageCustomerIn. There, I have no problems.

Yes, I am aware of the action codes. I tried with "04" and "01". No success .

Do you have any sample request for ManageSupplierIn with payment data where it works?

The other elements work without problems!

Best Regards,

Rufat

Former Member
0 Likes

Hi Hari,

I don´t know If you have already seen the screenshot in my posting above. There you can see that I don´t have specified the Internal ID and haven´t created a supplier with PaymentData but I try to.

Best Regards,

Rufat

Former Member
0 Likes

Hi Hari,

ok...Yesterday, I had a meeting with another partners. It is obviously a bug in FP4.0.

The problem with paymentData doesn´t exist in Release 1302. I´ve tested it and it worked very well!

Best Regards,

Rufat

Answers (1)

Answers (1)

Former Member
0 Likes

Great that you found the reason. I too tried on the same day and got the same error. I thought of asking you to raise an incident as we are not making any mistake in the request xml. Anyways, thanks for the info

Beset regards,

Hari