API Product revision missing fields

[jeremy_febvey]

Ability to create new product revision manually but not via API, Revision Name and Revision Date fields not available via API.

[andrade_david]

Hello @jeremy_febvey, I'm adding this idea as archived because we are not considering any future enhancements on the revisions feature - we're suggesting customers to add a suffix that includes the revision to the product code.

Our current approach is managing revisions outside the MES scope, such as on a PLM or an ERP.

[jeremy_febvey]

Hello @andrade_david,

Beyond the fact that what you're saying means we can never have the same product codes aligned across multiple systems, how can we then manage the execution of a production order on different versions?
It's clear that the PLM or ERP are the data masters so there's no question of managing versions in the MES, but the MES must be able to understand and communicate with these systems without needing to find workarounds like using ESB to implement management rules.

[andrade_david]

Hello @jeremy_febvey 

As we're not considering enhancements on revision control, indeed it means that when multiple revisions exist with the same code in external systems you'll have to add a revisions identifier on the product code in Fusion Operations (to prevent duplicated product codes).

For example, adding the revision code as a suffix of the product code - and indeed implement that logic when communicating data with other systems.

Managing the execution of different product versions can be done by having two independent products created, for example "Product [Rev:A]" and "Product [Rev:B]".