SOLVED

Query Compatibility Issue

%3CLINGO-SUB%20id%3D%22lingo-sub-2421184%22%20slang%3D%22en-US%22%3EQuery%20Compatibility%20Issue%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2421184%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20there!%20I%20am%20in%20a%20situation%20wherein%20I%20have%20created%20an%20excel%20file%20with%20approximately%2050%20queries(with%20data%20connection%20to%204%20different%20folders).%20The%20problem%20is%2C%20I%20tried%20to%20zip%20this%20file%2C%20and%20sent%20it%20to%20my%20colleague(he's%20the%20one%20who%20is%20going%20to%20use%20it).%20Unfortunately%2C%20the%20following%20error%20pops%20up%20in%20his%20system.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22YashWani_0-1623055338702.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F286782iFCB88E36A6F7754F%2Fimage-size%2Fmedium%3Fv%3Dv2%26amp%3Bpx%3D400%22%20role%3D%22button%22%20title%3D%22YashWani_0-1623055338702.png%22%20alt%3D%22YashWani_0-1623055338702.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20use%20Excel%20365%20whereas%20my%20colleague%20uses%20Excel%202016.%20Tried%20checking%20for%20compatibility%20issues%2C%20couldnt%20find%20any.%20Request%20all%20users%20to%20help%20on%20this!!Please!!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2421184%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EExcel%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2421502%22%20slang%3D%22en-US%22%3ERe%3A%20Query%20Compatibility%20Issue%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2421502%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1072618%22%20target%3D%22_blank%22%3E%40YashWani%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThat's%20not%20an%20error%2C%20that's%20the%20warning%20which%20says%20PQ%20was%20on%20more%20modern%20version%20of%20it.%20It%20appears%20on%20different%20versions%20of%20365%20as%20well%20if%20PQ%20was%20created%20on%20newest%20build.%3C%2FP%3E%0A%3CP%3EJust%20Close%20it%20and%20continue%20to%20work.%20However%2C%20there%20is%20some%20probability%20that%20incompatibility%20errors%20with%202016%20could%20appear%2C%20but%20that%20will%20be%20errors%20within%20concrete%20queries.%20If%20any.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2425041%22%20slang%3D%22en-US%22%3ERe%3A%20Query%20Compatibility%20Issue%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2425041%22%20slang%3D%22en-US%22%3EThanks%20for%20replying%20Sergei%2C%20the%20problem%20here%20being%20that%20the%20queries%20ae%20not%20refreshing%20because%20of%20this%20particular%20warning.%20I%20am%20getting%20a%20%22failed%20to%20refresh%20data%20range%20error%22%20for%20all%20the%20queries.%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E
New Contributor

Hi there! I am in a situation wherein I have created an excel file with approximately 50 queries(with data connection to 4 different folders). The problem is, I tried to zip this file, and sent it to my colleague(he's the one who is going to use it). Unfortunately, the following error pops up in his system.

 

YashWani_0-1623055338702.png

 

I use Excel 365 whereas my colleague uses Excel 2016. Tried checking for compatibility issues, couldnt find any. Request all users to help on this!!Please!!

5 Replies

@YashWani 

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.

Thanks for replying Sergei, the problem here being that the queries ae not refreshing because of this particular warning. I am getting a "failed to refresh data range error" for all the queries.

best response confirmed by YashWani (New Contributor)
Solution

@YashWani 

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!

@YashWani 

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.