Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Posting on Qlik Community is temporarily paused for some users. Thank you for patience and we'll update you soon!
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

Query error

Hi,

I got "Exception in thread "main" java.lang.Error: Unresolved compilation problems: " when I intend to join a CSV (Sales) with an XLSX (Products)  via a tMap component and to insert the output into tDB_Output Oracle table.

The error comes when I try to map a this expression row3.PRICE *row4.QUANTITY*(1-row4.DISCOUNT) to Sales_Volume target field. I attached a screenshot.

Thanks

Labels (2)
1 Solution

Accepted Solutions
Anonymous
Not applicable
Author

Re-creating the job solved the problem.

View solution in original post

5 Replies
TRF
Champion II
Champion II

Did you try this one?
row3.PRICE * row4.QUANTITY*(new Double(1.0) -row4.DISCOUNT)
Anonymous
Not applicable
Author

Have you actually tried this? The expression tester will fail when actual values are not being used. Try running the job.

Anonymous
Not applicable
Author

I got when I run the job:
"Error in the component's properties 0683p000009M9p6.pngALE_DATE cannot be resolved or is not a field
COUNTRY_ID cannot be resolved or is not a field
QUANTITY cannot be resolved or is not a field
DISCOUNT cannot be resolved or is not a field
PRICE cannot be resolved or is not a field
QUANTITY cannot be resolved or is not a field
DISCOUNT cannot be resolved or is not a field"
Anonymous
Not applicable
Author

I tried this, too. Nope.:-(
Error in the component's properties 0683p000009M9p6.pngALE_DATE cannot be resolved or is not a field
COUNTRY_ID cannot be resolved or is not a field
QUANTITY cannot be resolved or is not a field
DISCOUNT cannot be resolved or is not a field
PRICE cannot be resolved or is not a field
QUANTITY cannot be resolved or is not a field
DISCOUNT cannot be resolved or is not a field
Anonymous
Not applicable
Author

Re-creating the job solved the problem.