• State Not Answered
  • Replies 15 replies
  • Subscribers 5 subscribers
  • Views 6426 views
  • Users 0 members are here
Related Discussions
Home » Discussions » Reports

I am using a!queryProcessAnalytics to fetch data from a portal report with a group context.

mattj

#queryProcessAnalytics I am using a!queryProcessAnalytics to fetch data from a portal report with a group context. I am wondering if there is a way to add a user context (and a process model context) to the report after it has already been created? In the last query filter below marked "HERE", I am returning all users in a selected group using fn!distictusers, and trying to filter the data within the a!queryProcessAnalytics based on the users in that group. It is not working because it throws an error "All “data” arrays must not contain more items than the specified “batchSize”, but “batchSize” was 25 and the largest column data array had 26 items". It works in some lower environments but not all, which makes me think its a data issue. Does anyone have any ideas on how to fix this?

a!queryProcessAnalytics(
report: local!portalReportId,
contextGroups: local!selectedDepartment,
query: a!query(
...

OriginalPostID-193213

  Discussion posts and replies are publicly visible

Parents
  • 0
    @mattj Where is the actual query to analytics located? I guess it might have resided in load() as of now. It might be better moving the query inside with() or inside the 'saveInto' of a component with which you actually interact with to refresh the interface.

    Also please do bear in mind that the interface should be refreshed by some or the other means to see the new data, that is for instance, a button click or an interaction with a component should trigger the query again and thereby refresh the datasubset.

    Also if you are able to upload the code snippet, the practitioners here, would be able to guide you by suggesting the changes.
Reply
  • 0
    @mattj Where is the actual query to analytics located? I guess it might have resided in load() as of now. It might be better moving the query inside with() or inside the 'saveInto' of a component with which you actually interact with to refresh the interface.

    Also please do bear in mind that the interface should be refreshed by some or the other means to see the new data, that is for instance, a button click or an interaction with a component should trigger the query again and thereby refresh the datasubset.

    Also if you are able to upload the code snippet, the practitioners here, would be able to guide you by suggesting the changes.
Children
No Data
© 2024 Appian. All rights reserved.
We want to hear from you! Submit a review on Gartner or G2.