![]() ![]() Because of this, this article will also outline some risks involved with not waiting for the aforementioned future release.īefore outlining the steps for manual conversion, let’s review why Query Studio is being deprecated and its current state. Although IBM recommends users to wait for a future release of Cognos Analytics 11 that can open Query Studio reports in its new editor, many users feel that they need to convert their existing Query Studio reports now so that they are not continuing to develop in a legacy editor. The links you create are equi-joins (=) and can use data items or calculations.In this article, you will learn how to manually convert Query Studio reports to reports that can be opened in either Cognos Workspace Advanced, Report Studio, or, if you are using Cognos Analytics 11, the Authoring perspective. You can have more than one link, if required. You must browse and specify the existing report (or a Query Subject in a relational data source) and create a link using common column between the two. Use the step-by-step wizard to import the external data file from a computer accessible by IBM Cognos BI server or your computer. ![]() You can then map the data in the external file and the report by defining a relationship based on common data items in the two sources. When the corporate data you require for reporting exists in more than one Query Subject, you should consider creating a report that brings the data together into one single report from all the relevant Query Subjects. You can link the data from the external file to a data item in a Query Subject or to an item in an existing Cognos report. Defining these relationships is key to using the external data correctly for reporting. You see in the upcoming section how to define these relationships. For example, if the external file has Product line survey data, the corporate data must have the Product line defined as well. Data Mapping: When you want to use data from both an external data source and the corporate data available in Cognos, you must define how the data in the two data sources link together. When you import external data you do not overwrite the existing Cognos content it is stored separately.Ģ. In situations in which the server cannot locate the file automatically, for example, the file is inaccessible by the server and so on, the server prompts for the file location. This enables the server to automatically load the external data file for reporting. To bypass this you can select the check box Allow server to automatically load the file. When you change the default namespace name, you will be prompted to select the external data file every time to run the report. By default, this is the same as the external data filename without extension however, you can change it to anything else. ![]() The namespace name provides a unique name to associate with the data items imported. In addition, in the section Namespace for the external data, you must provide a name that will be used as the namespace name in the new package. ![]() You may select the check box Allow the server to automatically load the file with this option checked you are not prompted to provide the file name every time to run the report. Select Data: In this step you must select the external data file you want to import and the data items from the file you want to include for reporting. ![]()
0 Comments
Leave a Reply. |