►Q◄ Is this a bug or how do check for Ref.

BenHayat

Hi Guys;

I've run into a situation which I'm not sure it's bug or another way for checking if a Reference exists.
I need to show a section on a form or a Tab on VP, if a Customer.Contact exists.
I have a Customer Object and Contact Object as One-To-One relationship.
I need to show a section in form if Customer has a Contact reference and not show if there is not Contact Reference.

We have a sections in configurator "Condition when invisible" and I write
LoggedInCustomer.Contact IS UNDEFINED
In this case, whether a Customer Has or Does NOT have any Contact the section or tab doesn't show.

If I write LoggedInCustomer.Contact IS DEFINED
It shows the tab or section, regardless of the Contact reference exists or not.

Is this a bug or is there another way to check for reference?

Thanks!

BenHayat

I have even tried:

COUNT Contact Where (Contact IN LoggedInCustomeer)=0

And it behaves as IS UNDEFINED, meaning it cannot tell if Customer has a Ref. or Not.
Do you think it's a bug?

kklosson

It's not clear why you are using LoggedInCustomer. It seems you would want Customer.Contact EXISTS to check THIS customer. If your intent is that the customer is updating his/her own record, then I would say the same thing. But the bigger issue is whether you can do that lookup on a form condition. I'm not certain, but you may be limited to conditions of the primary object only. Just to try an alternative, may I suggest:

IF COUNT Reference WHERE (Reference.Customer=LoggedInCustomer)>0

But I still think you are limited to the primary object. If so, consider flagging the primary object by using a rule such as I provided above as a means to set its value.

BenHayat

kklosson wrote
It's not clear why you are using LoggedInCustomer. It seems you would want Customer.Contact EXISTS to check THIS customer. If your intent is that the customer is updating his/her own record, then I would say the same thing. But the bigger issue is whether you can do that lookup on a form condition. I'm not certain, but you may be limited to conditions of the primary object only. Just to try an alternative, may I suggest:

IF COUNT Reference WHERE (Reference.Customer=LoggedInCustomer)>0

But I still think you are limited to the primary object. If so, consider flagging the primary object by using a rule such as I provided above as a means to set its value.

I'm sorry my example turned out to be misleading. I actually started this checking in VP, to see if LoggedInCustomer has a Contact or not.
In many rules, I've used the exact condition "LoggedInCustomer.Contact IS ENDEFIENED" and provides the correct result, however when used to Show a Tab on VP or a Tab in a Form, the Condition does not return the True or False value.

So, if you were going to write a Rule in VP to show a Tab if Customer has an Contact Reference, how would you write it? I used IS UNDEFINED and COUNT and neither worked.
Thanks!

kklosson

The rule in the Customer object would be:

IF EXISTS Contact Where(Contact.Customer)=This Customer THEN
Customer.HasReference='Yes'

Then use Custome.HasReference in your rule to display/hide a form section.

BenHayat

This is where I'm trying to apply the rule. If Customer has Contact, then show the tab. But no matter what I write Customer's WITH or WITHOUT Contact behave the same.

BenHayat

kklosson wrote
The rule in the Customer object would be:

IF EXISTS Contact Where(Contact.Customer)=This Customer THEN
Customer.HasReference='Yes'

Then use Custome.HasReference in your rule to display/hide a form section.

Why do I have to create an extra attribute? Why can't I use same condition that you used in Rule, to Display/Hide Section or Tabs on VP? That's strange.
I mean appreciate your suggestion and I may have to do it this way. but don't you think this might be a bug?

kklosson

I know there are places in AwareIM when you cannot use a reference attribute. I believe this may be one.

BenHayat

kklosson wrote
I know there are places in AwareIM when you cannot use a reference attribute. I believe this may be one.

Ok, Thank you Sir!
We're on the same page that checking for Reference in this case doesn't work.