- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-15-2017 05:27 AM
Hi,
I have added under the related fields, in the Change form the Catalog Tasks section, and in the SCTASK form the Change Requests section, then carried out the following:
1. Created a new Request — navigated to the SCTASK -
2. Clicked on the Change Requests Tab and selected the NEW Button —
3. This allowed me to raise a Change via the normal work-flow —
4. Which is then Displayed and Linked into the SCTASK -
5. When I then go to the Change and the Catalog Task section it does NOT show the SCTASK ref for the Service Request
I am guessing this has something to do with the fact that when you select edit, where you would normally see the SCTASK ticket numbers, you just see false all the way down for the first 100 SCTASK tickets, It does however show the SCTASK number at the bottom. but as it only shows the first 100 tickets, I can not locate or search for my SCTASK that should be linked to it.
How do I address this issue and get it to show the correct SCTASK ticket numbers, so it can be searched for, and also so it shows for step 5 above?
Many thanks
Clive
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-15-2017 06:34 AM
Hi Clive,
It is important to differentiate which Parent field is used in which case. When you add related list "Catalog Task > Parent" to the Change Request form, it means you want to see all catalog tasks that have in their Parent field reference to Change Request. However in your case you created Change Request from Catalog Task which means Catalog Task is parent of Change Request, not the opposite. That means in Change Request's Parent field, there is Catalog Task stored, not the other way around. This is why you see Change Request in Catalog Task form (where you added related list "Change Requests > Parent").
To demonstrate it little bit, I did this screenshot where I defined Catalog Task as parent of Change Request. You can see it in Parent field, however still the catalog task is not listed in the related list as this shows "child" catalog tasks = catalog tasks that have change request as parent in their Parent field.
Once you add Parent field on the form, you should see your catalog task that was used to create Change Request. That means the relationship here is 1:M - change request can have only one parent, but multiple child records.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-15-2017 05:42 AM
Hi Clive,
Notice the condition in each Related List - there is always "Parent = <number>". That means the related list records are related to the shown record via Parent field. If you want to see the related SCTask in Change Request, add Parent field to the form. As it is related through Parent reference field, one change request can be linked to just one catalog task. If you want to have M:N relationship, you need the M2M table or use Task relationships table.
Best regards,
Dominik
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-15-2017 05:44 AM
Also be aware that once you link a change request to another SCTask, the previous value is overwritten as Parent field can contain only one referenced SC Task for a change request.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-15-2017 05:54 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-15-2017 06:34 AM
Hi Clive,
It is important to differentiate which Parent field is used in which case. When you add related list "Catalog Task > Parent" to the Change Request form, it means you want to see all catalog tasks that have in their Parent field reference to Change Request. However in your case you created Change Request from Catalog Task which means Catalog Task is parent of Change Request, not the opposite. That means in Change Request's Parent field, there is Catalog Task stored, not the other way around. This is why you see Change Request in Catalog Task form (where you added related list "Change Requests > Parent").
To demonstrate it little bit, I did this screenshot where I defined Catalog Task as parent of Change Request. You can see it in Parent field, however still the catalog task is not listed in the related list as this shows "child" catalog tasks = catalog tasks that have change request as parent in their Parent field.
Once you add Parent field on the form, you should see your catalog task that was used to create Change Request. That means the relationship here is 1:M - change request can have only one parent, but multiple child records.