Thanks for the clarification Alin - I don't think this is doable. This idea has been set to Needs Votes, which will help prioritize any future enhancements in this area.

Hi Alin - Are you formatting your measures to currency? There is a bit more control for decimals for currency, but maybe I'm not fully understanding the issue. Here are the controls for currency:

@mgoswami @Rajakumar Burra - thanks for the additional details.

Hi - Thank you for submitting this idea, I believe the new option would be to do the equivalent of a union of multiple sheets in the Excel into a single "Table" in the dataset. This is something that we have been exploring as a candidate for the roadmap, but community votes will help us to prioritize the feature. QQ - is…

Blends in OAC are based on a left join. This is because blending is often used for combining data sources that are not directly related. However, if you wish to use other types of joins, this is possible in the Dataset Editor, where all the common join types are supported between tables and LSAs. At this time, there is…

Hi Kartik - thanks for submitting this idea. In order to assist us in considering and prioritizing the idea, I have set the idea status to Needs Votes.

Thanks for submitting this Idea. This is a very interesting idea and request. I'll set the status to Needs Votes to assist us in prioritizing.

Hi - thank you for submitting this idea. We will set this to Needs Votes as this will help us internally prioritize this idea for consideration. But I believe this will be a very popular request.

Thanks for the additional details. We will review and get back to you if this is something that can be considered for a future release. To better understand if this is a widely requested feature, I will set the status to Need Votes.

We are aware of the limitation to create hierarchies in datasets and are working to fill that gap. Once this is doable, users will be able to create calculations at each level. We will keep you updated as this capability gets closer to a release.

Thanks for your submission. We need more information about your request. Currently if you are creating a multi-table dataset, the goal is to create a single dataset for workbook consumers from multiple joined tables, files, etc. So there is a requirement as you say to join the tables in the dataset. If you would like to…

Hi, we are aware of this limitation and are working on a solution. We have a story in the backlog that will address this issue. FYI this is a duplicate of an existing IDEA - once this makes more progress I will provide an update.

Hi, as you have already noted, the values shown in the Grouping dialog are based on representative sampling and in some cases, low frequency values in columns will be missed. We are exploring both options to increase the sampling for profiling or allowing full sampling, but we are also exploring options of the dialogs such…

Based on the errors you report - it looks like you are trying to replace the excel/csv files in the workbook. If there is a file based dataset and you want to replace the original file for that dataset with another file that either has fewer or additional columns, this must be done in the Dataset Editor using the Edit…

Just an update on this - in the OAC March 2024 update, we introduced the ability to use time-series calculations (using TODATE and AGO functions) for datasets. We are still evaluating the ability to create time hierarchies in Datasets - but just wanted to update this Idea with the new capabilities introduced in March. Here…

Also note that renamed columns also pose a challenge, but that would be an enhancement to "map" the renamed columns to their existing transforms.

A few follow up questions: Are you referring to datasets based on files or from a DB - and are you referring to a manual "Reload" of the data in order to update the columns, or the automated Manual or Scheduled reload from a DB Table? Each of these have their own restrictions. DB Table metadata changes are more restrictive…

Just to clarify, the metadata screen would have the original DB name and the current name of the column. In the case of a dataset created from Manual SQL, we would only be able to list the name of the column from the SQL and then any subsequent changes.

Thanks for submitting your idea. It is not clear from the submission that you are aware of the right click and Open on the Dataset option? This will indeed open the dataset in the Dataset Editor and not the Workbook.

We continue to make progress on the infrastructure required to make defining hierarchies in the Dataset Editor possible. But we don't have any estimated time to deliver this feature yet.