I've made progress with XLOOKUP and XMATCH. Example 6 in https://support.microsoft.com/en-us/office/xlookup-function-b7fd680e-6d10-43e6-84f9-88eae8bf5929 required me to relax a check in the FormulaParser and broke a negative test. I've disabled that test.
If someone could review the changes and if the FormulaParser change is too much, I can see if there is another way to get the example to work. https://github.com/apache/poi/commit/cbea2321f0a196a7466342e1291378683d9ff6fd https://github.com/apache/poi/commit/d924919ab5baf7fd7b4b4c7341e01327762fc579 On Tuesday 16 November 2021, 11:47:40 GMT+1, PJ Fanning <[email protected]> wrote: Hi, I've been looking at implementing XLookup function. I have a very partial implementation at https://github.com/apache/poi/pull/243. One issue is examples like Example 2 in https://support.microsoft.com/en-us/office/xlookup-function-b7fd680e-6d10-43e6-84f9-88eae8bf5929. In the unit test for that example in the pull request, I try to add the XLOOKUP formula as an array function but the formula evaluator sticks the first column value in the matched row in both cells as opposed to putting the second column value in the second cell. I'm not an expert on how POI evaluates formulas and I'm not sure whether array formula is the way to go in the first place. Is there anyone who is interested in working through this with me? Regards. PJ --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
