User_SYYDG, If you are adding this "footer" to a table view in a classic analysis, you have two choices: Add aggregation to your table view, as illustrated in image1, below. In your Compound Layout, add another view below the table view—one that has only the total count of rows, such as a pivot table or tile. This is…

I have no experience using the Tile in a DV workbook, but maybe my experience with classic analysis will help. In an analysis, a Tile will only work when the column is treated as a measure. To get your character string output to be treated like a measure, set the Default Aggregation rule field (to something other than…

Hi User_SYYDG, What interface are you using — classic analysis or DV workbook?

Hi User_SYYDG, The formula within single quotes has an extra closing parenthesis, and the column names have closing double quotes but no opening double quotes. Any of these problems would cause an error, but I am also wondering about using EVALUATE() to evaluate the result of a condition to TRUE or FALSE — this might not…

Yes, the logical dims should have the physical aliases as their source tables.

Hi. Create aliases for your dimension physical table—one alias per join to the fact table.

Subhakara split his data flow into multiple data flows/multiple datasets, which were united in the analysis or workbook using a UNION query,.

Thank you! I looked and looked for that information, but could not find it. Thank you so much!

@Bala.01 As I understand the error, it probably means you have included a column formula that uses the result of another column formula, when both columns are derived within the same SELECT statement. If you need the result one derivation (col1) to be used by another derivation (col2), then you have to put the col2…

Try combining your 3 logical table sources into a single table source that includes all three tables.

Is the list of values static, or does it frequently change? If static, you can use Specific Column Values instead of SQL Results. If you have Data Visualization, you can use a DV Dataset as though it is a subject area. You can upload the list as a file to DV, which will become a Dataset. Or maybe you can create a direct…

Yes, GT86, I mean columns in a subject area. :)

Hi GT86, You cannot do a direct database query within the dashboard prompt. If you use the SQL Results option, it has to be a logical query. Do you have any presentation columns that contain the values that you want to show in your choice list?

Hello GT86, Here are two sample conditions that use presentation variables: nvl(org.ORG_NAME, 'NULL') in (@{TS_Org.isAllColumnValues?NULL:TS_Org}['@']{nvl("ORG"."ORG_NAME", 'NULL')}) requests.REQUEST_TYPE in (@{TS_Type.isAllColumnValues?NULL:TS_Type}['@']{"REQUESTS"."REQUEST_TYPE"}) There are 4 things you should notice:…

The column was already defaulted with 'Repeat' option as below. Hmmm… Saving as the system-wide default has always worked for me, but I have not encountered an example that already had the desired setting as the default. However, i tried saving as you mentioned. There is no change to the behavior. You might try picking…

You should be able to use a logical SQL query for your dataset. If you built a union query in classic Answers, its logical SQL can be copied from it and then pasted into a manual query in DV. Instead of pulling the subject area into your dataset, pull "Manual Query" into the dataset and paste the logical SQL into its…

All the columns are suppressed by default. Hi Bala.01, I have 2 questions: Is this pivot table a DV Visualization, or is it a view in Answers? From where are the columns being pulled — from an uploaded file or from a subject area? Columns from subject areas can have their default properties changed if done in the Criteria…

Well, it did work for a while, then I began getting the same error message again. I will try the original solution, which was to write multiple datasets and unite them in the analysis or workbook.

Thank you, Brendan! It works very nicely to split the single filter into two, then union the two filter results together within the same data flow.

@Subhakara Netala-Oracle What did you finally do to resolve your problem? I am experiencing the same issue.