BPM action Add Related Record not recognizing existing related module

Hi Jeff ,

I wasn't able to reproduce the issue you are encountering. Can you provide a screenshot of the relationship you created in Studio?

Chris

Demo Relationships

Here's what I have in the designer

I appreciate the reply.  It's probably something stupid that I'm forgetting, but I've wasted half a day trying to figure it out and figured maybe someone could point me in a direction.

FWIW..   If I set the action type to Change Fields, I can see the related opportunity module.  So, I can change field values over this relationship, but for some reason I can't add related record.

Thanks, Jeff . Everything looks appropriate in your configuration. The only significant difference in my test is that I am using Sugar 25.2, so it's possible a bug was fixed since 14.0.

I recommend filing a case with Sugar Support so they can either confirm whether a bug was fixed or if there is something else that may need adjusted to expose the relationship for the Add Related Record action. If there was a bug fixed, they may be able to provide you with a hotfix on your current Sugar version as opposed to requiring an upgrade.

Chris

That was my next step.  Thanks for the advice.  Appreciate you.  Have a great holiday.  

Just to close the loop in this, Sugar support pointed out in the documentation where it says that the relationship can't be 1:1 or 1:M.   While I don't understand why the 1:1 relationship won't work, deleting that one and creating a M:M relationship let me select the Add Related Record Action type.  Maybe it needs the M:M relationship so that it had a separate relationship table.  Anyway, perhaps this will help someone else sometime.

Hi Jeff ,

I went back and tested this scenario from scratch with a new custom module with no module relationships initially defined.

I created a 1:1 relationship between the custom module and Opportunities, and I reproduced the issue you experienced in the process definition where I could not select the 'Add Related Record' action. I then created a many:many relationship to another module (Cases). After that relationship was created, I could select the 'Add Related Record' action and within the action, I could select either relationship I created:

It looks like the bug may be that all relationships are exposed in this selection once the module has either a m:m or m:1 relationship. 

I configured the action for the Opportunities relationship and it created the record as expected. As far as I can tell, the relationship creation works fine once it is exposed. 

Chris