Categories
- All Categories
- 126 Oracle Analytics News
- 22 Oracle Analytics Videos
- 14.5K Oracle Analytics Forums
- 5.5K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 47 Oracle Analytics Trainings
- 7 Oracle Analytics Data Visualizations Challenge
- 4 Oracle Analytics Career
- 8 Oracle Analytics Industry
- Find Partners
- For Partners
BIP Editor is not giving relevant error like TOAD and SQL Developer
Description
BIP Editor is not giving relevant error like TOAD and SQL Developer
Use Case and Business Need
BIP data set editor is not giving relevant errors always use to give same error for different type mistakes.its very hard to figure out exact issue.
if it shows relevant error like TOAD,SQL developers it will helps developer to correct error very easily and repidly
Original Idea Number: ac6a63473a
Comments
-
Agreed. Sine we have to the queries in the web, it would be nice if there was a simple SQL editor incorporated into BIP.
0 -
Agree.
0 -
Hello,
definitely! If it could at least indicate the line number of the issue, that would help.
Personally I've found a partial workaround by using a local "Oracle SQL Developer" installation (free from oracle), that I use as a SQL editor.
It cannot connect to the database, but at least it will underline some of the most common errors, like the missing commas, mismatching brackets, misspelled keywords, etc.
Also, the SQL auto-format feature is very useful,
When I paste the code in BIP I'm much less likely to get those errors,
hope this helps,
cheers,
Géraud
0 -
Yes you may choose the language as SQL and try to paste the code in Textpad and Notepad++ and you should be good.
0 -
Having to copy and paste back and forth completely defeats the purpose of having a cloud based application though.
0 -
hmmm.
Cloud also has its own set of limitation.
I mean it is a surprise that organizations wont implement HCM Cloud only because this feature is not there.
Alternatively, you may use the SQL Builder option too.
Note: My personal opinion.
0 -
Actually the error messages confuse, and are a waste of time. Sometimes it sounds, it is better to create on SR per SELECT term you need to write and let Oracle use the SQL Developer access in bahalf of you
Regards0