Request: Update compatibility with recent SDK

alazyworkaholic commented 2 years ago

This query

let
    List = {1..20},
    Result = List.Split(List, 4)
in Result

fails with The name 'List.Split' wasn't recognized. Make sure it's spelled correctly. List.Split is a valid built-in function and I can only guess that it is not recognized because of the outdated SDK.

New functions, like List.Split, above.
The language has evolved a little over time (e.g. the ?? coalesce operator).
The signatures of certain functions have changed. For example:
- Table.Skip no longer requires a second parameter (it now defaults to skipping one row).
- Table.AddColumn can now take 5 rather than 4 parameters

Such inconsistencies make what should be simple lift & shift of code from Power BI to PQnet a very difficult exercise.

I understand there was a reason to freeze the version but that was several years ago, so can you please update PQnet's SDK compatibility?

7ohm7 commented 2 years ago

Hi, thanks for the great CLI solution. I followed up on alazyworkaholic's request above. I would like to kindly ask to add latest built-in functions in the SDK, e.g. Table.FuzzyNestedJoin, Text.Reverse or Splitter.SplitTextByCharacterTransition.

Thank you.

gsimardnet commented 2 years ago

PowerQueryNet is project based on the Power Query SDK developed by Microsoft. The last time it was updated was in 2019. I first recommend that you ask Microsoft to update their library.

7ohm7 commented 2 years ago

Oh, understood, thanks for the quick reply

7ohm7 commented 2 years ago

Sorry to ask again, but these functions are in SDK from 2019 - please find attached the screen from #shared for SDK 1.0.0.25

I tried to install your application with this package, but it is not compatible:

Could you please update it so they work together?

gsimardnet / PowerQueryNet

Request: Update compatibility with recent SDK #32