1
Currently, if oData is used to generate a movement journal header, you have to first generate the journal number manually. There is no standard (OOB) oData way to get the journal number for a movement journal. The standard inventory movement header entity should be able to generate (and return) the journal number when supplied the journal name id. This currently happens for the count journal header, so why not for movement journals?
Category: Data Management
STATUS DETAILS
Needs Votes

Comments

A

While I understand that you work on a votes system, some ideas simply make sense and should be part of the road map. I feel that this is one of those ideas. What's the point of oData integration to movement journals if you can't create a journal number for the movement journal. It really defeats the purpose of integration. If you want people to integrate to the system, then the system has to provide the tools to allow the integration to occur. At present, the inability for oData to be able to generate the journal number means that the system is preventing integration for movement journals.

Given that is is allowed with other inventory journal types (ie: count journals), it makes no logical sense why movement journals is excluded.

Category: Data Management