Reports - Recent Threads

RE: Quick Filter Limit

Shubham Aware — Mon, 23 Mar 2026 08:52:53 GMT

AFAIK it's hard limit of 10.
https://docs.appian.com/suite/help/26.2/manage-reports-and-dashboards.html#add-a-report-or-process-to-a-dashboard

Quick Filter Limit

joseangelr342997 — Fri, 20 Mar 2026 18:18:13 GMT

I need to add more than 10 quick filters to the report, but the option is disabled. Is there a way to add more filters?

Issue in record sync

kaviarasan S K — Wed, 04 Mar 2026 09:29:54 GMT

Hi Team,

I have a main record type called Case, which is based on the Case table as its source.

For reporting purposes, I created another record type called Closure Report, and this record type is also using the same Case table as its source.

In our process model, we are using the Write to Record smart service to write data into the Case table.

The Case record is syncing automatically without any issues. However, the Closure Report record is not syncing automatically. When I check the data preview of the Closure Report record type, I can see the latest updated values in the table.

If I perform a manual sync for the Closure Report record type, then it works and the latest data is reflected properly.

Previously, we created similar report-type records using the same approach, and they were working fine. This issue is occurring only for records created from last month onward.

Could you please help me understand why the Closure Report record is not syncing automatically even though the data is getting updated in the source table, and why it works only after manual sync?

RE: Issue in record sync

kaviarasan S K — Thu, 05 Mar 2026 09:32:52 GMT

No older reports also synced record types only

RE: Issue in record sync

Shubham Aware — Thu, 05 Mar 2026 09:08:13 GMT

Older reports likely used unsynced record types.

RE: Issue in record sync

kaviarasan S K — Thu, 05 Mar 2026 08:12:20 GMT

Previously, we created similar report-type records using the same approach, and they were working fine. This issue is occurring only for records created from last month onward.

RE: Issue in record sync

kaviarasan S K — Thu, 05 Mar 2026 08:12:15 GMT

Previously, we created similar report-type records using the same approach, and they were working fine. This issue is occurring only for records created from last month onward.

RE: Issue in record sync

Harsha Sharma — Thu, 05 Mar 2026 06:18:54 GMT

The write records node has input and record type Case in the configuration and not the Closure Report record type. That is why just Case record type is synced. You should add a sync record smart service after the write Case records node to have the Closure Report Record synced as well within the same process. That will resolve the issue you are facing as well as prevent need of manual sync.

RE: Issue in record sync

Shubham Aware — Thu, 05 Mar 2026 05:05:51 GMT

The Write to Record smart service only triggers auto-sync for the record type it writes to (Case). Since Closure Report is a separate record type (even on the same table), it doesn't receive the sync signal.
You can add a Sync Records smart service in your process model targeting the Closure Report record type right after the Case write.

RE: Issue in record sync

kaviarasan S K — Wed, 04 Mar 2026 15:47:57 GMT

Could you please share a possible solution to this issue?

RE: Issue in record sync

Stefan Helzle — Wed, 04 Mar 2026 13:50:14 GMT

I copied your question into the AI Chat in the documentation and got some good hints.

RE: How to Hide AI Copilot in Process HQ Reports?

Shubham Aware — Wed, 25 Feb 2026 17:37:24 GMT

[quote userid="296434" url="~/discussions/f/reports/40228/how-to-hide-ai-copilot-in-process-hq-reports"]should we raise a support ticket with Appian to get it removed?[/quote]

Yes! Admin can't control this setting.

How to Hide AI Copilot in Process HQ Reports?

toshij7 — Wed, 25 Feb 2026 12:24:01 GMT

We’ve created several reports for business users in Process HQ and made them available on our site. By default, the AI Copilot feature is appearing in those reports, but the client does not want this feature enabled.

Is there an option in the Admin Console to disable or hide it, or should we raise a support ticket with Appian to get it removed?

RE: How to Hide AI Copilot in Process HQ Reports?

Stefan Helzle — Wed, 25 Feb 2026 12:49:54 GMT

AFAIK this cannot be configured. Open a support case to discuss options.

RE: Grouping Not working properly on date time field in Bar Chart when the interval is DATE_TEXT

Mike Schmitt — Fri, 13 Feb 2026 14:44:02 GMT

Interesting conundrum honestly - I assume you're originally referring to query-time aggregation, no? So the grouping puts the boundary at GMT/UST (which i'd basically expect) but it doesn't end up looking correct or intuitive for the end user (or even the designer really) since the data at the boundaries between groups ends up being intuitively wrong. I'm not sure what feasible solution there might be for this, given the basic nature of the aggregation grouping functionality available to us.

Stefan might have a good idea that I haven't thought of, but if it were critical to me I'd raise it with Appian to see if they happen to have any supported solution.

