IBM Sterling Ideas

formerly Watson Supply Chain

Submit new product ideas for IBM Sterling solutions. Before you submit, please review existing ideas; if an idea close to yours already exists, it's better to add comments or vote on the existing idea. We will review your ideas and use them to help prioritize our product development. Best of all, the portal will automatically update you when the status of your idea has been changed. Order Management, Store Engagement, Watson Order Optimizer, Inventory Visibility, CPQ and Call Center are now part of Watson Supply Chain

Connect with IBM experts and your peers on the Supply Chain Collaboration Community and the Order Management Interest Group

automapper should also work with same input/output types

It is a common pattern to work twice on a output card, e.g.:
- when the output should also include summarized amounts of several output records that need to be built/calculated first
- when the header should announce how many records will follow

Now when building the mapping for the 2nd iteration of the output card, the automapper comes in handy, because we usually map the results of the first iteration 1:1, except for one or two fields that need the SUM() or COUNT() values. Unfortunately the automapper doesn't work here, since its behavior somehow differs when input and output use the same typetree (please see the linked PMR for details).
  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Jan 9 2018
  • Declined
How will this idea be used?
What is your industry?
What is the idea priority? High
DeveloperWorks ID DW_ID85851
Link to original RFE
  • Attach files
  • Admin
    Luke Raiano commented
    28 Aug, 2018 06:55pm

    We are plannignt o re-architect the automapper in a future release