Generating a Get request to the API at: /JobMtls({Company},{JobNum},{AssemblySeq},{MtlSeq}) always returns the last material added to the job. Not the material requested.
I’m new to the Epicor bug fixing process so please bear with me.
Is this able to be patched in 10.1.600? It is a major jump to go to 10.2.200 and we upgraded to 600 in large part for the REST API.
How can I look up the 207815 bug details?
aidacra
(Nathan your friendly neighborhood Support Engineer)
4
Q1: Is this able to be patched in 10.1.600? It is a major jump to go to 10.2.200 and we upgraded to 600 in large part for the REST API.
A1: It is not targeted to be included in 10.1.600 at this time. Please open a case with Epicor Support, and we can submit a request to have development review the changes introduced for this SCR to determine if they can be retro’d back to the 10.1.600 release during a future point update.
Q2: How can I look up the 207815 bug details?
A2: https://scrs.epicor.com/ (and log in with your epicweb credentials). Information from the scrs.epicor.com site is the same information that gets included in our formal release notes when we publish updates/releases.
Awesome. The scr details includes the following: “Severity=3 - Error Workaround”. Does this mean a workaround exists? If so, is there a way to look this up?
I have provided this information to our support ticket (CS0000801283).
I am not very familiar with JobEntry\JobMtl, but it you are positive that the you are looking in the right place and filter is written correctly, then my only idea is that REST record limit should be checked in web.config.
Try to add the following line into the web.config, appSettings section: