Using REST v1 vs v2 on 10.2.500

Epicor ERP 10
1

Are there any known issues using REST v1 instead of v2 in 10.2.500?

Thanks
David

2

Bugs wise or feature wise?
From a feature standpoint I hear the following a lot:

REST v1

  • OData v3
  • Session Properties like Company in the message header.

REST v2

  • OData v4
  • Session Properties like Company in the URL.
  • API Key Support (requirement)
3

I thinking bug wise. Like something fixed in v2 that is still not fixed in v1.

4

I am trying to remember anything glaring but it would be in the release notes.

The thing to remember is that the emphasis on changing versions was to align with the newer OData protocol. The industry is in a mixed state of supporting both 3 and 4 so we need to do the same so half your apps don’t break.
e.g. - There are no plans to even discuss retiring v1 until the industry drops OData v3 which means I am not holding my breathe.

Since the patient was on the table with the v4 uplift and contracts were being broken, we took the time to clean up some of the larger usability complaints around putting company in the URL, etc.

1 Like
5

Thanks @Bart_Elia . I will review the release notes to verify I’m not missing anything.

6

I am curious what others think. :wink: