Wiki Markup |
---|
{anchor:top} {toc: class=contents} h2. Overview概要 {styleclass: Class=topLink}[top|#top]{styleclass} Views within Yellowfin provide the link between users, their reports, and the database. The purpose of the view is to simplify the knowledge required by end users of the source database. This section describes some of the basic view management options available to you. # To create a new view: ## click the add view link from within the source record, OR Yellowfinのビューは、ユーザー、ユーザーのレポート、およびデータベースの間を結びつけます。ビューの目的はエンドユーザーが専門的な知識を必要とせずにソースデータベースを使えるようにすることです。このセクションでは、基本的なビュー管理オプションのいくつかを解説します。 # 新規ビューを作成するには、以下の手順を実行します。 ## 「データベースビュー」画面で「ビュー追加」をクリックします。または !46.png|thumbnail,border=1! ## click on the Create menu in the main navigation bar and select Viewメインナビゲーションバーの「作成」メニューをクリックして、「ビュー」を選択します。 !46b.png! The view initiate page will prompt a select of the type of view you wish to create and the data source connection to use. The choices you have are: ||Builder||Description「ビューの初期化」ページでは、ビューの作成方法や接続するデータソースの選択を行います。選択肢の意味は以下の通りです: || Builder || Description || | *[Drag and Drop|Viewビューの作成#Drag Creation#Drag and Drop Builder]* |Use the Yellowfin builder to create a view on your database.| |作成に、Yellowfinのビュービルダーを使用します。\\ | | *[Freehand SQL|Viewビューの作成#Freehand Creation#Freehand SQL View]* |Use an作成に、SQLエディターを使用します。\\ SQL statement to create your view| | |*[Composite View|Viewビューの作成#Composite Creation#Composite View]* |Use to create a view which connect to multiple separate data sources and views.| |複数のデータベースに接続するビューを作成する場合に使用します。\\ | | *[OLAP|Viewビューの作成#OLAP Creation#OLAP Cube View]* |Select an既存のOLAPキューブを選択します。新たな属性を加えることはできません。\\ existing OLAP cube - you will not be able to add additional attributes to a cube.| || | *[Stored Procedure|View Creation#Storedビューの作成#Stored Procedure]* |The ability to create a view from existing stored procedures on you database.データベースに実行されている既存のプロシジャーからビューを作ることができます。\\ | !47.png|thumbnail,border=1! # Select a category for the view. This is used to limit the field item categories to an appropriate set. For example only Sales Related field categories will be displayed for a sales view. # To create a new category click the create category link. This will open a popup window in which you can add a new category. h2. Drag and Drop Builderビューのカテゴリーを選択してください。このカテゴリーは、フィールドのカテゴリーを限定するのに用いられます。たとえば、販売ビューには、販売関連カテゴリーのフィールドだけが表示されるようにします。 # 新しいカテゴリーを作成するには、「カテゴリーの編集」をクリックします。新しいカテゴリーを追加するためのウインドウが開きます。 h2. ドラッグ&ドロップで作成 {styleclass: Class=topLink}[top|#top]{styleclass} This option allows you to use Yellowfin to simply join multiple tables from a single selected database through a web interface. Yellowfinのウェブインターフェースにより、データベース内の複数のテーブルを簡単に結合することができます。 bq. See [Drag & Drop View Builder] for more information. h2. Freehand SQL ViewフリーハンドSQLビュー {styleclass: Class=topLink}[top|#top]{styleclass} The freehand SQL option allows you write your own view directly into the Yellowfin repository. The tables available from the source system are displayed in the table list on the left hand side. 「フリーハンドSQL」を選択すると、直接Yellowfinのリポジトリにビューを書き込むことができます。ソースシステム上の使用可能なテーブルは、左側の「データベーステーブル」に一覧表示されます。 !48.png|thumbnail,border=1! {color:#C00000#c00000}{*}Note:*{color} When writing an SQL view it is very important that you do not include an order by - since results are sorted by the Java application not the database. The order by will cause your view to fail. h2. Composite View {styleclass: Class=topLink}[top|#top]{styleclass} A composite view allows you to create a view which joins multiple data sources together. This allows users to create a report which includes data from these multiple databases. The view builder for a composite view differs in that rather than displaying tables from a selected database it allows you to join existing Yellowfin views together and create virtual tables from any defined database. # To create a composite view select the composite view option from the author drop down. # You will also need to select a database in which you wish to store the view results. This is needed since composite views can be highly complex and result in slow query performance by your users. As a result Yellowfin schedules a query to generate the view and all its data on a regular basis to be stored in a specific warehouse database. !49.png|thumbnail,border=1! bq. See [View from Multiple Sources] for information on creating composite views. h2. OLAP Cube View {styleclass: Class=topLink}[top|#top]{styleclass} An OLAP cube is a pre-aggregated structure on your database. Like a data mart it already contains a set of dimensions and measures which have been pre-aggregated to support rapid reporting. # To create an OLAP cube view select OLAP cube from the author drop down menu. # Choose the source connection - Yellowfin will only provide OLAP source connections for you to choose from. If no source exists you will have to create a specific OLAP source connection record. # Choose the cube from a list of available cubes. !olap.png|thumbnail,border=1! {color:#C00000#c00000}{*}Note:*{color} When creating an OLAP cube as a view you will have limited options for updating field information. This is because most of the metadata is already contained in the cube itself. h2. Stored Procedure {styleclass: Class=topLink}[top|#top]{styleclass} With Yellowfin you can connect to stored procedures running on your application database. # To connect to a stored procedure select the stored procedure options from the create view drop down list. # Select the Database and then the stored procedure you wish to connect to. !sp1.png|thumbnail,border=1! # Click the next arrow to continue to the stores procedure parameters page. Yellowfin will automatically detect parameters which exist in your stored procedure and display this list on the page. # You must fill in a value for each parameter. The value is only used to return column at this stage of the view builder. (The non-return fields will become automatic filters on the reports created from this stored procedure). # When you have completed the parameter section click accept to return the list of fields in the result set. !sp2.png|thumbnail,border=1! # Complete the metadata as you would for a standard view. Note that the non-return parameters exist as filter fields. !sp3.png|thumbnail,border=1! # Filters will be added into each report created from the stored procedure automatically. They will not be visible on the report data page but will be displayed on the report filter page. \\ \\ {horizontalrule} {styleclass: Class=topLink}[top|#top]{styleclass} |
Page Comparison
General
Content
Integrations