We have several database columns that are saved in UPPERCASE. End users would prefer to see the data in proper case on reports and dashboards. Please add the INITCAP function to the String functions available in OAC.
@MGibbs_2023 — if this were an option in the dataset editor — is that sufficient?
@Luis E. Rivas -Oracle This seems useful.
@MGibbs_2023 I agree adding Initcap would be a useful addition for case handling. In the meantime, Sentence case may be a good workaround for now, it will uppercase the first word in the text and lowercase all others.
If your data is in Oracle DB you can do:evaluate('Initcap(%1)',Employee."First Name")
@Martin_Gibbs_Mayo Please could you comment if the above solution is helping. I will close this request.
@Benjamin Arnulf-Oracle and @Gabby Rubin-Oracle , while the EVALUATE workaround works, but it comes with a SQL Injection Risk and hence EVALUATE is not permitted by a lot of customers. Having a native INITCAP function would make this a clean approach rather than writiing complicated Substrings and Upper/lower concatenations.
With the OAC Visualization AI Skill, users can potentially extend existing custom visualizations and address limitations encountered in real-world use cases. As an example, we used the AI Skill to enhance the OracleVectorMapsH3 visualization from approximately 10,000 data points to a version supporting up to 50,000 data…
Currently, the Purchase Requisition Redwood page provides an option to export Purchase Requisition information. However, business users also require the ability to include additional downstream transaction information in the same export. We request an enhancement to make the Redwood Purchase Requisition Header and Line…
When new analysts join, getting them confident in OAC takes a lot of hand-holding. The learning content exists, but it's scattered and none of it lives inside the tool. Managers also have no easy way to see who's ready to build and share content. It would be great to have: A "Learn" panel in OAC with short guided paths by…
Add a workbook or dataset setting that automatically hides or rounds values below a set threshold, for example counts under 5, across all visualisations. Suppressed values would show as "<5" or "*". It should also stop the hidden number being worked out from totals or subtotals, sometimes called secondary suppression.…
Add an accessibility check to Data Visualization workbooks, similar to the one in Office, that runs before you share or publish. It would flag: Low colour contrast between text, data labels and backgrounds Palettes that aren't colour-blind safe, with a suggested alternative Visualisations with no title or alt text for…
