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

Announcements

Welcome to the Power Platform Communities
News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Apps / Error "Expression Sect...
Power Apps
Unanswered

Error "Expression SectorID eq null is not supported"

(1) ShareShare
ReportReport
Posted on by Community Power Pla... Microsoft Employee

Hello!

 

On my PowerApps application, I have a dropdown that has its allowed values based on the selected value of another dropdown, using the filter function below: 

 

Filter([@MasterData_Subcategory]; SectorID = DataCardValue14.Selected.CategoryID)

 

Rodrigo_N_1-1656693643688.png

 

 

However, the following error shows when I run the app: "Expression SectorID eq null is not supported"

 

I don't understand why this error is showing up since there are no null values in any of the tables (I've attached both in this post) and every value has a match, ensuring that there are no comparisons that would return null values. Could you help me with this? Thanks!

 

 

 

tables.xlsx
Categories:
Building Power Apps
I have the same question (0)
  • WarrenBelz Profile Picture
    WarrenBelz 155,315 Most Valuable Professional on at

    Hi @Anonymous ,

    This post may assist - one of the (many) issues with using Excel as a data source when things get a bit complex.

     

    Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

    Visit my blog Practical Power Apps

  • MickHtoo Profile Picture
    MickHtoo 2 on at
    This isn't a fix so much as a way around it. I was having the same issue with Power Apps not liking a blank dropdown box while the data was being uploaded into the App from SharePoint:
    The error had no effect on the App itself and worked fine (but not having a blank dropdown was not aesthetically pleasing).
     
    However, by changing the following to Blank()
    it stops the 'error eq null' happening until my data is loaded. 
     
    Not my brilliant idea, found it on YouTube here: Power Apps OnError to capture, suppress, and report all errors
     
    Hope that helps (and the Power Apps crew doesn't remove that option).

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

News and Announcements

Welcome to the Power Platform Communities

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Users!

Kudos to our 2025 Community Spotlight Honorees

Congratulations to our 2025 community superstars!

Congratulations to the April Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Apps

#1
Vish WR Profile Picture

Vish WR 899

#2
Valantis Profile Picture

Valantis 571

#3
11manish Profile Picture

11manish 499

Last 30 days Overall leaderboard

Featured topics

Auto-Populate field Power Pages
Gallery Tabs - Show or Hide Tabs based on Field Value
How to patch multiple records at once
Enable Copilot for end users in model-driven apps
Question for everyone : How are you using Create Text GPT in AI Builder?
Community content - sample components, blogs etc. - Link to this page (http://aka.ms/PCFdemos)
Welcome to the Power Apps forum!

Product updates

Microsoft Power Platform Community release plans