Ways to access your data
To access your
Loading data from tables
After you authenticate the connector with your account credentials, you can use the following tables to select and load data:
|UserVideos||Shows the list of videos from the authenticated user.|
|VideoSearch||Shows the public videos based on a search query.|
|ChannelSearch||Shows the public YouTube channels based on a search query.|
Shows the video statistics for a video based on the video ID. Video IDs can be entered as comma-separated values: videoid1, videoid2,...
|ChannelStatistics||Shows the channel statistics for a video based on the channel ID. Channel IDs can be entered as comma-separated values: channelid1, channelid2,...|
|HomePageActivities||Shows the list of activities from the homepage of the authenticated user.|
|MyActivities||Shows the list of activities by the authenticated user.|
|ChannelActivities||Shows the activities for a channel, based on a channel ID.|
|VideoComments||Shows the comments for a video, based on the video ID.|
|ChannelComments||Shows the channel comments, based on a channel ID.|
|CommentResponses||Shows the comment responses, based on a channel ID.|
To select and load data from a table, enter the required table parameters and click Preview data. Required parameters are marked with an asterisk (*). The table fields are displayed under the Data preview tab. You can select fields individually by selecting the box beside each field name. Select Insert script after you have made your selection.
The Uservideos, VideoSearch, and ChannelSearch tables allow you to you select data based on a search term or by using YouTube query parameters. To learn how to specify the YouTube query term with the search list documentation.
Working with the YouTube API quota limits
Reference - YouTube Developer documentation
You can refer to the
You receive an error message that you have reached the API rate limit
You have exceeded the API limits that are imposed on the Qlik Web Connectors by the YouTube Data API.
To reduce the impact of reaching the API rate limits, develop your app with the following in mind:
- Extract only the data you need.
- Reload one YouTube Data-based application at a time.
- Ensure that loops in your script that make API calls will not result in infinite loops.
You experience reduced functionality or see an incorrect operation for some tables
There are several known issues which may cause reduced functionality:
- The UserVideos table does not include parameters for publishedAfter or publishedBefore.
- VideoSearch and ChannelSearch tables may return unexpected results if publishedAfter or publishedBefore parameters are used.
- The HomePageActivities table does not include parameters for publishedAfter or publishedBefore.
Refer to the following known issues:
Failed to search.list with publishedAfter.
Search publishedAfter and publishedBefore not working as expected
Actvities API: publishedAfter is not respected in activities