Forum Discussion
Query Compatibility Issue
Warning itself only says you may have errors (and you have it) due to incompatibility, that's not the source of the error. You need to check on 2016 concrete quires to see there the errors are.
That's not an error, that's the warning which says PQ was on more modern version of it. It appears on different versions of 365 as well if PQ was created on newest build.
Just Close it and continue to work. However, there is some probability that incompatibility errors with 2016 could appear, but that will be errors within concrete queries. If any.
Warning itself only says you may have errors (and you have it) due to incompatibility, that's not the source of the error. You need to check on 2016 concrete quires to see there the errors are.
- Thanks Sergie, I checked the queries in the power querie window and found an error with a particular command(int64.type in index column) which was creating an error. Thanks for the help!
Yes, 4th explicit parameter in Table.AddIndexColumn was added about an year ago and it is not supported by previous versions of Power Query. That's one of compatibility issues.
If you work with people who are on outdated Power Query you may manually remove this 4th parameter in formula bar, it's optional. Bit annoying, but the only other variant if your users will do the same on their machines.
Have a nice weekend.