Skip to main content

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.

 Adding entities 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
Hover over My Cart to open contents

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

Selected objects from discover grids and catalog appear in My Cart

Publish to Qlik Sense

Publish to Qlik Sense: exports non-QVD entities and QVDs to a configured instance of Qlik Sense. 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 QVD tiles of interest), or Discover by selecting or multi-selecting the source or entity row(s) then Add to Cart [or Datasets then icon actions (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.

Take Action from My Cart

Publish to Qlik Sense from Take Action menu

When Publish to Qlik Sense is selected for QVD and non-QVD entities, two radio button options will display in a modal: Create New App and Publish to Existing App.

Qlik Sense Publish to Qlik Sense options from My Cart

The following properties are required in core_env global properties file to configure Publish to Qlik Sense. The property values are examples and must be configured for each environment:

  • is.publish.to.qlik.enabled=true
  • podium.qlik.dataconnection.name=qdc
  • podium.qlik.appcreation.nodecommand=node
  • podium.qlik.qsockclient.script.directory=/usr/local/qdc/qlikpublish/
  • qlik.sense.url=https://ducks-sense1.ad.podiumdata.net/sense/app/<podium-gen-app-id>
  • qlik.sense.active.directory.name=AD
  • qlik.sense.record.count.threshold.for.data.load=20000 (default)

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.

Warning: Regardless of whether a new app is created or the data is published to an existing app in Qlik Sense the number of records in the newly published entities must not exceed the threshold specified in core_env property (qlik.sense.record.count.threshold.for.data.load). If the number of records exceeds this threshold, then the data must be manually loaded into Qlik Sense by the user (in the event of this scenario an alert will display stating the data must be manually loaded).
Note: The logged in user only has access to apps created by their credentials.

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

Analyze sheet view in Qlik Sense Insight Advisor

From the analyze sheet, click icon Qlik Sense edit (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

Editing sheet view in Qlik Sense Insight Advisor

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 Qlik Sense data load editor starting view

Qlik Sense data load editor view

Publish to Qlik Sense data manager starting view

Qlik Sense data manager view

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 users first create a Qlik Catalog application on Azure Active Directory (AD) portal; this application is used to obtain eight (8) required API permissions for the Catalog user and three (3) critical pieces of information for authentication that users enter into System Settings in the Catalog Administration module: System Settings tab: 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.

The following property setting is required in core_env global properties file to configure Publish to Power BI. This property must be explicitly set (default value is false):

  • is.publish.to.powerbi.enabled=true
Note: Note that setting up the application in Azure AD portal, acquiring permissions, and transferring Application (client) ID, Directory (tenant) ID, and Client Secret values to Qlik Catalog is a one-time process that must be completed by a Qlik Catalog Admin.
Note: SSL must be enabled on the Qlik Catalog Catalog instance of Tomcat. Refer to Catalog install guide: Tomcat SSL Configuration for instructions.

To begin the integration process between Qlik Catalog and Power BI, go to Azure Active Directory (AD) Portal go to

https://aad.portal.azure.com/

to create a new application.

Click on All Services, and then App Registrations

Azure AD All Services and App Registrations

Click on New Registration.

Azure AD New Registrations

Provide the required information for the following fields (values are examples, configure to environment):
Name The user-facing display name for this application (this can be changed later): qlik-catalog
Supported account types Who can use this application or access this API?: [check radio button for] Accounts in this organizational directory only
Redirect URI (optional) An authentication response is returned to this URI after successfully authenticating the user. The received code is a silent authentication process, users do not interact with the code. Providing this URI now is optional and can be changed later, but a value is required for most authentication scenarios.
[The first field is a dropdown value]: Web
[The second field is a free-form field in which to provide Qlik Catalog install URL]: https://hostname.corp.qlikcatalog.com:8443/qdc/powerbi/recieveCode

Click Register.

Entered name, account type, Catalog install URL

An overview with application information will display. Select API Permissions under Manage.

Application overview and API permissions selection

Select Add a permission to display Commonly used Microsoft APIs and select Power BI Service.

Select Power BI Service permissions

When popup asks what type of permissions your application requires select Delegated Permissions.

Delegated permissions selection

From API permissions tab, search for and add the following permissions:

  • Data.Alter_Any
  • Dataset.Read.All
  • Dataset.ReadWrite.All
  • Group.Read
  • Group.Read.All
  • Metadata.View_Any
  • Workspace.Read.All
  • Workspace.ReadWrite.All

Search on and add eight permissions

Once the eight permissions have been added, select Certificate and secrets and select New client secret. Enter a password and expiration duration (options are In 1 year, In 2 years, or Never).

Warning: Be sure to make a note of client secret password, it will not be visible again after application set up.

Enter secret password string

Select Overview from Manage pane and copy values for Application (client) ID and Directory (tenant) ID; these values and client secret will be copied into Qlik Catalog System Settings.

Copy client and tenant IDs from Overview tab

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.

Catalog System Settings Azure ID and password values settings

The integration is complete and users can now select datasets and objects, add them to My Cart, and Publish to Power BI.

Publish objects to Power BI from Cart

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, users are navigated to a Microsoft login URI that includes session authentication and redirect information.

Microsoft Login redirect URI with session information

Upon verification and login Microsoft requests permissions, Accept these permissions.

MicroSoft requests API permissions acceptance

Users are then navigated back to Qlik Catalog where the cart is now empty. Publish to Power BI logs are found in the same place as Publish to Qlik Sense logs by selecting Logs button on the cart dropdown.

Example: Publish to Power BI logs:
2020-07-29 18:16:03.600: [ CPI_FoodBev, CPI_ALLItems, CPI_USHousing, CPI_OtherWest ]
2020-07-29 18:16:03.605: Starting job: Publish To PowerBI
2020-07-29 18:16:03.657: Watching for process completion/termination.
2020-07-29 18:16:06.677: Submitting data to Power BI
2020-07-29 18:16:06.677: Dataset Name: Demo_INDEXSN
2020-07-29 18:16:06.677: Client Id: f038d757-4706-41cf-abdc-99043fe244ec
2020-07-29 18:16:06.677: Tenant Id: c21eeb5f-f5a6-44e8-a997-124f2f7a497c
2020-07-29 18:16:06.677: Username: podium
2020-07-29 18:16:06.677: Entities to be published with field and record counts:
2020-07-29 18:16:06.678: Entity Name: CPI_ALLItems , Field Count: 5 , Row Count: 49612 , Validated: true
2020-07-29 18:16:06.678: Entity Name: CPI_FoodBev , Field Count: 5 , Row Count: 119198 , Validated: true
2020-07-29 18:16:06.678: Entity Name: CPI_OtherWest , Field Count: 5 , Row Count: 47895 , Validated: true
2020-07-29 18:16:06.678: Entity Name: CPI_USHousing , Field Count: 5 , Row Count: 39939 , Validated: true
2020-07-29 18:16:07.653: Finished job: Publish To PowerBI

 

Screenshot example: Publish to Power BI logs:

Power to 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.

Published datasets display in Power BI application for analysis and reporting

Note:

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