> Mark, you're a fine human being!Depends on who you ask... ;-)
> I'm curious if you've gotten any feedback from Epicor on what writingExcept for the speed, I think it's exactly like using SC. I believe that
> code against the Business Objects does to your "support status". Will
> they completely punt on your problems if you touch the API in this
> manner? Seems like it should be equivalent to using Service Connect
WebServices are generated automatically with the SDK and no special code is
added "for your protection".
I would add that using the Business Objects is considerably safer than using
the Epicor supplied "update table buffer" program and certainly far safer
than using the unsupported ODBC or T-SQL path. It is no different than
buying the SDK and modifying the "Rich Client" I suppose.
> since the web services are fairly thin wrappers around the BOs, and theI don't have SC. Does the "helper code" just give you help on the parameters
> helper code (as I understand it) in the web services is mostly there as
> a convenience to save you some annoyance and effort.
and the types? If so, that is provided in Visual Studio too. If not, I'm
curious what it does do for the "webservice choreographer".
I guess Epicor can always claim user-inflicted damage to the database with
SC, BPMs, or customizations as well. But if the marketing literature is
accurate:
"Epicor 9 is unparalleled because it is designed for the way people work
today, is built for business, and is ready for change. Our strategy is to
provide both new and existing customers with unprecedented flexibility and
choice. It's about delivering business without barriers."
Why advertise a self-describing service oriented architecture when the only
person who's going to use it is the developer?
Mark W.