Related list issue with Problems and attached Incidents

Tom Alday · ‎02-18-2014

So we have a Problem that has a few Incidents have been manually attached to it from the related list on the Problem record

The way I believe it should work is that if I go into one of those Incidents (ex INC0025026) I should see this Problem in its Related list under "Problems", but I'm not seeing it

It does this the other way too, if I add a Problem to an Incident using the related list on the Incident record that Incident doesn't show up in the related list in the Problem record. Am I doing something wrong? It seems like they should be connected, but they don't seem to be...or I'm doing something wrong, which is possible.

geoffcox · ‎02-19-2014

m2m can be confusing at first, but it's a key concept.

You should already see a new related list available when personalizing related lists on the problem form as well. It should appear by the name you gave it above ("Incidents").

You won't see anything in the related list until you relate the incidents to the problems (thus populating your new m2m table). If you select Edit on the related list on the problem form, you can select the incidents to relate to the problems, or vice-versa on the incident form.

If you have some kind of meeting maker and want to call me to discuss sometime, we can schedule something.

Cheers,

Geoff.

View solution in original post

Tom Alday · ‎02-26-2014

I've never used the security rule debugger before but it looks like it gave me some good info:

It looks like it's failing because I don't have Create ACL's in place, am I reading that right?

eican · ‎02-26-2014

That sounds right.

Create them for table level (no ".*") and you should be good.

Easiest would be to take one of the existing ones, change the type to create and the use the form context menu with "insert and stay with roles"

Tom Alday · ‎02-26-2014

SUCCESS!

I also had to create a Delete ACL so they can remove incidents/problems from the list if needed.

I really appreciate all your help and patience, you're awesome eican, You too geoffcox !

geoffcox · ‎02-27-2014

Thanks!

Although, I'm a little concerned that you now have two m2m tables, apparently for the same thing?

If you already have a u_m2m_problems_incidents, you shouldn't also need a u_m2m_incidents_problems. That would be redundant.

Cheers,

Geoff.

geoffcox · ‎02-26-2014

I had him add the m2m table: he wanted to see multiple related incidents on the problem form, and multiple related problems on the incident form.

I have no idea why users can't save records to the m2m table.

Impersonate a user and try to open an individual record of the m2m table itself (rather than using the slushbucket editor). See if the user can insert a new record into the table. That's probably where the ACL is preventing the behavior you want.

Cheers,

Geoff.