Detach your M code from workbooks to reuse it! Import modules from local or web storage (unlimited number of sources)
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
Docs Move test code into a separate directory Sep 7, 2018
Modules Move test code into a separate directory Sep 7, 2018
Samples Update Assert to make it documentation compliant Feb 12, 2018
Tests Move test code into a separate directory Sep 7, 2018
VBA Add module description on the top of the file Apr 11, 2018
.gitattributes
.gitignore More extensions for ignoring test workbooks Jan 10, 2018
CONTRIBUTING.md Add README and CONTRIBUTING information Nov 29, 2017
LICENSE Apache License, version 2.0 Nov 29, 2017
LibPQ.pq Bump modification timestamp Feb 21, 2018
LibPQPath-sample.pq Move test code into a separate directory Sep 7, 2018
README.md Add information on user support Oct 11, 2018
RELEASES.md New changelog entry about Tests/ directory Sep 7, 2018
ROADMAP.md Release 1.1.0 Jul 11, 2018

README.md

LibPQ - detach your M code from workbooks and reuse it!

This project offers a collection of functions and useful queries for Power Query Formula Language (also known as M language) and a loader to import source code from external modules into Power Query.

Feature highlights

More information

What other people say about LibPQ

Installation and usage

Copy source code to the filesystem (optional)

Download the contents of this repo and extract it anywhere you want. If you skip this step you will not be able to list all available modules with LibPQ() call and every time you load a module LibPQ will access the network.

Add LibPQ to the workbook

Create two blank queries in your workbook:

  • LibPQ - copy the contents of LibPQ.pq verbatim
  • LibPQPath - provide location of modules source code (local and/or web). See sample at LibPQPath-sample.pq

Import LibPQ modules when writing your queries

Import any of the available modules via LibPQ("modulename") when writing your queries in Advanced Editor.

To import all modules available locally use LibPQ() with no arguments (or null). That will return a record where keys are module names and values are the results of loading those modules (function object or output of a query).

LibPQ modules

All modules are grouped into namespaces, much like the standard library:

  • Date - Functions for working with dates
  • Factory - Functions that create other functions
  • Folder - Functions for manupulating folders and their contents
  • Function - Functions that operate on other functions
  • List - Functions for working with lists
  • Module - LibPQ tools for importing source code
  • Read - Functions that import data
  • Table - Functions for table operations
  • Tests - Unit tests for LibPQ modules
  • Text - Functions for working with text
  • UnitTest - Unit testing framework

Detailed module list is available in documentation, and each module has a clear description in the comment at the top of its source file.

Compatibility with @tycho01's library

LibPQ allows specifying multiple possible locations for source code, that's why you can add @tycho01's library as a fallback.

Any module from that library should be supported, though some will require adding a Load query to your workbook. To create a Load alias for LibPQ you need to:

  • Create a new blank query
  • Replace all its code with text LibPQ
  • Save the query under the name Load

Now the Load function will be available from #shared context, and you should be able to import any module from @tycho01's library.

Contributing

All contributions are welcome! Please check CONTRIBUTING.md for details

Support

Issue tracker

GitHub's issue tracker is the primary venue for asking and answering support questions. Please don't forget to search closed issues for the topic you're interested in!

If you know an answer to the question asked by someone else, please do not hesitate to post it! That would be a great help to the project!

Email

If for some reason you'd rather not use the issue tracker, contacting me via email is OK too. Please use a descriptive subject line to enhance visibility of your message. Also please keep in mind that support through the channels accessible to the public is preferable because one answer can help many people who might read it later.

My email is visible under the GitHub profile and in the commit log.

Community support

You might get faster and more interactive support from other users.

This project does not (yet) have a dedicated community venue, but experienced PowerBI/Power Query users will most likely be able to figure out most common questions. You can try asking at the local PowerBI-related forums, Facebook groups, IRC/Discord/Telegram chats or on Reddit/StackOverflow.

License and copyright

Copyright © 2017-2018 Vitaly Potyarkin

   Licensed under the Apache License, Version 2.0 (the "License");
   you may not use these files except in compliance with the License.
   You may obtain a copy of the License at

       http://www.apache.org/licenses/LICENSE-2.0

   Unless required by applicable law or agreed to in writing, software
   distributed under the License is distributed on an "AS IS" BASIS,
   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
   See the License for the specific language governing permissions and
   limitations under the License.