Lee,
If you set a trace on a Part Description search, it may show you the format for the Where clause there.
Mark W.
1 Like
whereClause is SQL Style Field=XX
1 Like
Thanks Guys… for some reason I was over thinking it all- I didn’t even consider that it would be the same as the SQL standard! /FacePalmsSelf 
2 Likes
How are you performing the GET request using the URL in your code? I’m trying to use $.ajax() in a simple test intranet page but am having issues retrieving the data.
Any assistance you might be able to provide would be helpful!
Thanks,
Ben
1 Like
Use PostMan application for your specific language it will give you the code. If you are using jquery there will be plenty of examples online of how to perform an async get request using ajax. Make sure you use the RestAPI documentation pages within the application for the URL paths you need to call copy and paste makes life easy.
1 Like
Thank you for the PostMan recommendation. That’s a great tool! I’m able to get it to work in the Chrome version with no auth, and in the native version with SSL-verification disabled, but not in my test script. I’m wondering if my problem is on the server side. I’ve tried everything I know of but I keep getting either 400 preflight request errors or 401’s.
Anyway, thanks for your helpful response. I’ll keep chipping away at it!
Ben
1 Like
Sorry if I’m way behind, but we finally got our DEV environment configured to accept SOAP API calls according to the example in the WCF developers guide.
Is there any harm in trying to setup the REST API preview in addition to the SOAP configuration?
I would hate to start developing our integrations in one way if another way is the future/preferred way.
1 Like
You should have no problem running both.
1 Like
Does the payload still go through the Epicor business logic layer or does it hit the database directly?
1 Like
Goes through the normal channels like any other external service Epicor provides just like the webservices.
1 Like
All the endpoint stuff is correct as said above. Check out the ‘networking options’ in the help. We did a lot of work in there explaining why to choose what, etc.
We use WCF for the standard clients - choose one of each - net.tcp, http, https.
For REST we use a different url endpoint (Note the /api in the url) and use WebAPI, not WCF.
Both of these technologies route to the same business objects. The wrappers change, the BOs stay the same. Over time we are talking internally about some REST optimized routes through the server but nothing to advertise at this time.
1 Like
Comments are my own and not an endorsement by my employer 
2 Likes
Ended up being a silly web.config problem on the intranet side. All works fine now, thanks again for your help!
2 Likes
This is really cool thanks for sharing. I plan to use this.
I have found a bug in the help when using the “Switch to Custom list” link I get an unresponsive script message, at this location.
api/help/odata/Erp.BO.JobEntrySvc/index
Is there someplace ww can submit bug reports?
1 Like
There is a timeout issue we are working on that Swagger takes forever to build the help page meta for huge services - lots of methods, lots of tables, lots of columns. fyi - Swagger is a project common on the internet for describing REST APIs. MS Azure uses for example.
We may need to work with the swagger dealing with our larger API surface. It’s in scope for 10.2 but nothing to report yet…
1 Like
try to use another browser, like Chrome x64 or Opera.
2 Likes
Olga is correct - this building of the doc page is faster in different browsers. Which one are you using when you received the error? (and version)
1 Like
I’m using Chrome 64bit. Whatever was causing the issue has gone away and I am not experiencing this problem anymore. My Chrome browser was recently updated or possibly my server has become more responsive.
Thanks for the input.
1 Like
Good to hear. Just finishing the labs for Insights. So excited to give the 4 hour extended ed and 1 hour labs.
2 Likes