Format Rule Expensive? Working on an app her...

(Greg Huston) #1

Format Rule Expensive?

Working on an app here. I have a table with the following columns… 1. Material 2. Alloy 3. Pricing

I have a form with dependant drop downs from 1 & 2, and a format rule that checks if that particular alloy has pricing, and if yes, highlights in green. Here’s my code…

ISNOTBLANK(ANY(SELECT(MaterialList[Pricing],[Alloy]=[_THISROW].[Alloy])))

It basically checks if the Alloy you have selected already has pricing. This is a quoting app, so before trying to calculate pricing, it is basically alerting the user if it does, or does not have pricing data.

This is triggering an alert…

“The condition of format rule ‘New Format Rule’ may be expensive and slow the user experience of your app”

Is there a better way to do this?

Thanks!

(Aleksi Alkio) #2

Is your “Alloy” field a ref field?

(Greg Huston) #3

Hi,

I’ve done it both ways… I set it as a REF field and I’ve also used the “Valid if” constraint since this is essentially a double-dependant drop down. Select material, then select alloy.

Is there a way to do this that I can make it work without it being too slow?

Thanks!

(Aleksi Alkio) #4

You could add an additional Show type field just after the Alloy field telling the situation if it has price already. You could do that because you only need that information when filling the form.