How to have Applicability on Query Buttons re-computed

BLOMASKY

I have a query that displays Purchase orders. When a user selects (edits) a row, I update an attribute in the LoggedInRegularUser (and I checked, this is being done right).

I have a button on a form with the Applicability rule set to:

LoggedInRegularUser.selectedPurchaseOrder <> UNDEFINED

I have the refresh logic set properly but the button is never displayed. How can I have this logic recomputed when a record is selected?

Thanks

Bruce

tford

I normally use this syntax:

LoggedInRegularUser.selectedPurchaseOrder IS DEFINED

Not sure if that contributes to your issue or not.

BLOMASKY

Tom, that was just my last attempt. I have tried IS, <> tried using a shortcut field instead of the actual attribute, but it never seems to recompute.

Bruce

BenHayat

BLOMASKY wrote
I have a query that displays Purchase orders. When a user selects (edits) a row, I update an attribute in the LoggedInRegularUser (and I checked, this is being done right).

I have a button on a form with the Applicability rule set to:

LoggedInRegularUser.selectedPurchaseOrder <> UNDEFINED

I have the refresh logic set properly but the button is never displayed. How can I have this logic recomputed when a record is selected?

Thanks

Bruce

Don't use "<>". Use "IS UNDEFINED" (without the double quotes of course 🙂 )

BenHayat

BenHayat wrote
BLOMASKY wrote
I have a query that displays Purchase orders. When a user selects (edits) a row, I update an attribute in the LoggedInRegularUser (and I checked, this is being done right).

I have a button on a form with the Applicability rule set to:

LoggedInRegularUser.selectedPurchaseOrder <> UNDEFINED

I have the refresh logic set properly but the button is never displayed. How can I have this logic recomputed when a record is selected?

Thanks

Bruce

Don't use "<>". Use "IS UNDEFINED" (without the double quotes of course 🙂 )

Sorry, I meant to say "IS DEFINED" as Tome had said.

tford

Do you have RegularUser BO in your query's auto refresh?

BLOMASKY

Thanks for the fast response Tom

I have both the process that assigns the selected PO to the Reg User AND the reg. user update both in the auto refresh. But if this works for you, then I guess I just have to play more (or talk sternly to the program)

tford

Place this type of condition in the applicability condition on the selection operation:

PurchaseOrder.ID<>LoggedInRegularUser.Selected_PurchaseOrder.ID

tford

AR.zip

22B

Below is a BSV to demonstrate. It used Customers instead of Purchase Orders.

To demonstrate, open the BSV in test mode and:
1) Click New Customer and add a few
2) You'll notice "Select" shows up beside each Customer in the Query
3) When you choose a Customer in the query by clicking "Select", you'll notice the Select button will no longer appear for that Customer.

AR.zip

22B