Cart
Users select entities, sources, or datasets to add to My Cart for use in the following actions:
- Create Dataset: Creation of a new dataset
- Add to Dataset: Inclusion in an already existing dataset
- Publish: Publish to a target location
- Explore: Explore data (also known as Shop for Data) to be queried and saved as an internal user View or checked out locally to CSV or XLS
- Prepare: Inclusion in a prepare transform dataflow
- Publish to Qlik Sense
- Publish to Power BI
Add to Cart: entities and sources
Select individual Entities or Sources and then Add to Cart.
Selection of datasets to add to cart
Users add Datasets to My Cart by selecting the sets to be added then Add to Cart.
Datasets are the recommended tool for the logical grouping of objects for inclusion in Prepare transforms and Publish facilitated by My Cart.
From My Cart located in the top-middle of the screen, display items in the cart by selecting the small orange carat to the right of My Cart and items count:
Display cart items
Once the cart opens to display content, either check Select All checkbox to select all cart items or expand each object type (Entities, Sources, and individual Datasets) to delete non-desired entities to make more granular selections.
Once items have been deleted and omitted for the operation, expand the Take Action dropdown.
Note that the number next to My Cart represents the number of selected entities and datasets placed in the cart. For example, if a dataset contains 3 Entities, My Cart will only register 1 item for that dataset however if a source containing 3 entities is added to the cart, the cart will register 3 more items.
Entities selected for My Cart
Publish to Qlik Sense
Publish to Qlik Sense creates (or updates) an app in Qlik Sense using either imported QVD or non-QVD entities. Publish to Qlik Sense logs are available by selecting the Logs button on this option in the dropdown from My Cart.
Users are able to choose one or more entities in either Catalog (by selecting cart icons on entity tiles of interest), or Discover by selecting or multi-selecting the source or entity row(s) then Add to Cart [or Datasets then (the gear icon) actions and Publish to Qlik Sense]. Multi-selection in Discover or Catalog will place entities in the cart from where users can Take Action to choose a destination for the selected entities. This section will focus on Publish to Qlik Sense options. Hover over My Cart in the top navigation bar to view possible actions from My Cart.
When Publish to Qlik Sense is selected, Catalog will check to see if any non-QVD entities are present. If non-QVD entities are present, a dialog appears allowing the user to select the Qlik Sense server at which the app will be created or updated (if multiple Sense servers are configured):
Select a Qlik Sense server
If only QVD entities are present, the Select Qlik Sense Connector dialog is skipped, as QVDs can only be published to the Sense server from which they originate. In this case, Qlik Catalog automatically determines the correct Sense server (if multiple Sense servers are configured).
Once the Sense server has been selected or determined, a new modal presents two radio button options: Create New App and Publish to Existing App.
Configuration of Sense servers
Information required to Publish to Qlik Sense is configured in Admin > Qlik Sense. Global settings are configured in the core_env.properties file. For each configured Qlik Sense connector, its Publish to Qlik Sense Settings can be altered by clicking to expand Publish to Qlik Sense Settings. Tooltips exist for each of the nine additional fields. For more information, see Qlik Catalog + Qlik Sense Integration Guide here: Installation Guides.
Publishing non-Managed, non-QVD entities to Qlik Sense
Publishing Registered or Addressed entities to Qlik Sense requires configuration to ensure that data is or can be loaded. Registered and Addressed entities do not have data loaded to them by definition, therefore either promotion or additional properties must be invoked to access and load source data. The following options are available to users:
- Recommended: Promote the entities to entity level MANAGED before selection, load the data in Catalog, then select and publish to Qlik Sense.
- Publish the entities to Qlik Sense and manually load the data in Qlik Sense.
- If the non-Managed, non-QVD entities are from a JDBC source, an additional option exists. The following core env property should be configured with default value (EXTERNAL) enabling Qlik Sense to pull data directly from the table’s external source (with Catalog brokering the exchange): podium.qlik.dataconnection.addressed.registered.entity.generating.from=EXTERNAL
Note that these properties must be set in addition to setting standard Publish to Qlik Sense properties.
Selection of Create New App or Publish to Existing App with Insight Advisor selected for the Starting View options navigates the user directly to an instance of Qlik Sense. Insight Advisor is the entry point for exploring data and creating visualizations. The difference between these options is that Create New App will produce a new app with the entity name (seen in the upper left of Qlik Sense Analyze sheet) and Publish to Existing App option will provide a new sheet within the existing selected App (the App name will appear in the upper left of the Analyze sheet).
Qlik Sense Analyze sheet
From the analyze sheet, click 
(edit) at the top right to navigate to the Edit sheet, where published tables can be accessed from Filter by table dropdown. Published entity fields are listed below Filter by table dropdown.
Qlik Sense Edit sheet
If the button for Publish to Existing App is selected, listed Apps to which the user has access in Qlik Sense are enabled for selection. Users also select their choice of starting view location in Qlik Sense: Insight Advisor (default), Data Load Editor, or Data Load Manager. Developers building Qlik Sense applications will likely select Data Load Editor or Data Manager starting views. Once a selection is made for the starting view, and then the existing App in which to publish, and then Ok, the entities in the cart are published and data can be loaded to the App.
Publish to Power BI
Publish to Power BI from My Cart pushes data from Qlik Catalog to a Power BI user’s workspace. Leveraging Power BI RESTful APIs, this feature requires that an admin first register the Qlik Catalog application with Azure Active Directory by using the Power BI app registration tool. It is used to obtain required API permissions for the Catalog user and critical pieces of information for authentication that an admin enters into System Settings in the Catalog Administration module: Application (client) ID, Directory (tenant) ID, and Client Secret. This information is used by Qlik Catalog to obtain an access token to call Power BI REST APIs.
Configuration properties
The following property setting is required in the core_env.properties global configuration file to enable Publish to Power BI. This property must be explicitly set (default value is false):
- is.publish.to.powerbi.enabled=true
Qlik Catalog supports Publish to Power BI for three Microsoft cloud environments: Commercial, GCC (Government Community Cloud), and GCC High.
Three properties in the core_env.properties global configuration file are used to configure support for the desired Microsoft cloud environment:
| Microsoft Cloud | core_env properties |
|---|---|
| Commercial | powerbi.resource.url.host=analysis.windows.net powerbi.api.endpoint.host=api.powerbi.com powerbi.auth.host=login.microsoftonline.com |
|
GCC |
powerbi.resource.url.host=analysis.usgovcloudapi.net powerbi.api.endpoint.host=api.powerbigov.uspowerbi.auth.host=login.microsoftonline.com |
| GCC High |
powerbi.resource.url.host=high.analysis.usgovcloudapi.net powerbi.api.endpoint.host=api.high.powerbigov.uspowerbi.auth.host=login.microsoftonline.us |
After setting the above four properties, select Refresh Core Env in Admin and then log out and back in.
Qlik Catalog and Microsoft Power BI configuration
To begin the integration process between Qlik Catalog and Power BI, login to the appropriate Power BI cloud environment:
| Microsoft Cloud | Power BI home |
|---|---|
| Commercial | https://app.powerbi.com |
|
GCC |
https://app.powerbigov.us |
| GCC High | https://app.high.powerbigov.us |
Once successfully logged in, open a new browser tab with the appropriate Power BI app registration tool:
| Microsoft Cloud | Power BI app registration tool |
|---|---|
| Commercial | https://app.powerbi.com/apps |
|
GCC |
https://app.powerbigov.us/apps |
| GCC High | https://app.high.powerbigov.us/apps |
Enter an application name.
Choose an application type of Server-side web application.
Enter a homepage URL replacing <hostname>: https://<hostname>:8443/qdc
Enter a redirect URL replacing <hostname> ("recieve" is misspelled): https://<hostname>:8443/qdc/powerbi/recieveCode
Check the following access settings:
- Read all datasets
- Read and write all datasets
- Read all workspaces
- Read and write all workspaces
When completed, the single page app registration tool will display the following application and URL values (examples shown) with the selected API settings:
Application Type: Server-side web application (for web apps or web APIs)
Home Page URL: https://<hostname>:8443/qdc
Redirect URL: https://<hostname>:8443/qdc/powerbi/recieveCode
After submission, you will be presented with the Application (client) ID and Client Secret. Copy both values and save to a safe location.
Open a new browser tab to the Azure portal: https://portal.azure.com
Select Azure Active Directory, then select App Registrations.
You will see a link for the app registration you created in the previous step under a heading like 1 applications found. Select the link.
When you select the link, application details display. The Application (client) ID should be the same as that shown in the previous step. Copy the Directory (tenant) ID.
If the secret value is lost, you can revisit the App details screen to create a new one (Manage>Certificates and secrets).
Qlik Catalog
Log into the installed instance of Qlik Catalog specified in the Redirect URI field during registration.
Go to Admin>System Settings and copy the values for Application (client) ID, Directory (tenant) ID, and Client Secret.
Save the settings.
The integration is complete and users can now select datasets and objects, add them to My Cart, and Publish to Power BI.
A popup will display requesting a name for the published dataset so that it can be identified in Power BI. Upon proceeding after naming the dataset, if not previously logged in to Power BI, users are navigated to a Microsoft login URI that includes session authentication and redirect information.
Upon verification and login, there are two possible paths to obtain admin consent: (1) Microsoft requests permissions and the user should Accept these permissions; or (2) the user must Request Approval from an Azure admin. Both of these are a one-time operation.
If approval is requested, the workflow order is the following:
- An Azure admin receives an email for an Admin consent request
- It includes a button link Review request
- This link leads to the Azure portal: Enterprise Applications, Admin consent requests
- Select the link for the app
- In Details, select Review Permissions and Accept
- A browser will open with a dialog like Admin consent request above; Accept the permissions
The end user should re-run the Publish to Power BI action in Qlik Catalog
After publishing to PowerBI, regardless of whether path (1) or (2) has been taken, users are navigated back to Qlik Catalog and the cart is now empty.
Publish to Power BI logs
Publish to Power BI logs are found in the same place as Publish to Qlik Sense logs by selecting the Logs button on the cart dropdown.
Screenshot example: Publish to Power BI logs:
Log into Power BI app at https://app.powerbi.com/groups/me/list/datasets to view and work with datasets published from Qlik Catalog.
Note the following Publish to Power BI limitations:
- This functionality is currently only available for Power BI Web (not Power BI Desktop)
75 max columns
75 max tables
10,000 max rows per single POST rows request
1,000,000 rows added per hour per dataset
5 max pending POST rows requests per dataset
120 POST rows requests per minute per dataset
If table has 250,000 or more rows, 120 POST rows requests per hour per dataset
200,000 max rows stored per table in FIFO dataset
5,000,000 max rows stored per table in 'none retention policy' dataset
4,000 characters per value for string column in POST rows operation