Reference attribute or rule?

vinsnash

There is a BO "Member" with an attribute "Type" which is a single character and an attribute "Amount" which is a number.

There is a BO "FeeTable" with an attribute "Type" single character and an attribute "Amount" which is number.

When creating a new "Member" I'd like "Member.Amount" to equal the "FeeTable.Amount" where "FeeTable.Type" = "Member.Type".

Is this done with a reference or a rule? The attribute "Member.Type" is calculated based on input of other attributes.

I've tried a rule:

If Exists FeeTable Where (FeeTable.Type = Member.Type)
Then Member.Amount = FeeTable.Amount

That reports a "possibly wrong object identifier FeeTable is used in path FeeTable.Amount" message on "Save".

Thanks for any help.

technopak

All that I can see wrong with your process is that you're not telling the system which Member to set the Amount for. Or in Aware-speak, at the time of your 'Then Member.Amount = FeeTable.Amount', there's no Member in context.

If it's for each new Member, you can use something like

IF Member IS NEW AND EXISTS FeeTable Where (FeeTable.Type = Member.Type)
Then Member.Amount = FeeTable.Amount.

With this structure, the system 'knows' it's the new Member (in context) that you are setting the Amount for.

A word of caution however - how many FeeTable.Type can match Member.Type ?

If there could be more than one, the question of exactly which FeeTable's Amount attribute you wish to set arises. If there's only one possibility, the rules above will work just fine.

If there could be multiple FeeTable types which could match Member.Type, I think creating a reference attibute in Member to the FeeTable BO is the best way to set it up.

Hope this helps,

Peter

vinsnash

Thanks Peter but It still produces the same message on "Save" not when I set up the rule and click the "OK" button. I've picked all the rule telements from the drop down lists. The syntax is accepted and there is no error at that point. When I click "Save" the "Possibly wrong object identifier FeeTable in path FeeTable.Amount" appears.

I save anyway but the rule does not execute. There is only one FeeTable.Type per possible Member.Type. Member.Type is calculated correctly when creating a new Member. The rule is set for "dynamic recalculation on forms". The initial value "$0" in the Member form for Member.Amount does display correctly.

Vins Nash

tford

Don't know all the BO relationships, but you could try:

If Exists FeeTable Where (FeeTable.Type = Member.Type)
Then
FIND FeeTable Where (FeeTable.Type = Member.Type) Member.Amount = FeeTable.Amount

Like Peter said, FeeTable has to be put in context. The FIND action does that.

tford

If Exists FeeTable Where (FeeTable.Type = Member.Type)
Then
FIND FeeTable Where (FeeTable.Type = Member.Type)
Member.Amount = FeeTable.Amount

vinsnash

That all makes sense. Just like "Read Random" in an old procedural language 🙂

Thanks much!