Refresh Settings - on a Query vs. Content Panel in VP

Jaymer

In Magic, we called this a Synchronized one-to-many, where you have a list of customers, for example, and as you click on a customer, you see another list of Invoices (or Contacts, or Orders, etc.) get updated real time as you click or up/down thru a list.

Not sure what Aware calls it.
Basic premise is this:

You have a VP with multiple Content Panels.
Panel Alpha shows output of a Query "All Custs"
... the default action by clicking on a Cust saves the CustID to LIRU

Panel Beta shows Invoices
... it Refreshes when the SaveCustID process runs... or is it when LIRU is changed. Can never remember which or why - use both.
... Does the Panel need to refresh, or does the Query need to refresh? You have to try it until you get the results you want.
... Supposed to also "Select First Line" so the Default action runs "by itself", this saving Invoice ID and triggering the next refresh on Invoice Lines. (Hasn't been working in 2477 - doesn't select the line - maybe fixed already in later bld)

Panel Charlie shows Invoice Lines
... it refreshed ALSO when EITHER SaveInvoiceID or LIRU is changed - be safe, use both

OK, so thats what I go through.
And there's an awful lot of saving to LIRU - which is convenient but also writes back to the db constantly - which COULD BE an issue per Ben's Un-answered Q here and an issue I discovered

PointsWell

3 Queries

Q1 - All Customers - Default Action DISPLAY Query 2
Q2 - Invoices WHERE Invoices.obCustomer=Customer Default Action DISPLAY Query 3
Q3 - InvoiceLines WHERE InvoiceLines.obInvoice=Invoice

VP Panels Default Outputs
Customer -> Invoice
Invoice -> InvoiceLine

Only Panel Customer has an operation defined Run Query Customer, but you could forces Panels Invoice and InvoiceLine to show a dummy query that you know will not show anything so that the VP is fully constructed (ie no white space that gets overwritten) before doing its refreshes

No refreshes on VP or query and no LIRU references.

See attached sample.

You only need to use the LIRU to store things if there is some condition that might result in the query not showing, if the contact was not a customer for example you might want to show Purchase Orders, but you could probably manage that with a process that triggered different Queries based on the Contact type.

ChainedQueries.bsv.zip

39.54kB

ChainedQueries.bsv.zip

39.54kB

PointsWell

Jaymer wrote
So, the point and Question is this:
1) How would you know, other than Trial and Error, if you want a Query to refresh, or the Content Panel (which contains a query) to Refresh?
2) Does anyone else get odd refresh result when refreshing after a Process Runs - and then you don't get the result expected, and then you change it to the BO - and then the refresh works?

To your question of Panel or Query, I am not sure it make much difference (though if you do both you are potentially creating double overhead nb not based in any technical understanding)

As far as, where do I use the refresh, semantically if I am changing just the query I would refresh just the query. The caveat being does that query get reused anywhere. If I am just updating the information presented I would tend to update the query.

Where I tend to use Auto refresh for Panels is if I want to change the information being presented (as opposed to updating), for example I have a series of child BOs related to a Contact record eg.

Contact has Addresses,
Contact has Clients

I have various Contact types: Customer, Employees.

If I look at Joe Customer's Address record and then change the Contact that I am looking at to Jane Employee then I don't want to store (or be able to show) Address records for my Employees, so I use a process on the Auto Refresh for the Panel to instead show a Query of Clients (Jane Employee has clients), likewise when I change back to Joe Customer the Auto Refresh changes back to Addresses.

That being said I could just implement this auto refresh on the query and attach the process there, but then if I ever want to reuse that query I'd potentially generate unwanted results.

As to your second question, no, do you have a simplified example of what is happening?

Jaymer

SEAN
Thanks for re-focusing me.
I've done it so long "the Bruce method" where the Default action had to save the ID.
(Bruce frequently is saving an ID on each click in a Query so he can do something with that ID)
In this simple case, wow, was this Easy.