I have two data providers. One is a universe, one is an excel file. Excel file has column ID. I want to find ID,JOB_ID, Cost
I have created a merged dimension:- ID. When I create report with ID and Cost, I'm getting an outer joined result which is what I want. But when I add another attribute from universe it is being inner joined result. Where can I control this feature
You are ever so close. Here are the basics when working with a zero or one to many relationships. Credit for this goes to this blog post. I am copying it here if perchance that link goes dead.
As a rule of thumb , when trying to merge DP’s with a 1xN relationship
:
Merge the common fields
Use the dimension coming from the N side query
Create detail variables from the 1 side query for each dimension needed with associated dimension equal the merged dimension
Check "Show rows with empty dimension values" on Table formatting for each table using dimensions coming from both queries.
Here is a screen shot to highlight where to find the setting in step #4.
Related
Tables in Question
I don't think I am going to be able to do what I am trying to, but thought it would be worth asking the question. In my point of sale system there is no report available for a specific type of order so I am writing a crystal report to be able to view the order type in question. Unfortunately the POS system only saves the document sequence field in one table. The document sequence is the number that is shown on a document when viewing it, all of the DocIDInternal numbers are gibberish that are not visible to employees when pulling up a document to view it.
I would like to be able to view the document sequence for both the order and the associated purchase order on my report, but I can not find a way to link both into the Documents table to access the document sequence without breaking the report. As far as I can tell I am able to link either the order or the purchase order to the document table, in order to view the document sequence field for one or the other. Neither the order table or the purchase order table contain the document sequence and it is only available through the documents table. I have searched and been unable to locate any other tables available to me that contain the document sequence field other than the documents table.
If you open Database Expert and go to the Links tab where you took the screenshot above. Double-click on the line linking your OrdersDtl and Document tables to edit the link. On the left side is a set of radio buttons that define the type of join to use with the tables. Try changing this value to "Left Outer Join" if the current selection is "Inner Join". This should solve the problem with it breaking the report, but I suspect there is more to troubleshoot before you will have the data your want from the Document table.
When Inner Join is used as the type of join, if there are no records found on the Documents table that correspond to the value of DocIdInternal on the OrdersDtl table, then the query returns no rows. When Left Outer Join is used, the query will always return all rows from the table on the left side of the join, even when no corresponding records are found on the right side of the join.
Once you have the report returning data again, now we need to determine why there are no records being linked from the Documents table. To do this, I would place the DocIdInternal database field on your report so you can verify it has a value on the OrdersDtl table. You may need to discuss this with your Database Administrator to determine if this is the proper way to link these tables.
I'm new to Pentaho.
This is the transformation I'm trying to do:
Import Transactions and Merchant and merge these two tables using MERCH_KEY
However, this isn't working, see below:
This is table Transactions:
And this is table Merchant:
And this is the Merge join:
This all seems good, but it's not working and I have no idea why.
From the preview, I can see the two tables are being imported, so how can I merge them?
Remove all fields except "MERCH_KEY" from the right-side list.
The Merge join step is a little misleading with its behavior, as it only allows you to click Get Fields and get ALL fields, but doesn't let you pick a single field in a dropdown.
As the name suggest, these are the key fields that will be compared in the join, so fields need to be in the correct order. In your case, you only need the one. The other input fields (from both tables) will be automatically added to the output stream, with fields from the second table getting renamed if duplicated.
I have a fact table containing lines of different types. Based upon each type I have a different dimension table that I need to connect. Is there a solution to this problem without creating different fact tables for each type of line?
When connecting the fact to one dimension, I get the error that one key cannot be found in the dimension table. That's right, because that value exists in another dimension table
Here a picture of what I intend to achieve:
I have a DimPerson table and a DimPersonDecileOutrigger Table which stores decile data. The way the outrigger is structured is that a customer is given a decile for current year and previous year (if they have bought in the period)- which means a customer might have TY and NOT LY and vice versa. Some customers are both.
In ssis when I picked the columns in dimension structure- I initially only picked columns from DimPerson and not the outrigger. That way in the browser it showed all the id's starting from 1. But when I dragged some columns from outrigger- then in the browser it doesnt show all personID's. I want to see all customers regardless of them having a decile or not.
Pic attached to show what it looks like in dimension structure tab. Also the relationship is between OutriggerID as primary and OutriggerID in person as foreign.
If you just want to solve the problem, you can create a View in your underlying relational database that uses LEFT OUTER JOIN to link the two tables, so that the view will return all rows from DimPerson, even if they don't have a Decile.
Then use the view as the source for your dimension instead of the tables.
I have three tables, one fact and two dimensions. I want to make a referenced relationship between the fact table(measures) called InternetSales and the Geography table, se image(schemaCubeStructure".
The intermediate table is Customer. I first create the Geography and InternetSales tables and then the Customer with a field from Geography to use later when creating the ref. rel.
Everything works fine until browsing the data in the cube (se image "errorBrowseSalesCube". If i don´t make the relationship between the two tables i get image "correctBrowseSalesCube" which is what i want. That is i don´t get any data when processing with the rel.ref.
See image "dimensionUsageSalesCube for rel.ref.
Why is that i don´t get any data?
correctBrowseSalesCube
errorBrowseSalesCube
dimensionUsageSalesCube
schemaCubeStructure
What fields did you use when setting up your reference dimension relationship between Georgaphy and Internet Sales?
The in the AdventureWorksDW database, the Georgaphy dimension is a snowflake off of Customer dimension. In the AdvWrks cube project, Microsoft includes the geography table and corresponding attributes in the customer ssas dimension (red boxes in screenshot below). However, they could have, as it looks like you are trying to do, simply added the GeographyKey to the customer dimension (red arrow in screenshot below)
This exposes the GeorgaphyKey field when creating the reference dimension relationship so that you can properly define the relationship between the intermediate dimension (customer) and the reference dimension (geography):
After that, you can properly browse the Internet Sales facts by Georgraphy dimension attribute (and user) hierarchies:
The correctBrowse sales cube can be easily explained. It means that the data is not calculated based on the Geography dimension and thus indicates that the connection between the Internet sales and the Geography is not correctly calculated.
I would suggest the following:
Try making the customer a Mesaure (or fact table). Do not rename it just make a measure i.e. the count of customers (can be used as a counter of customers/per region or can be invisible altogether).
Then The customer will appear as a measure in Dimension usage and then connect Geography to Internet sales via a many to many relation Using the customer measure table.