We are encountering an issue where we are trying to fetch data through query rule and displaying the same in report.

varnikam over 8 years ago

Hi,

We are encountering an issue where we are trying to fetch data through query rule and displaying the same in report. In the expression rule it works fine and returns the correct output whereas in report, looks like the same expression doesn't work. Does anybody have any idea if the query rule works in report or not?

Currently, we are on 7.5 and the issue is consistent in both our test and prod environment.

Thank you in advance,
Varnika

Discussion posts and replies are publicly visible

0 sikhivahans over 8 years ago

@varnikam I haven't come across this kind of behavior so far and it is not expected. It would be grateful if you can let the community know about the error in detail(for instance, the error message you see on the report) and also the logs generated at the time when you experienced the error in the report.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Amitkumar over 8 years ago

If you are dealing with portal reports, your expression rule containing calls to database might not work. If that is not the case, and you are using Tempo report. I suggest you create a report using Report Builder by supplying the concerned data store entity in your case and see if data shows up. You can make use of Query Entity instead of Query Rule unless you need to show all columns data from that entity on report.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 varnikam over 8 years ago

@Amitl, I am using portal reports only. So are you trying to say there is a limitation to Appian that we can not query the database via query rule in portal reports?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Amitkumar over 8 years ago

Yes, unfortunately you cannot query a database from portal reports. It simply does not work. Though expression rules and custom functions are allowed for use in data columns but not any scripting functions.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Amitkumar over 8 years ago

Anyway, can you please elaborate your use case and problem that you are trying to solve?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 varnikam over 8 years ago

We are trying to display a field called Minor Account type via query rule on Portal report. So in the report, if we use query rule - rule!ODR_Account(pv!AccountNumber).Minor_Account_Tp and pass Account Id to it, it returns no value and that particular column is showing all empty in the report but if we write the same expression in expression rule, it works and returns the desired output.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Amitkumar over 8 years ago

Do you have a process model or process instance where all data elements for report are available and stored in a pv or cdt including Minor Account Type? If no, then process report is not a good option to combine and present data from several data sources. What's your flexibility in using ncolumntable function and prepare and present the data that you want?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel