• State Suggested Answer
  • +1 person also asked this people also asked this
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 8 subscribers
  • Views 4430 views
  • Users 0 members are here
Related Discussions
Home » Discussions » General

a!queryEntity: Invalid Query Parameter

erickp

Trying to understand why on the process history for the instance below I see the error on the first screen shot. On the SAIL task on the second screen shot, the task name for the task is coming from an expression rule and that expression rule has a query entity (not best practice, I know)

Has anyone experienced this issue in the past?

 

 

  Discussion posts and replies are publicly visible

  • 0
    Certified Lead Developer
    For the line that has the Error (Start), is that the start node? If yes, does your PVs have default values or are they passed in? If they are null at start, does your rule handle nulls? The rule is looking for a parameter to the query and not seeing it at that time. Just a thought.
  • 0
    Certified Lead Developer

    Can we see the code inside P360_qry_r_getPriority rule?

    Did you check that above rule working properly to get the data from DB? Sometimes this error will come if the DS not get verified properly.

  • 0
    Please post the code inside P360_qry_r_getPriority rule. Also check if the variables you are using in the query rules have some value (be it default/passed in). It looks like some input parameter is missing from the call. I also agree with ravichandrat, make sure your DS is verified with DB.
  • 0
    A Score Level 1
    Hi Eric,

    I came across such thing long time back and it usually comes when we use dynamic display name of the task either with some expression rule or the pv whose value is determined through some other source. Task in the task queue is also sowing the same name right? The error which is shown in the above is like you are calling some external source using query parameter which is not present in that particular table or view on the destination.

    As Ravi mentioned, If we get to see the code of that particular rule then we may able to corner the issue.
    Thanks
  • 0

    Hi erickp,

    Issue is in P360_formattaskdisplaynamewithinstanceid rule where you are using p360_qry_r_getpriority rule and variable which is passed in this rule is coming as null.
    to resolve the issue you need to add a null check of that variable before using that query rule and then needs to check why the variable is coming as null (according to requirement).

    Error is coming on the process history because history always shows the task display name and your task display name is throwing the error

    Hope this will help you.

    Thanks
    Shafaly

© 2025 Appian. All rights reserved.
We want to hear from you! Submit a review on Gartner or G2.