What is the goal here? Sort order is often defined at query time. What do you hope to know or do based on "uploaded" sort order?

For the file type -- today we do use the file type to determine how to parse the file. Supported file types are: .xlsx, .xls, .csv, .text, .txt, .tsv, .tab For the ADB connection, it is not clear what is happening here. Can you make a connection with these credentials via SQL developer or other desktop tool?

Which type of report is being exported here? Is the user trying to get the visuals of a canvas from a workbook? In general -- export should not cause a timeout unless there is a time when viewing the dashboard.

Have you tried using the screen for "Edit Definition" -- this shows you a preview of the data based on the SQL you enter when using Manual SQL.

For the formatting -- yes you can set formatting options in the dataset editor. These properties on in the lower left corner of the editing screen per column.

You can see all objects via the "Content" management option in the OAC Console. You can use this to filter by Connections to see all connections. You can change ownership or identify the owners from this screen

Have you tried using Edit Definition after it is copied? https://docs.oracle.com/en/cloud/paas/analytics-cloud/acubi/filter-dataset-table.html#GUID-C39918C2-EB0B-470D-BA1C-98AB3908EFE8

As a work around currently -- a user could edit the dataset definition with a filter and then reload. If it were via some kind of variable, would you set it for every dataset reload or you would you want it to be driven by something like an RPD variable which changes independently.

You can control re-use of an exist connection by changing the Access settings on a connection. If you remove all access from a user or group -- they will not be able to create a dataset from the connection. We will need an improvement to control whether a Content Author can create a new connection, or it is not allowed.…

This is a good suggestion. Right now columns are order based on the order which they were added or where you position the selection when you add a row-wise calculated column. You can use this as a work around while we look in to this improvement. You will need to remove and re-add the columns via "edit definition"…

This idea should be directed to https://community.oracle.com/products/oracleanalytics/categories/otbi

I think this idea should be directed to the OTBI forum. https://community.oracle.com/products/oracleanalytics/categories/otbi

There is work being done around fine-grained permissions. @Adam Bloom-Oracle FYI

This is a good enumeration of the key capabilities needed and that they are required for OAS.

Michal ... might be worth to discuss. With this example, you could create a specific dataset or dataset table with the complex calculation (or even a DB view) ... making the logical SQL simple where you are just grabbing a simple item in LSQL.

No timeframe to announce. We will change the status when we start development and again once we ship it. It is a bit of a ways down the dataset improvements list and for now I would implement the work around if you can or create a Subject Area for this use case.

Michal -- can you give an example? You can use logical sql to initialize a parameter. That logical sql can reference a dataset. Would that work?

We are investigating how we can add an alternative sort column. For now the work around is to add the column to the visual and set the sorting on that extra column.

Have you considered data actions for this scenario?

To understand a bit better, you want to pass the hierarchy as an object and then set the value/level in the destination. Is that right?