Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Enhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.

Reply
LSLjsb1982
New Member

Flag values that are not allowed

Is there a way to highlight the PN Removed and PN Installed red if it doesn't fall within the correct PN based on the Pack Style? An A319 can only have ACM 1814A0000-XX and PL 1816B0000-XX installed on that config. If the wrong PN is installed can I highlight that number through a function? Top left would be the correct ACM and PL based on AC and Pack, bottom is my table of removals and installs some being incorrect. I need to flag the incorrect ones with a color or icon.

 

LSLjsb1982_0-1750177299731.png

 

2 ACCEPTED SOLUTIONS
v-ssriganesh
Community Support
Community Support

Hello @LSLjsb1982,
Thank you for reaching out to the Microsoft Fabric Forum Community.

I have reproduced your issue in Power BI Desktop based on your requirement where specific PN Removed and PN Installed values should be highlighted in red if they do not match the allowed part numbers based on Aircraft Type and Pack Style.

I implemented this using rule-based conditional formatting with a helper flag column (1 = valid (True), 0 = invalid (False)) and applied it to both columns successfully.

Achieved the expected output where incorrect values are flagged in red(false) matching your original requirement:

vssriganesh_0-1750224782589.png

 

For your reference and testing, I’ve attached a .pbix file that you can explore and customize as needed.


If this information is helpful, please “Accept as solution” and give a "kudos" to assist other community members in resolving similar issues more efficiently.
Thank you.

View solution in original post

Hello @LSLjsb1982,
Thank you for your follow-up and for sharing the complete data view.

To differentiate between each Work Order line and ensure uniqueness, even when Serial Numbers (SN Installed or SN Received) repeat across rows, you can use your LSL Work Order column as the primary unique key it appears to uniquely identify each transaction in your dataset.

If this helps, please mark it as “Accept as solution” and feel free to give a “Kudos” to help others in the community as well.
Thank you.

View solution in original post

7 REPLIES 7
v-ssriganesh
Community Support
Community Support

Hello @LSLjsb1982,
Just checking in have you been able to resolve this issue? If so, it would be greatly appreciated if you could mark the most helpful reply accordingly. This helps other community members quickly find relevant solutions.
Please don’t forget to “Accept as Solution” and Give “Kudos” if the response was helpful.
Thank you.

v-ssriganesh
Community Support
Community Support

Hi @LSLjsb1982,

May I ask if you have resolved this issue? If so, please mark it as the solution. This will be helpful for other community members who have similar problems to solve it faster.

Thank you.

v-ssriganesh
Community Support
Community Support

Hello @LSLjsb1982,
Thank you for reaching out to the Microsoft Fabric Forum Community.

I have reproduced your issue in Power BI Desktop based on your requirement where specific PN Removed and PN Installed values should be highlighted in red if they do not match the allowed part numbers based on Aircraft Type and Pack Style.

I implemented this using rule-based conditional formatting with a helper flag column (1 = valid (True), 0 = invalid (False)) and applied it to both columns successfully.

Achieved the expected output where incorrect values are flagged in red(false) matching your original requirement:

vssriganesh_0-1750224782589.png

 

For your reference and testing, I’ve attached a .pbix file that you can explore and customize as needed.


If this information is helpful, please “Accept as solution” and give a "kudos" to assist other community members in resolving similar issues more efficiently.
Thank you.

IS there a way to keep my "LSL RD" current with the data? I need to diferentiate between each individual line or Work Order. I may have repeating SN's from the data. This is the full data set:

LSLjsb1982_0-1750682534086.png

 

Hello @LSLjsb1982,
Thank you for your follow-up and for sharing the complete data view.

To differentiate between each Work Order line and ensure uniqueness, even when Serial Numbers (SN Installed or SN Received) repeat across rows, you can use your LSL Work Order column as the primary unique key it appears to uniquely identify each transaction in your dataset.

If this helps, please mark it as “Accept as solution” and feel free to give a “Kudos” to help others in the community as well.
Thank you.

Hi @LSLjsb1982,
I hope the information provided has been useful. Please let me know if you need further clarification or would like to continue the discussion.
If your question has been answered, please “Accept as Solution” and Give “Kudos” so others with similar issues can easily find the resolution.
Thank you.

speedramps
Super User
Super User

Try this ...

 

dont have have any relationship between your repairs table and config table

 

This measure will return TRUE is the part is valid or FALSE if it is invalid.

You can use it in conditional formating to change the colour

 

SELECTEDVALUE will get the cursor cell value 

which I call my part and my config

 

FILTER then creaste a temp table of any rows on the config table that match

 

ISEMPTY checks if the temp table is empty

 

Is installed part valid =
VAR mypart = SELECTEDVALUE(repairs[PN install])
VAR myconfig = SELECTEDVALUE(repairs[Aircraft family]
VAR matchingcongfigs =
FILTER(config, 
config[acttype) = myconfig  &&
config[PLinstalled)= mypart)
RETURN
ISEMPTY(matchingcongfig)

 

 

Please click thumbs up and accept solution

Helpful resources

Announcements
August Power BI Update Carousel

Power BI Monthly Update - August 2025

Check out the August 2025 Power BI update to learn about new features.

August 2025 community update carousel

Fabric Community Update - August 2025

Find out what's new and trending in the Fabric community.