S6909 will complain saying the Types.BIGINT line could be moved outside the for loop - which of course is not true and would change the semantics because it is inside an if statement!
Welcome to the community and thank you for reporting this FP!
I feel the pain here since the suggestion is likely to introduce a bug. Hopefully, the sample you shared was just for education and you see how you could improve this to be more efficient
However, I can reproduce the problem locally, and I created a ticket to track progress on the issue.
Sorry, you can discard my comment on efficiency.
I misread the original snippet and thought you were assigning the value in position 11 with the same method called in both branches. In which case you could have moved the test of nullability into a variable assignment and called the method with the same variable without branching anymore.
But that does apply here