Can an Objects attribute (Shortcut) point to a query?

MartinPluss

Hi, I'm brand new to Aware IM and I'm fighting my way through some of the concepts. I need some help with the best way to achieve the following:

I have an Object called Person, and Another called Address. A person can have multiple Address objects associated (work home parents etc), and each Address Record has an 'IsMain' attribute (Yes/No).

From a Presentation Perspective I want to be able to Display a Form Tab with the Person info on it (Firstname, Lastname, DOB etc). I also want to display the 'main' address data here, so this is the address object that has 'IsMain' set to Yes. The Address info on this tab will be non editiable.

All of the Addresses associcated with the Person are available on the Addresses Tab where they can edit and add new ones.

I thought I might be able to add a shortcut attribute and point it to a Query, but that doesn't seem to be possible.

How Can I do this?

Thanks in Advance, Martin.

tford

Martin,

I think I can help you get 1/2 way there. I'm not sure how you would make the Main address on Person tab not editable.

Try this:
1- A Person form with 2 form sections:
a- Person
b- Addresses

On the Person form section, you will include a reference attribute -- I'll assume Person.Addresses. On this reference attribute you will filter for IsMain = 'Yes'

The Addresses from section would also include the Person.Addresses reference attribute, but here it would not be filtered.

Hope this helps.

Tom

aware_support

Further to Tom's reply - to make the main address not editable you can define the following rule on the Address object:

If Address.IsMain = 'Yes' Then
PROTECT Address FROM ALL EXCEPT 'Administrator'

tford

Neat idea.

To edit the Main address then, all a user would have to do is uncheck "Is Main".

Tom

tazzmaxx

I like this concept. Is there a way to ensure that a Person does not have 2 records that are main?

I am assuming that a rule would have to exist that checks if an Address record already has a main "yes" record.

I just can't seem to get how I would associate that rule to an individual Person.

johnaohman

Similarly, how would you ensure that at least one of the addresses was designated as the main address, so that everyone had a main address?

tford

Is there a way to ensure that a Person does not have 2 records that are main?

Probably the simplest way is control how Main is assigned. One way would be to have a process linked to each Address instance/line in the Addresses tab. You would want this process to be the only way that Main is set to yes. Let's call it the "Set to Main" link.

That process would:
1- Find all Address instances for that Person that are Yes (there should only be one).
1a - Set Main to 'No'.

2- For the address that was clicked, turn it to 'Yes'

Tom

aware_support

like this concept. Is there a way to ensure that a Person does not have 2 records that are main?

Add a rule to the address object:
If Address IS NEW AND EXISTS Address WHERE (Address.IsMain = 'Yes' AND Address.ID <> This.Address.ID) Then
REPORT ERROR 'Only one main address can exist'

This means that if a new address is being added and there is already an address different from the one being added that is main, then it''s an error.

Similarly, how would you ensure that at least one of the addresses was designated as the main address, so that everyone had a main address?

Similarly:
If Address IS NEW AND Address.IsMain='No' AND NOT (EXISTS Address WHERE (Address.IsMain = 'Yes' AND Address.ID <> This.Address.ID)) Then
REPORT ERROR 'At least one main address must exist'

MartinPluss

Thanks Tom, and AS I'm getting really close now - just need a little more help getting it to look right.

The Person Form now has the 'Main address' displayed on the person tab as well as an addresses tab to list all the addresses. As suggested the main address displayed is actually the same object reference as the one in use to display all the addresses in the addresses tab, but with a filter applied to limit it to the first address marked as main.

Trouble is the Main address is displayed on the person tab as a table and I want to view it as a form (so that it looks like the other fields displayed from the person object).
I hoped to be able to pop into the presentation section of this attribute on the person form and choose a form template but this option (Use Form) is greyed out.

How can I display the referenced attribute on the person tab as fields in a form layout rather than as data in a table?
Photo below, Top Current, middle shows the greyed out edit option, bottom shows the sort of thing I'm aiming for.

Thanks for your help.

-Thanks also for answering my next question about ensuring there is at least one, but only one Main Address 😃

aware_support

To enable form editing of the attribute the reference itself must not be "multiple allowed" and the "Allow inline editing" checkbox must be ticked on the Presentation dialog.

tford

Martin,

That's not possible without additional attribute fields. Because Addresses are a Multiple Allowed reference, AwareIM can not use a shortcut.

If you really need to show the address more like a form, you will need to add some Calculated attributes to Person like Person.Address. When a Main address is selected, you can populate those Calculated attributes. Then you will be able to put them on the Person form any where you'd like.

Tom

MartinPluss

Once again, thanks Tom and AS.

I now have this working by using additional calculated attributes for the Person object - which is excellent.

Naturally this leads me on to other questions about formatting but I'll start new topics for those.

Thank you kindly,

Martin

tazzmaxx

Hi Support,

I attempted the rule that you included and it does work for the first record. When I attempt to add a second record (even if main is not checked) I received the error 'Only one main address can exist'

Am I doing something wrong with the rule?

I used the rule listed below

If Addresses IS NEW AND EXISTS Addresses WHERE (Addresses.Main='Yes' AND Addresses.ID<>ThisAddresses.ID) Then
REPORT ERROR 'Only one main Address can exist'

Thanks

tford

Tazz,

You might want to try:

If Addresses IS NEW AND EXISTS Addresses WHERE (Addresses.Main='Yes' AND Address.Person=ThisAddress.Person AND Addresses.ID<>ThisAddresses.ID) Then
REPORT ERROR 'Only one main Address can exist'

The previous rule was looking at ALL addresses & not just addresses for the same person

Tom

aware_support

Tom is right as usual 😃 I was too sloppy when specifying the rule. Apologies.

tazzmaxx

Hi Tom and AS thanks for the assistance. I tried your rule Tom and I am still continuing to have errors. I will try creating a new BSV and try the rule again. It still gives me the same error. :o(

tazzmaxx

I tried a brand new bsv and encountered the same problem. It now allows me to add a single MAIN record to each Person but not multiple address records.

tford

Tazz,

I'm 100% why the other rule does not work, but try this:

If Address IS NEW AND EXISTS Address WHERE (Address.Main='Yes' AND Address.Person=ThisAddress.Person AND Address.ID<>ThisAddress.ID) AND Address.Main='Yes' Then
REPORT ERROR 'Only one main Address can exist'

Tom

tazzmaxx

THAT'S IT!!!!!!!!!!!!

Way to go Tom!!! When you are ready to start the Aware IM for Dummies book please let me know. That was very helpful!

Thanks again