- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-04-2017 03:09 AM
Hi SNC,
I am wondering why some Related Lists do not appear when we access the form through Service Portal's Form Widget. Additionally, why do sometimes the name of the Related List appear different from the original one on the back-end form?
For instance: accessing the Project form (pm_project table) on the back-end, we have a Related List called "Sub Projects", but accessing the same form through the Service Portal's Form Widget, that same Related List is presented as "Project". Another example is the Related List called "Project Budget" on the beck-end and "Project Fundings" on the Form Widget.
Any ideas on why this happens?
Thanks in advance,
Fábio Gonçalves
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-06-2017 04:14 AM
And the same for the Cost Plans and Cost Plan Breakdowns related lists.
So, if you want to show Resource Plans, Cost Plans and Cost Plan Breakdowns related lists on Service Portal's Form Widget simply replace the OOTB related lists present on the pm_project table with the following: Resource Plan -> Task, Cost Plan -> Task, Cost Plan Breakdown -> Task.
It will work as the OOTB related lists with the improvement of appear both on back-end form and Service Portal's Form Widget 😉
Thanks again for the help on this issue Bryan Tay.
Best Regards,
Fábio Gonçalves

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-04-2017 09:47 PM
hi Fábio,
Have u check the "View" for pm_project table back end form?
I tried on my instance, the default views show exactly the same for portal as well as the back end form.
Note: Related list can be added to different view.
hope this help.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-04-2017 09:50 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-05-2017 02:22 AM
Hi Bryan Tay,
Thanks for your answer but I double-checked the views and that does not seems to be the problem.
One pattern that I was able to identify was the fact that the Related Lists that contain the "filter conditions" of the type "Task/Parent/Demand = xxxxxx" are the ones that appear both on back-end and Service Portal Form (see Capture 1); and the Related Lists that contain a different type of "filter conditions", like "Assessment Category Results" only appear on the back-end (see Capture 2). Both captures were taken using the Demand (dmn_demand table) form as an example. If you could find the time to test this on your instance I would appreciate the help 🙂
Capture 1:
Capture 2:
Does that make any sense? Have your ever came across something like this?
If yes, how can I workaround this?
Thanks,
Fábio Gonçalves

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-05-2017 05:18 PM
hi Fábio,
After testing it, realized that the out of the box form widget only pickup related list that belongs to pm_project or related list with "filter conditions" of the type "Task/Parent/Demand = xxxxxx" (you are right).
Missing related list are those relationship that tag to "Task" table (where task -> planned_task -> pm-project).
tracing back to the form widget source, Server Script
data.f = $sp.getForm(data.table, data.sys_id, data.query, data.view);
and html
<span ng-repeat="rl in data.f._related_lists" ng-if="rl.visible">
where data.f._related_lists are from the $sp_getForm function aboved.
I think u can try:
1. Log a HI ticket to service now and see are there any alternate solution to the out of the box.
2. Create a customized 'Form' widget (clone) and customize the code to fetch the related list you want by adding missing related list e.g Cost Plan, Resource Plans, cost breakdown (those relationship extended from Task) etc after $sp.getForm function call.
3. Create additional pm_project relationship so link from E.g. resource_plan -> pm_project (instead of task).
Note: Method 3 require no code change on widget.
I hope this helps.