Suggest an Idea

[simonaubert]

Hello all,

Here is a real big issue I face on a new project with an Oracle Database : all the id are integer (cool)... but 15-16 digits integers. Oracle allows that kind of stuff (actually, if I understan https://docs.oracle.com/cd/E18283_01/server.112/e17110/limits001.htm it can goes to 38 digits !!).

Si, what's the heck ?

Qlik Sense only allows 14 digits numeric fields. This is related to IEE754 (https://ieeexplore.ieee.org/xpl/mostRecentIssue.jsp?punumber=4610933 )

Some posts on the issue, to see it's quite a big deal :
https://community.qlik.com/t5/New-to-Qlik-Sense/Problem-with-big-numbers-more-than-14-digits/m-p/369...
https://community.qlik.com/t5/QlikView-App-Development/Problem-reading-numbers-over-14-digits/td-p/1...

https://community.qlik.com/t5/New-to-QlikView/calculation-issue-for-14-digits/td-p/1197424

Of course, there are turnaround with the Evaluate function or the casting in text (to_char in sql may do the job) but this is really, really, really inefficient in term of performance when you have 500 millions of line !!

Best regards,

Simon

[Patric_Nordstrom]

Thank you for your feedback on ways to improve our product. While this is something we understand would be useful, it's not on the short-term roadmap. Please continue to show your support for this idea.

Thanks,
Patric

[Meghann_MacDonald]

From now on, please track this idea from the Ideation portal. 

Link to new idea

Meghann

NOTE: Upon clicking this link 2 tabs may open - please feel free to close the one with a login page. If you only see 1 tab with the login page, please try clicking this link first: Authenticate me! then try the link above again. Ensure pop-up blocker is off.