Oracle Communities

Oracle Analytics and AI

Child Item

AI Assistant throws error for column name having the character '$'

Hi Team,

We have recently started using the AI assistant in OAC May Update. We did the indexing for a subject area and tried the AI assitant for it. But we have noticed that for all the measure columns where we have the character as '$' in the column name the asistant throws error. I also saw a blog which suggested that special character migt create an issue so we tried to give synonym as well for the said column but the error persists. Any workaround or anyone else who has seen the same issue.

Find more posts tagged with

Oracle Analytics Cloud

Oracle Analytics AI Assistant

Accepted answers

Bret Grinslade - Oracle Analytics-Oracle

This looks like an issue with the Assistant which I can repro. As a work around — you could rename the column in a dataset to something from say $ Amount to USD Amount … for now.

Jacques V.-Oracle

You should definitely an SR for this. I believe this is currently a known limitation on special characters. We do not allow these chars in the synonyms either.

Filing an SR will allow you to track our progress to changing this.

As @bret mentioned , Renaming or creating a duplicate column without that char in the SA could allow you to move forward for now.

All comments

Benjamin Arnulf-Oracle

+ @Jacques V.-Oracle for review

Bret Grinslade - Oracle Analytics-Oracle

This looks like an issue with the Assistant which I can repro. As a work around — you could rename the column in a dataset to something from say $ Amount to USD Amount … for now.

Jahnavi-Oracle

Thanks @Bret Grinslade - Oracle Analytics-Oracle .

We are trying that work around as well. But we have around 15 subject areas with the similar measure names, so it would be a big change to do and also to let the users make aware of it. Is there any bug raised for this issue which I can share with the customer? if there is please let me know.

Jacques V.-Oracle

You should definitely an SR for this. I believe this is currently a known limitation on special characters. We do not allow these chars in the synonyms either.

Filing an SR will allow you to track our progress to changing this.

As @bret mentioned , Renaming or creating a duplicate column without that char in the SA could allow you to move forward for now.

Jacques V.-Oracle

We communicated with Dev about this issue, and they are working to get this resolved.