Column rules and conditions with if/then scenarios

[Iulia_Stoi]

Is there a way to create if/then scenarios to set a condition for a column?

I have a project clean up report where I need project owners to emphasize form fields that they need to complete as part of their project planning. I would like to create a condition where IF a selection is made in one field, and not an a subfield, THEN the report will highlight the missing entry for the subfield. 

For example: our project entry form requires the selection of the market and business line of that market. In this case if the project owner selected a market but did not complete the business line for that market, the report should highlight that field in a color to emphasize this is a missing entry for their project. 

How can I achieve this using reporting column conditional rules?

[Sven-iX]

Hi @Iulia_Stoi

I don't fully understand: You have a PROJ form with 2 custom fields, market and business line. 
You write you want a highlight in case 

• market is selected
• business line is not selected

Does that mean you do NOT want a highlight when 

• market is not selected and business line is not selected
• only business line is selected

?

If so - you'd need a 3rd field (calculated) that does this check, so you can use that calculated field's value in the styling condition. 

The styling logic is pretty limited: it looks at a single field and compares its value with a either a given value or with another field - but you cannot do logic like "if field A is not blank and field B is blank"

[Iulia_Stoi]

Thank you for your response. To clarify the business line is a subfield that only becomes visible in the project form, when a certain market is selected. In this case I only need a highlight when the market is selected and the subsequent business line is NOT selected.

[kautuk_sahni]

@Iulia_Stoi just checking in! Were you able to get this resolved? If one of the replies above helped—whether it completely solved the issue or simply pointed you in the right direction—marking it as accepted can make it much easier for others with the same question to find a solution. And if you found a different way to fix it, sharing your approach would be a great contribution to the community. Your follow-up not only helps close the loop but also ensures others benefit from your experience. Thanks so much for being part of the conversation!