I am going to join the above mentioned datasets ( costrepcostandvarince ) to date & delivery_prod… datasets ) . For that joining Purpose I have created a CC field in each table ( Short Date Column )… Short Date, Short Date & Prod Short Date
. -----3
I see the Short Date column in both Date table & delivery_prod table when i try to joining… but
when i try to join costreprcostandvarince and Data table, i am not able to see the short Date column in cost table
( All CC fields that i have created in 2 screenshot not visible after adding the other 2 datasets — scrolled down too
The publish option will not be enabled unless your dataset definition is all correct. In this case since your joins are not completely defined the Publish button is disabled.
I suggest you do things one step at a time so you are able to debug the issues; resolve them and then go ahead.
Unless you share the details of the individual datasets and their data type it is difficult to say what the problem is. Since you say the Calendar Date and Deivery_prod_vol_and_variance has the required columns to join complete that and then deal with the next ones.
Check for data types; that may be one of the reasons for the issues. It may not be compatible for the columns you want to join
Hi @Giridhar.Prabhu , I have cross checked & verified the datatypes of the joining columns ( Short Date… whatever i have created those CC fields ), are same datatypes ( String - in all 3 datasets ).
Moreover, Let’s say I am about create an analysis using Data Table & I have added the Cost table ( Screenshot —3, for the joining purpose Short Date = Short Date ). After adding the another dataset, i don’t see the CC fields in Date table.
Before adding the Cost Dataset ( I am again saying all the datasets are from S3 )
( But i see that CC column in Cost Table ). Similarly, if i start analysis using cost dataset then adding Date dataset, i don’t see CC fields in Cost dataset & able to see CC fields in Date table
Pls help me out. ( Is this a limitation - not possible to use CC columns in Joining ). I would say the data Modelling is majorly causing my development + ETL also major issues in QS because most Clients give raw data not cleaned & normalized data for the report development, right?.
Besides, the data modeling using joining causing duplications or removing records in the existing datasets thus resulting incorrect data in the visuals.
Hi @Venkat.Metadata - Are you able to take one data set and publish it and see the result and then add another one and do the join and able to see the data or not. I agree with you Data modelling is very much require which is already raised to QS team and some new feature will come down the line. If you can create samples in Arena, then we can verify it .
@Sanjeeb2022 , Yeah, as you said , i took one dataset first ( which is cost table ) & published then i have added Date table but facing same issue ( not able to see CC columns in Cost table but see in Date table while try to joining 2 tables using CC columns which is Short Date).
So, i decided to join Cost & Date tables with existing columns & able to did.
Data modeling in QS is not like Power BI. The setup like Power BI is a request that many have raised and I think has been listed as a feature request with AWS.
You have mentioned CC fields/columns. Can you elaborate what you mean by these fields?
In general Calculated fields in dataset are available for joins. Refer the documentation that has the details
There may be some limitations since you have datasets from two different datasources. There is an article in the learning section. You can go through the same.
Hi @Giridhar.Prabhu , All datasets are form s3 only as i mentioned above as well in the screenshots. ( Same source ).
Issue: I am not able to see calculated fields while joining & why?
