![]() By suppressing the newline, the problem seems to be resolved. May come between the SELECT clause and the first column. This format is 'yyyyWww-d' where yyyy is the year, W is as separator token, ww is (01-53) week number and d is (1-7) day of the week. I would build a calendar table with a ISO-8601 week-within-year format column in addition to the usual Common Era date. It seems than when using a SQL formatter a bad newline char (return, …) Since SQL is a database language, we prefer to do look ups and not calculations. Unresolved table: "(SELECT MyTable.M圜olumn saw_100, FILTER(". ![]() Support nQSError: 27004 - Unresolved table Odbc driver returned an error (SQLExecDirectW).Įrror Codes: OPR4ONWY:U9IM8TAC:OI2DL65P:OI2DL65P In dashboard, Setting / Administration / Issue Sql ORDER BY D.saw_0, D.saw_1, D.saw_2 The result in answer ( Select Products."Prod Name" saw_0 FROM SH WHERE Products."Prod Name" = 'Bounce' ) C WHERE Calendar."Calendar Year" IN (2000, 2001)ĪND Fiscal."Fiscal Week Number" BETWEEN 20 AND 30 ) B, ( Select Calendar."Calendar Year" saw_0, Fiscal."Fiscal Week Number" saw_1 SELECT C.saw_0 saw_0, B.saw_0 saw_1, B.saw_1 saw_2 FROM (Calendar."Calendar Year" IN (2000, 2001))ĪND (Fiscal."Fiscal Week Number" BETWEEN 20 AND 30) The cross join and the outer join select D.saw_0, D.saw_1, D.saw_2, A.saw_3 However we get only 18 rows because weeks 25 and 26 are missing in 2000, and weeks 26 and 28 in 2001. In this example, we would expect 22 rows of data (11 weeks each from 2 years) if the data were dense. ![]() SELECT SUBSTR(p.Prod_Name,1,15) Product_Name, OBIEE - Date Format in presentation variable, dashboard prompt and logical SQLĪ typical situation in the sh schema with a sparse dimension is shown in the following example, which computes the weekly sales and year-to-date sales for the product Bounce for weeks 20-30 in 20:.OBIEE - Densification / Dimensions Preservation Possibilities.
0 Comments
Leave a Reply. |