optimization tool Objective value type

[niteshsharma677]

How to make sure the objective value we get in the optimization tool output should be integer ? 

[JamesCharnley · Accepted solution]

Hi @niteshsharma677,

Not the clearest what you mean but I can take a guess. I'm assuming you're talking about the actual value coming out of the tool being an integer in value not type, in which case you need your coefficient entering the O anchor to also be an integer, otherwise the tool will be trying to minimise/maximise it regardless of what your 'variable type' is, and if it's a decimal going in then that includes decimals coming out. If your amounts can only be integers, you should change your variable type to be 'I' and then map that in the tool configuration (B if it's binary).

If you mean data type, as far as I'm aware there's no way of getting it to be output as an integer instead of a string, but you could just change it afterwards in a Select in pretty much every scenario I can think of.

Hopefully that makes some sense.

[niteshsharma677]

@JamesCharnley Yes this makes sense. Thanks.
Also one more thing, The Maximized Objective value provided by the Excel solver and Alteryx Optimization tool is different. Alteryx Optimization tool is giving slightly greater value than Excel Solver. Is this expected. If Yes why ?

[JamesCharnley]

No problem @niteshsharma677. If you have all variables and constraints configured the same then I can only assume that the algorithm being used under the hood is different, but I don't have much knowledge of that and I can't really find any good comparative documentation. 

If you can validate that the constraints are all being met within the Alteryx result then I'd be inclined to take that one as my answer.