Calculated fields. Best practices for Application Studio

[jdrucker (Jose Alfredo Drucker Guerrero)]

Hello! I’m creating a new Layer for my Order Entry screen.
I’m trying to hide a shape based on a BAQ result, but it’s getting complicated.
The BAQ is based on the Customer.

Here is what I’ve already tried:

Using a Data Directive to set a UD field, then hiding the shapes using Rules. It works, but it relies on the user saving the order before any UI update happens.

Using the txtCustomerCustID2 OnBlur event. There, I save the BAQ result into a View, but the View is populated after the Rules run, so the UI doesn’t update correctly until I tab out of the txtCustomerCustID2 field a second time.

At this point, I’m very frustrated and feel like I’m just creating workarounds instead of a proper solution.

[jbooker (Josh Booker)]

@jdrucker

I save the BAQ result into a View, but the View is populated after the Rules run, so the UI doesn’t update correctly until I tab out of the txtCustomerCustID2 field a second time

My understanding is the rules are in effect ‘always running’ so something else is going on here.

I believe the row rule would be on the dataview having the field to which your shape is bound (orderhead, for example) and the rule condition should be looking at the BAQ dataview.

Can you share a screenshot of your rule?