I use Power Query at work and not everyone is on the same version of Power Query. Inadvertently, this causes problems that I don't know how to proactively manage.
For example, I'm using the latest version of PQ and when I create a query from an Access database, the line generated is,
When a coworker using an older version of PQ tries to run this, an error is returned, stating that 2 arguments were passed to a function expecting 1.
Apparently, the [CreateNavigationProperties]=true was not part of the File.Contents function in prior versions?
This is rather frustrating because these are lines generated automatically by using the PQ interface... not as if they were lines I specifically wrote. So it's hard to anticipate where PQ changes over time and does not maintain backwards compatibility.
Just wanted to get your thoughts to see if there is anything I can be doing about this or else just require everyone to be on the same/newest version.
Thanks
For example, I'm using the latest version of PQ and when I create a query from an Access database, the line generated is,
Code:
Source = Access.Database(File.Contents("\\server\access.mdb"), [CreateNavigationProperties=true])When a coworker using an older version of PQ tries to run this, an error is returned, stating that 2 arguments were passed to a function expecting 1.
Apparently, the [CreateNavigationProperties]=true was not part of the File.Contents function in prior versions?
This is rather frustrating because these are lines generated automatically by using the PQ interface... not as if they were lines I specifically wrote. So it's hard to anticipate where PQ changes over time and does not maintain backwards compatibility.
Just wanted to get your thoughts to see if there is anything I can be doing about this or else just require everyone to be on the same/newest version.
Thanks
