Expand my Community achievements bar.

SOLVED

1 - N Link Configuration from Profile to Custom Resoulrce

Avatar

Level 2

Hi,

 

I need to create a 1 - N Link from Profile to a Custom Resource based on a attribute present in both the schemas.

I followed the documentation provided in the following section and successfully created my join  by selecting options - 

 

 

The following were observed after the join creation - 

  •  I was not able to open any of the profiles from the profile tab saying "ERROR - The resource you are trying to access is unreachable".
  • I viewed my custom resource table from client data and it was empty (even having records not linked to profile). Only those records were visible in which it had values in the attribute chosen for the link in both profile and custom resource.

Please advise or correct if this is acceptable or if any corrections needs to be done to correct both issues.

 

Thanks in advance !.

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Hi @acs-ratul,

 

I believe you have created link from Profile to Custom resource, if that's the case then remove the link and recreate the same link from custom resource to profile. This should fix the profile access issue.

 

Thanks, Sathees

Thanks, Sathees

View solution in original post

3 Replies

Avatar

Correct answer by
Community Advisor

Hi @acs-ratul,

 

I believe you have created link from Profile to Custom resource, if that's the case then remove the link and recreate the same link from custom resource to profile. This should fix the profile access issue.

 

Thanks, Sathees

Thanks, Sathees

Avatar

Level 2

Hi Sathees,
Thanks for the reply.

 

I have created the link in my custom resource and selected "Profile" as the target resource. I havn't done any changes in profile schema.

Does anything else needs to be done to successfully create a 1-N link from profile to custom resource?

 

Thanks.

Avatar

Community Advisor
No, you don't have to. if you have created link from custom resource to profile schema and publish the changes should work.
Thanks, Sathees