Cognos Text box Prompt: Oracle Invalid number error - oracle-sqldeveloper

I have a text box prompt where user can enter a amount from 0 to 100,000. I have the below code in SQLbut it is throwing Oracle invalid number error.
Amount = #prompt('p_amnt','string')#

Related

While creating test cases on DevOps i am getting error as Steps exceeds the maximum allowed length of 1048576

While creating manual test cases on the DevOps platform, I am getting the following error after 19 steps.
Error: TF401262: Value of long text field Microsoft.VSTS.TCM.Steps exceed the maximum allowed length of 1048576.
I am adding Action and the expected result fields for each step.
Expected Results contains text and reference screenshots.
After the 19th step, it is not accepting screenshots in the "expected result" field.
While creating test cases on DevOps i am getting error as Steps exceeds the maximum allowed length of 1048576
Generally String fields take a max of 255 characters. PlainText/HTML will take a max of 32K. If it crosses this limits, you can try to store it to a file and add it as an attachment:

Need Command button to open record ID range using text boxes

I have 30 reports to open to file my sales tax based on installs in different areas. I made a query and report for each area with criteria in each query under PaymentID stating Between FromPayment And ToPayment My issue is that i have to open each query and enter the ID 30 times.
Can I make a text box range and button to open all reports at once by filling in the text box on a form ONE time. Not sure how to do this. Please help.

$P{LoggedInUsername} and data from a user in a WITH-clause

I am using JasperSoft Reports v.6.2.1 and when running a report within the Studio preview the output comes after 2 seconds.
Running the same report (output xlsx) on the server takes > half a minute - though there is no data volume issue (crosstab, 500 lines, 17 columns in excel, "ignore pagination" = true).
I am using $P{LoggedInUsername} to filter data within the WHERE-part of a WITH-clause (based on the user's rights), run the report and realized, when using a fixed value (the user's id as a string) instead of the parameter in the query, the report execution speed is good.
Same against Oracle DB from SQL Developer - the query resultset with a user's id string is back in 2 sec.
Also the output of $P{LoggedInUsername} in a TextField produces a String.
Once switching back to the $P{LoggedInUsername}-parameter in the query, the report takes ages again or runs out of heap memory in the Studio/server.
What could be the issue?
Finally my problem was solved using the expression user_id = '$P!{LoggedInUsername}' instead of $P{LoggedInUsername} in the WHERE-part of my query.

My admin not working during install payment charge extension installation process

I need to import Bulk description of products, in my csv 1200 records are there, 800 records import successfully remaining not import, i get error like :
SQLSTATE[HY000]: General error: 1366 Incorrect string value:
'\xA0Ideal...' for column 'value' at row 1
save your file using notepad++ or the one that you like and select UTF-8
you are surely using some other format that it is NOT utf-8

How to remove the message below?

Message => FRM-40831: Truncation occurred: value too long for field PHONE.
I have table named 'CLIENT'. The table has many fields. One of the field name is 'PHONE'. The field data type and length is VARCHAR2(20 byte). By using the 'CLIENT' table I have created a form using Forms Developer 10g. It works fine. But I have changed the field length and Forms Property Value as VARCHAR2(40 byte) and Forms Property > Maximum Length = 40. Now the Form data save smoothly. But when I am going to retrieve data the message shows => FRM-40831: Truncation occurred: value too long for field PHONE.
N.B: The message shows when it gates the value over than 20 characters otherwise not.
How to solve the problem?
Please help me.
Apparently you are facing the multi-byte character set problem.
Define your column as VARCHAR2(40 CHAR).
Currently the column can contain only 40 bytes, so if - as I assume - you use multi-byte character set in your database, the truncation occurs.