web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Finance | Project Operations, Human Resources, ... / "Column is not filtera...
Finance | Project Operations, Human Resources, ...
Suggested Answer

"Column is not filterable" on ALL columns on form grid using view as datasouce

(1) ShareShare
ReportReport
Posted on by PM-31101632-0 7
On a custom form clicking on any column header in the header grid to filter produces the error "Column is not
   filterable" on every column — including standard bound fields like JournalNum (String), JournalType (Enum), CreatedDate (DateTime), etc.

The line grid on the same form does not have this issue - all columns are filterable.

Observations:
-The view works in table browser, all columns are filterable there. 
- The line grid with a seemingly identical setup works fine

What causes "Column is not filterable" on ALL columns of a cross-company view when used as the form's primary datasource in a TaskParentChild pattern? Is there a known
  framework limitation or a specific property/configuration I'm missing?
Categories:
Dynamics 365 Finance
I have the same question (0)
  • Diego Mancassola Profile Picture
    Diego Mancassola 652 on at
    Hello, see this error in the past but not remember the solution i found, honest.
     
    By the way i suggest you (what i do)
    * Check the relationship of form data source, may have a not correct join's of tables
    * Check if the data source property are set correctly in the grid and controls
    * Delete usage data
    * Delete personalization of form view
  • Suggested answer
    PM-31101632-0 Profile Picture
    PM-31101632-0 7 on at
    Thank you Diego. Update: 

     Problem: When opening the form from the workspace tiles, users get
      "Column is not filterable" because the tile menu items use queries that have AllowAdd set to No on the root datasource, which prevents adding any filter columns.
     
    Fix: Set AllowAdd to Yes on the root datasource of both queries.
  • Diego Mancassola Profile Picture
    Diego Mancassola 652 on at
    Hello, great, pleasure to hear your fixed
    Didn't remember that condition of Query, that typically is default Yes

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Congratulations to our 2025 Community Spotlights

Thanks to all of our 2025 Community Spotlight stars!

Congratulations to the February Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 555 Super User 2026 Season 1

#2
Giorgio Bonacorsi Profile Picture

Giorgio Bonacorsi 364

#3
Diego Mancassola Profile Picture

Diego Mancassola 259

Last 30 days Overall leaderboard

Featured topics

End-of-life Announcement for Microsoft Dynamics GP

Product updates

Dynamics 365 release plans