Triggered from #468, currently the parameters are ordered by sdkmessagerequestfield.position however for CustomAPIs the position isn't included in solution exports; resulting in the position following solution imports coming through "randomly".
This breaks portability of scripts between environments as select * from CustomAPI(paramA, paramB, paramC) on one environment might need to be changed to select * from CustomAPI(paramB, paramC, paramA).
Suggestion is to either allow hinting on the query or the use of set (like set QUOTED_IDENTIFIER ON).
Triggered from #468, currently the parameters are ordered by
sdkmessagerequestfield.positionhowever for CustomAPIs the position isn't included in solution exports; resulting in the position following solution imports coming through "randomly".This breaks portability of scripts between environments as
select * from CustomAPI(paramA, paramB, paramC)on one environment might need to be changed toselect * from CustomAPI(paramB, paramC, paramA).Suggestion is to either allow hinting on the query or the use of set (like
set QUOTED_IDENTIFIER ON).