@Jorge Olmeda I guess your question is how to color your bars without changing the grain, which will cause the gaps that Ben has in his image. The best solution for this scenario is to use a stacked chart.

My bad. Disregard the reference line for now. Currently, we can parameterize it only if the category is of a Date data type, but in your case, it is not. Sort should work if you set it up correctly, and I also have an idea for you for the highlight. Here is the example I built. I'm using two selectors to change the sort…

in order to sort by category, you can create a My Calc that is filtered by the specific category that you want to sort by (i.e. FILTER(Revenue USING Product = 'Apples') ) and then sort you X-axis attribute by the new calc that you created. Note that since it is a 100% stack chart and the calc is in actual numbers and not…

Hi Helen, It is hard to see the issue in your screenshot. Did you open an SR on this topic?

@Narayanan Ramachandran Can you DM me the SR number? I agree that support should be able to help when you are trying to follow the documentation and run into issues. @Pedro Albuquerque The capability exists, and the discussion revolves around the complexity and challenges of deploying the elements required to enable it on…

SQL and SQL-based tools are usually sorted based on ASCII order, where the uppercase letters come before the lowercase letters. The solution is usually to create a calculated field that uniforms the case and is used as a sort key. A feature coming shortly to workbooks will allow you to use a sort key in visualization while…

@Michal Zima Yes, if it lands in January, it should be in OAS.

We are trying to get this done ahead of OAS 2025. We will update you once we make more progress.

This one is currently planned for November January.

Update: Customer home page groups is planned for November Datasets in catalog folders are in 1H 25. While we were hoping to get it done in time for OAS 2025, at this point, we do not believe it will be feasible.

Update: Currently planned for November.

The dataset editor allows you to add and rename columns. Analytics tools are not generally tools for modifying individual rows, but some facilities allow you to do that in bulk within OAC. e.g. I can fix a misspelled Sidney to Sydney, but it will fix all rows with that error. I can also use the grouping tool to bulk rename…

@User_YBCVZ do you have a filter or a parameter selector? If you drag a column over from the subject area, it is a filter, i.e. the value that you select will be used to slice the data in the query. If you drag a parameter, you create a parameter value selector, i.e., the user will select a value for the list of values,…

Can you provide a more detailed example? I'm not sure I understand which columns the data flow should add. Are you referring to the fact that 'add column' step before the 'select column' step will not automatically add the column to the selected list, but it will be in the removed list?

I guess the question would be, which is worse? If you have one dataset with 30 columns and one with 28, you will either need to create two dummy columns in one or, alternatively, map the 28 out of 30 to the 28 existing one so the system will know which two columns are the missing ones. We can use the existing matching…

You can use the VALUEOF function to read variable values.

I'm not sure I understand. You can store the filter value in a parameter by binding a parameter to the filter. This allows you to use that filter value in various ways. When the filter changes, the parameter will always store the current values.

@Rajakumar Burra can you share an example dataset? I was not able to create the same outcome.

I would not define that in that way; it does allow Workbook parameters to drive the values of request variables, which, in turn, can impact what is presented in classic reports. However, I consider "passing parameters" to be a different type of gesture.

The assumption that "OACS only apply user filters or data-level security after the SQL in data set returns ALL data" is not correct, especially for ADW (assuming your dataset is set to live). When possible, OAC will push down filters to the physical source. The specific caveat concerning the attached support doc is that it…