nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Oracle Communities

Oracle Analytics and AI

Child Item

Allow changing format of date columns in visualization for authors w/o write permission to data set

Michal Zima

Organization Name (Required - If you are an Oracle Partner, please provide the organization you are logging the idea on behalf of):

Czech National Bank

Description (Required):

Currently (we are on OAS 6.4) it is not possible to change format of date/date time column for users without possessing write privilege to corresponding data set (in visualization properties, Date/Time format tab). This is very restrictive (since for measures this is possible) and from security perspective, we really don't want to give to potential authors (creators of DV workbooks on top of data sets) write permission to corresponding data set/s.

Use Case and Business Need (Required):

Allow authors (workbook creators) to change format of date/date time columns in visualization without the necessity to give them write permission (which is strong permission, allowing to modify definition of DS) to corresponding data set - this violates security rules.

Enhancement Request / Service Request:

Find more posts tagged with

Under Review

Analysis and Data Visualization

Status: Under Review

Comments

Luis E. Rivas -Oracle

Hi Michal, I believe what you are asking for is already possible. Users with only read access to datasets can change the data formats in Workbooks at the Viz Level - Please review the below for more details and the Blog for additional details - let me know if you use case/request is different.

Overriding the Default Format in the Dataset in Workbooks

Once the default formats have been set in the dataset, users can override them on individual visualizations based on their requirements. If you select the column from the Data Elements Tree, the properties panel shows the default formats and you can’t override them globally. To override the default formats in workbook visualizations, follow these steps for each visualization. Select the visualization and notice that a visualization Properties panel is displayed. Locate the pound icon (#) for number or the clock icon (?) for dates, and you can change many of the default format settings to your requirements.

Overriding Default Number and Date Format in Workbooks

Refer to this blog: https://blogs.oracle.com/analytics/post/four-oracle-analytics-dataset-editor-tricks-every-dataset-author-should-know

Michal Zima

@Luis E. Rivas -Oracle - Luis, unfortunately you are only half right.

Users, having only read permission on data set, can override formatting for measures on visualization - as you correctly pointed - in visualization properties on Values tab- pound icon (#). But the same does not pay for overriding default formatting on visualization for date columns - properties on Date/Time format tab - clock icon (?). Here, users having only read permission on corresponding data sets, cannot change anything - since everything on this property tab is greyed out. This is the behavior on OAS 6.4. Cannot comment on OAC (we are not cloud customer), but for OAS, this is definitely how I have described it. So we are expecting this (for me not correct) behavior to be changed. Thanks.

Luis E. Rivas -Oracle

@Michal Zima - Hi - What you are describing is the new default behavior of separating the dataset editing from the workbook authoring. And what seems to be the request is for users without read/write access to the dataset to be able to change the default data formats - this behavior in the past caused issues because if would also change the behavior and default formats for other users in other workbooks. Is your request for the workbook user to be able to change the default format only for the workbook they are working on? Please describe the use case in more detail, and we can determine if this is a good general solution for other users. thank you.

Michal Zima

@Luis E. Rivas -Oracle You ale a little bit contradicting yourself in your statements, Luis.

First you mentioned, that it should be possible to change/override default format of date columns in particular visualization in workbook (for authors with only read permission for data set) - similary as it possible for measures in worbook (ponting to blog, you have written). And now, you declined it, claiming, that this is new behavior….

So to make it clear: We are not requesting behavior, where user with read permission to data set should be able to change default format of date column of this data set. But this user should be able to override/set his own format for this date column in particular visualization in workbook, he is creating on top of this data set (thus just for this visualization in workbook, using date column from data set). Is this clear enough ? Basically allow the same, what is already possible for measure columns in worbook/visualization.

Michal Zima

@Luis E. Rivas -Oracle Hi Luis - back to your question:

"Is your request for the workbook user to be able to change the default format only for the workbook they are working on? "

Answer is: Yes, this is what we want - to allow author (with read-only permission to data set) to change format of date column just for the workbook (or more precisely visualizations within this workbook) he is creating. Thus this change in formatting should be solely done in workbook definition, not influencing default format for date column, at data set.

Michal Zima

@Luis E. Rivas -Oracle Hi Luis, I just wanted to ask you, whether my specification is clear now and it is sufficient for you to evaluate it ?

Thanks and regards

Michal

Luis E. Rivas -Oracle

@Michal Zima - yes thank you - I have changed the status to "Under Oracle Review" and it will be forwarded to the appropriate team for this area of the product. Thank you for your idea.

Michal Zima

@Luis E. Rivas -Oracle Hi Luis, do you have any news regarding this Idea (created in June) - it is still since then in status "Under Oracle Review" - is there a plan to include this ability into future releases of OAC/OAS ?

Thanks for update and regards

Michal