Venting - Poor BO Service Documentation

(Caleb Grundmeier) #1

I just spent quite a bit of time troubleshooting an updatable BAQ that essentially adds/updates Price List Parts and Breaks.

The Designer gives you two options.

So I choose Erp.PriceLstParts because the query actually matches pretty logical to the DataSet. I get everthing mapped, run/edit and click update. And then the BO error comes up “Can not Create” or “Can not Update”. So I go to the BL tester to see if I can get it to work there. Same Errors. I go to the REST page and try it there, same errors. If finally decompile the darn thing to see what the heck was going on. Come to find out that the service will throw a BO Exception for Add, Update and Delete! Yet it still has and visible public Update and UpdateExt Methods!

I guess my point is, why does Epicor expose those methods and let us choose it if you can’t actually do anything with it?!?

(Joseph Moeller) #2

I hear you on this, Caleb. There’s a cool document available on EpicWeb called ERP_BO_Ref.chm that contains a breakout of all the methods with descriptions. Some of the method descriptions say things like “this is obsolete, do not use it”… some are very nice and detailed… However, the descriptions are by and large incomplete (for instance, pricelist has no descriptions). I’d like to see Epicor update this very diligently and then offer this up as the developer bible.

I’ve certainly wasted a lot of time trying to use obsolete methods or methods that do things they shouldn’t do, but I get that Epicor may leave them in there as to not break legacy customization setups at the point of compiling. If you want to compile something during an update and the file isn’t there at all, it leaves you in a different layer of troubleshooting the problem.

(Bart Elia) #3

That pain is well felt internally as more teams are building on new clients to E10 - Consider Social, Search, Infoworker, ECC, FSA, Mobile CRM, etc. All have had the same need you have so a lot of discussion around this has been occurring.

The first efforts in this area are being targeted at our partners and they are giving us some feedback on areas so docs and simplified APIs have been getting tried. No roadmap but the pain points are well understood. As new Kinetic apps come online over the next months and years, I’d hope we have a more coherent approach on this.

No delivery vehicle to announce but the intent is clear on need.

(Olga Klimova) #4

Designer just shows objects with suitable dataset automatically.
It does not know if update is suppressed internally in the code and not intended to be used.