Econnect and the UpdateIfExisting Parameter

(0) Share

Report

Posted on by Greg Kowieski

I have something odd happening with a custom xml.

I have an object called ibsCreateItemVendors. One of the properties is a public short UpdateIfExists {get; set;}.

if I leave this property uncommented, when I call the CreateEntity method, I get a "cannot convert string to booean" error.

Apparently it has nothing to do with my sql proc as the profiler doesn't show the proc even being called. I'd like to utilize this variable for consistency's sake in my sql code to update records like the standard econnect nodes.

Any ideas?

*This post is locked for comments

All responses (3)

Answers (1)

Verified answer

GovindDevda 615 on at

Like (0)

Report

RE: Econnect and the UpdateIfExisting Parameter

Hey Greg if you pass UpdateIfExists = 1 (Means that transaction is update into GP ) and 0 means not update. UpdateIfExists facility not provide all nodes in econnect.

and we talking about custom xml no Greg it's not possible because eConnect node already pre-define field property that fields only you pass in eConnect CreateEntity method .

if you have any other issue please let me know Greg.

Hope this helpfull for you !!!

Regards,

Govind Devda
Greg Kowieski 90 on at

Like (0)

Report

RE: Econnect and the UpdateIfExisting Parameter

Thanks for taking the time to help. What if I want my value to be zero meaning perform the anti of what the 1 does?

It seems like the UpdateIfExists may be a key word for econnect and perhaps we shouldn't include it in our custom code. Have you been able to utilize the property in your own custom xml?
GovindDevda 615 on at

Like (0)

Report

RE: Econnect and the UpdateIfExisting Parameter

pass the 1 value in UpdateIfExists field.

Regards

Govind Devda