Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
4 replies
Subscribers
8 subscribers
Views
1605 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
General
I have created a query rule which takes a date and text. I am calling it using =
karls
over 10 years ago
I have created a query rule which takes a date and text. I am calling it using =rule!FR_getCommunicateScheduleForNotifyDate(today(),"RSD"). I get the following error
Expression evaluation error in rule 'fr_getcommunicateschedulefornotifydate' at function 'queryruleexec': Error evaluating function 'queryruleexec' : Unexpected error executing query (type: [FRRATESCOMMUNICATESCHEDULEDT1441], query: [FR_getCommunicateScheduleForNotifyDate], order by: [[]], filters:[(('EMAIL_NOTIFY_DATE' = TypedValue[it=7,v=2014-08-05]) AND ('COMPANY_CODE' = TypedValue[it=3,v=RSD]))])
How can I pass a date to the query rule for evaluation ...
OriginalPostID-118277
OriginalPostID-118277
Discussion posts and replies are publicly visible
0
Eduardo Fuentes
Appian Employee
over 10 years ago
In order to troubleshoot issues where the message is very generic such as: "Unexpected error executing query" you need to reproduce and then find this error in the application-server.log, once you have identified it review each of the individual "Caused by" clauses. Usually the most bottom ones (that belong to that error) will be the most informative ones in the stack trace.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
rishirajk
A Score Level 1
over 10 years ago
You should check application server log. There you can find the exact cause of this error.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
karls
over 10 years ago
Thanks I see this in the logs. ORA-00904: I will check the column names
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Eduardo Fuentes
Appian Employee
over 10 years ago
Since that code belongs to the "invalid identifier" error the place to look at is your CDT, remember that since Oracle is case sensitive you do need the @Column(name="") annotation in your XSD to make sure it maps correctly to the column names in the table. Also make sure your data store which holds the entity this query rule is querying is pointing to the latest version of FRRATESCOMMUNICATESCHEDULED and not to FRRATESCOMMUNICATESCHEDULED^X where X is a number >=1 which indicates an old version of the CDT
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel