attribures displayed with DISPLAY

robleer

I need a certain list but it is not possible to write a query whichs shows records I want.

I managed to get the right list with a process like this:

Find PlayerInTeam WHERE PlayerInTeam.PlayerLink=LoggedInPerson

Find TeamInSeason WHERE TeamInSeason.PlayersLink = PlayerInTeam

DISPLAY TrainingSession WHERE TrainingSession.TeamLink=TeamInSeason

But, the DISPLAY action displayes all attributes of the trainingsession BO, and I only want to see two attributes.

How can I show only the two attributes I want ???

aware_support

This should really be in Tips and Tricks. Lots of questions about this. The answer is still the same:

Create a query using the query editor and specify the attributes you want to display there. Then refer to that query in the DISPLAY action.

robleer

Yes, I know, but in some cases I cannot use a query to get the results that I want. Mostly this is caused because of the 'allow multiple flag' is on and I have to find another way to get my results.

In my case I use a few Find actions to put some BO's in the right context first. After that I show the results by displaying the BO (with unfortunately all the attributes).

So, to my opinion, this should not be in Tips and Tricks, but Aware should solve this by making it possible to present the attributes that I want.

Something like a 'Presentation' for DISPLAY actions as:

DISPLAY Employees USING MyPreferredAttributes

If there are so many questions about this, it is better to solve it instead of pointing us to use a query because that is not always possible.

And in my case the main problem is caused because of the impossibility of making References to Appointment object (with recurrency). I have to force myself in all kind of work arounds to get the right results.

technopak

Hi,

Here's how I'd do it -

Create a TrainingSession reference attribute in SystemSettings or RegularUser and create a query to DISPLAY the required fields for that TrainingSession. Your process should look something like this -

Find PlayerInTeam WHERE PlayerInTeam.PlayerLink=LoggedInPerson

Find TeamInSeason WHERE TeamInSeason.PlayersLink = PlayerInTeam

SystemSettings.TeamInSeason=TeamInSeason

DISPLAY TrainingSession (a query which finds TrainingSession for the TeamInSeason)

The query will then give you dynamic results based on the end FIND of your process stored into SystemSettings - and you will have control over the fields displayed.

This is just an extension to the suggestion from support.

Hope I've not misunderstood what you're trying to do.

Peter

aware_support

It doesn't matter whether you specify your query conditions directly in your rules or in the query editor. You can use dynamic values in the query editor as well. When you say:

DISPLAY 'Query name"

the query will use your current context whatever it is.

This is exactly the same as:

DISPLAY SomeObject WHERE ...

You can put the "WHERE" part into the query editor irrespective of what's inside this WHERE clause.

robleer

@Technopac

First I tried it with a non-persistent BO to store temporarily data, but that does not show data in a query.

Then I 've made a temporary BO to store the data temporarily and made a query to show my desired data. This gave me the right results, so I managed to work around it and I have my data now.

You're solution is also working I think (just a different approach), but I still think that it is a lot of work which can be done much more easy.

robleer

@Aware_support

You say: 'the query will use your current context whatever it is'

I've made a simple test (of course I know that getting the right results in the example can be done otherwise, but it is just to demonstrate the problem)

This is the process:

Find TrainingSession WHERE TrainingsSession.MonthName='Aug'
//This puts the TrainingSession in context, so only the trainingssessions in August are in context

DISPLAY QryTrainingSessions
//This is a query with the following rule inside: FIND TrainingSession WHERE TrainingSession.ID=TrainingSession.ID (btw: I also tried FIND ALL TrainingSession)

The DISPLAY QryTrainingSession displays ALL OF THE MONTHS so it does not use the context from the first rule.

aware_support

There is absolutely no reason to use BOTH FIND and DISPLAY, since DISPLAY is just another version of FIND. Your query should be:

Find TrainingSession WHERE TrainingsSession.MonthName='Aug'

Call this query "My Query". Then in your process use this:
DISPLAY 'My Query'

robleer

No, please read the whole treat first before answering.

I my case it is not possible to write a WHERE clause which shows the right records I need. This problem is caused because of the 'allow multiple' flag is on and this is not allowed in a WHERE.
To solve this, I've setup a process which has 3 rules. These rules will set three BO's in the right context. The 3th is containing the right records which I finally need.
After setting everything in the right context, I want to show the records of the 3th BO. I can only use DIPLAY for that, but that shows all the attributes, and I want only a few.<<<<Now here is my problem

So, the example in my last posting is only to explain (in an very simplified way) the problem to you.

Aware Support says that a query uses the context of an earlier rule. So I made very simplified example which shows that to my opinion it is NOT using the context as Aware says.

technopak

Hi,

As far as I know, the only way to display specific attributes of instances of a BO found is by creating a query in the Aware Configuration Tool and using the DISPLAY facility of the query editor to configure the attributes you wish to display.

Using the DISPLAY command from within a process will not enable you to configure the attributes which you want to display.

For me, this is really only a minor inconvenience. Given the re-usability factor, I actually prefer to construct queries the Aware way 🙂

Peter

robleer

Hi Peter,

I do not agree with that. In most cases it will do, but you have to create a query for every situation. I my (large) project I get many, many queries this way. So it would be far more easy when you could set the attributes in the Object (some kind of query presentation).

In fact, when you should have something like DISPLAY ObjectA Using MyPreferredQryPresentation, you would have less queries and a better overview of your project.

And in my case it is sometime not possible to use a query. This is caused by the Appointment object which cannot store multiple references. Then I have to follow another rout to achieve my desired results.

technopak

Hi,

Must admit I'm getting a bit lost now - why don't you use a presentation to display the attributes that you wish to present, and base the presentation on your query ?

Some of my Aware apps have 50+ queries configured and generally perform very well.

I guess it's whatever suit each individual best.

Good luck with your development.

Peter

robleer

Yes, we're a little of topic now. I do not say it does not work, but it can be a little easier I think. Tnx for your help. Rob

aware_support

I my case it is not possible to write a WHERE clause which shows the >>right records I need. This problem is caused because of the 'allow >>multiple' flag is on and this is not allowed in a WHERE.

This flag should not be a problem for queries, which support IN statement, subqueries etc.

Going back to your original process. Instead of writing this:

Find PlayerInTeam WHERE PlayerInTeam.PlayerLink=LoggedInPerson
Find TeamInSeason WHERE TeamInSeason.PlayersLink = PlayerInTeam
DISPLAY TrainingSession WHERE TrainingSession.TeamLink=TeamInSeason

you should have written this:
First step:
Find PlayerInTeam WHERE PlayerInTeam.PlayerLink=LoggedInPerson
DISPLAY TeamInSeason WHERE TeamInSeason.PlayersLink = PlayerInTeam

Second step:
a) Create a query with the following text in the Rule Language tab:
FIND TeamInSeason WHERE TeamInSeason.PlayersLink = PlayerInTeam
b) Define displayed attributes
c) Rewrite the process to be:
Find PlayerInTeam WHERE PlayerInTeam.PlayerLink=LoggedInPerson
DISPLAY 'My query'

The process above and the process before are EQUIVALENT.

robleer

Yes you are right. I was struggling with it but my problem was a stupid typo in a rule before.

Changing a < into a > solved my problem. Sorry for this.