Jump to content
Salesforce and other SMB Solutions are coming soon. ×

Using a lookup field as relational match field


cfirenzi

Recommended Posts

Hi,

 

I actually have 2 questions regarding related files.

 

First of all, from my lack of success, I assume that you can't use, as a match field, a calculation field that already includes a relational value--

 

e.g. match the text field "key number" in table 1 with the following calculation field in table 2:

 

if (number field 1 =""; relationship name:number field 2; number field 1)

 

Secondly, I tried to get around the problem by substituting a regular lookup field (i.e. non relational) so that the new match field is as follows:

 

if (number field 1 =""; conventional lookup number; number field 1)

 

This field calculates correctly, meaning that if the number field 1 is blank, it will display the correct lookup value. And if the number field 1 is not blank, it displays the value from number field 1.

 

Oddly enough, this works as a match field for the relation when the calculation returns the value for number field 1, but the portal is blank when the calculation field returns the value from the conventional lookup number.

 

Why is the lookup value a less suitable match field than the value in number field 1?

 

I'd greatly (!) appreciate any ideas.

 

Thanks,

 

CF

Link to comment
Share on other sites

This thread is quite old. Please start a new thread rather than reviving this one.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.



×
×
  • Create New...

Important Information

Terms of Use