We have two fields that we added to our packout screen for a handheld that are EpiBound to CallContextBPMData. The screen is ignoring the TabIndex value we enter in the properties tab. I know EpiBinding on Fields can override some of the properties set but I am wondering if anyone has an idea how to force the screen to recognize the tabindex values for these two fields?
Sometimes Epicor hard codes the next field jump at which point index will not work. In those cases you might have to hardcode your order to override their order. Not sure if that’s the case without reviewing the source but sometimes it’s an uphill battle.
Yea I have read that on other posts. I was able to get this to work by creating a leave field event and then using the .Focus() to get it to goto my fields next.