DataLayer.WebFeed - Working with DataLayer.WebFeed

The datalayer connects directly to the web feed and retrieves the information. Unlike most datalayer elements, this one does not requred a Connection element. Feed information is retrieved and cached as rows and columns, with one row per news item. Data retrieved into the datalayer is cached in XML format.

The data retrieved with a datalayer is available using @Data tokens, in the format @Data.ColumnName~. The spelling of the column name is case-sensitive. The data is only available within the scope of the parent element of the datalayer, not throughout the entire report definition. The DataLayer.Linked element can be used to make the data reusable in another datalayer outside this scope.

"Column names" may vary depending on the feed, however the column names for news items will all start with "item_" and for header values with "channel_". Examples of possible valid "column names" available through the @Data token are:

Column	Description
item_title	The title of the new item
item_link	A link to the item. If the feed is a news aggregator, this link may have embedded in it the URL of the source for this item
item_guid	A unique identifier used by the feed for this item
item_category	A categorization, specific to the feed, of this item
item_pubDate	A publication timestamp for this item
item_description	Text of the actual item, possibly in HTML format
channel_pubDate	A publication timestamp for this item
channel_lastBuildDate	Timestamp for the last assembly of the feed page
channel_webMaster	Email address of the feed page web master
channel_image_url	URL for images associated with feed
channel_copyright	HTML copyright message
channel_language	Language designator abbreviation
channel_image_link	URL for image associated with item

The Auto Columns element can be used to quickly see which "column names" are being returned by the feed. You can view the data retrieved into the datalayer by turning on the Debugger Link in the _Settings definition (General element) and using the resulting icon at the bottom of the report page to view the Debugger Trace Page. A link on the trace page will display the retrieved data.