The "traditional" (CDT backed) approach MIGHT be to create a view with "alternate" date/time columns that carry "converted" values of the date/times causing grouping into the correct groups after time zone adjustment. I suppose it's possible you could create custom columns in your record type that do a similar preemptive conversion, but I haven't tried such a thing.

Grouping Not working properly on date time field in Bar Chart when the interval is DATE_TEXT

mohammedwarishb7086 — Fri, 13 Feb 2026 08:09:36 GMT

Hi, the grouping is not working as expected in bar chart when i am using a!recorddata. I am working on PST time. So, any record which is created after 4 PM PST is grouped as the next day. Let's say I have 2 records, one at Feb 12, 3 PM PST and another at Feb 12, 5 PM PST. When I apply a filter for Feb 12, the bar chart actually shows me data of two dates, Feb 12 and Feb 13. The record which is created at 5PM PST is grouped to Feb 13. It is most likely due to the time difference(8 hours) between gmt and pst, as I can clearly observe any record after 4 PM PST is grouped to the next day. Is this behaviour expected? Please suggest me a solution.

RE: Grouping Not working properly on date time field in Bar Chart when the interval is DATE_TEXT

mohammedwarishb7086 — Fri, 13 Feb 2026 14:31:44 GMT

Hi, Thanks for the solution. It worked. Btw, I still feel Appian should not have done the conversion during the grouping. Even if it did, I think it should have done -8 hours right and keeping it on the same day? rather than doing a +8 and changing it to next day.

And coming back to the conversation, when I query the data, it converts to PST(my local time) and gives as expected, meaning when I add a record at 5 PM PST, it saves in gmt in db and returns as 5 PM PST. The issue happens only when it groups with a datetime field. I also tried with the createdOn datetime field with the hour interval and it grouped to the same day, meaning I can see the records after 4 PM for the same day. It was only when I used the interval DATE_TEXT, it started acting funny and grouping the records after 4 PM to the next day.

++ adding the GOATS Stefan Helzle Mike Schmitt for their perspectives

RE: Grouping Not working properly on date time field in Bar Chart when the interval is DATE_TEXT

Shubham Aware — Fri, 13 Feb 2026 10:44:32 GMT

Yes, expected: Appian converts datetimes from UTC to your local timezone.
Add custom record field pst_date: datevalue(local(created_datetime, "America/Los_Angeles")); use that Date field for primaryGrouping with interval: DATE_TEXT. Groups by PST calendar day.

https://docs.appian.com/suite/help/26.1/Chart_Configuration_Using_Records.html#apply-time-intervals

RE: How to Retrieve Appian Memory Units in Task/Process Reports for Querying with Process Analytics?

Marco Galvão — Fri, 16 Jan 2026 12:47:04 GMT

I could find information on process size from Health Check Report logs on System Logs/health-check/hc-process-model-sizing.csv

I am ordering the last column (Total Process Size) and its giving me the same problematic processes that shows on Process Model Metrics page, but not the same AMU count. But at least is something.

How to Retrieve Appian Memory Units in Task/Process Reports for Querying with Process Analytics?

pierpaolo.longobardi — Fri, 31 May 2024 12:56:56 GMT

Hi Appian Community,

I am currently working on optimizing the performance of our processes in Appian and would like to monitor the memory usage of individual processes. Specifically, I am interested in obtaining the Appian Memory Units (AMUs) consumed by each process and including this information in our task reports. This way, we can query these reports using Process Analytics.

Does anyone have experience or insights on how to capture and report the memory usage of processes in Appian? Any guidance on integrating this data into task reports and making it available for analytics would be greatly appreciated.

Can we export charts or images in excel

salmak1788 — Fri, 09 Jan 2026 14:12:45 GMT

Can we export charts or images in excel?

RE: Can we export charts or images in excel

Shubham Aware — Mon, 12 Jan 2026 05:14:12 GMT

Appian's out‑of‑the‑box Excel exports only export data.
Recommend you would try, Create an Excel template with charts that reference a data range and then populate that data via a plugin or template‑based export, Excel will render the charts when opened, but the charts themselves are authored in Excel, not exported from Appian’s chart components.

RE: Can we export charts or images in excel

Stefan Helzle — Sat, 10 Jan 2026 10:00:49 GMT

No, not with Appian’s built‑in Excel export features.

RE: End User Reporting Tool related question

aijaz4app — Wed, 03 Dec 2025 15:32:28 GMT

Thank you for the reply.

End User Reporting Tool related question

aijaz4app — Tue, 02 Dec 2025 21:03:19 GMT

Hello,

I have a question related to End-User Reporting tool.

In the Appian Community it is mentioned that this tool was last updated on May 2023.

Since then this listing has been archived.

I would like to know if there are going to be any new versions or upgrades related to this tool in the future.

Can we use this utility for future application building.

Thank you.