Survey Analysis
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-31-2026 03:48 AM - edited 07-31-2026 03:49 AM
I didnt understand the requirement for the survey analysis .Could you please help,
Survey analysis is a form section but they are asking related list table view ,didnt understand the requirement properly
a) Survey Analysis tab is to be completely reworked to clearly display all analysis findings in a related list table view (separate line per root cause identified). Old structure and fields are to be removed.
b) Call Back Analysis tab is to be deleted.
c) Assessment Instance Questions tab is to be added, showing answers to all survey questions at a glance.
So that we can streamline the analysis done on the surveys submitted by end users and prepare the ground for an AI-driven survey analysis.
Survey Analysis tab - related list table view should contain the following columns:
Drop-downs are dynamically populated based on the defined structure : e.g. Dissatisfied -> Communication throughout the process -
| Call quality / soft skills / professionalism issue |
| Preferred language not supported |
| Incident communication rules not followed / lack of proactive updates |
| Contact attempt or callback ineffective |
| End user had to repeat information |
| Dissatisfaction with standard communication process — no operational fault |
| Project / change communication impact |
| Other — communication |
Recommended Actions depend on the selected Root Causes, and the Analysts should be given the possibility to manually add additional Recommended Actions. Use Cases & Description
are to be added as supporting information for each of the Root Causes.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Wednesday
The requirement is simpler than it sounds. They want you to stop storing the analysis as fixed fields on the Survey Analysis form. Instead, each root cause becomes its own row in a list under the tab, so one survey can have several root causes, each on its own line.
To do that, you need a child table that holds one root cause per record and points back to the Survey Analysis record (your form is on u_survey_analysis, as the URL shows). The documentation says a related list depends on a reference field between two tables. So a reference field on the child table pointing to Survey Analysis automatically gives you a related list on the Survey Analysis form.
- Create a new table, for example Survey Analysis Root Cause, with a reference field to the Survey Analysis table.
- Add the columns from the requirement as fields on this table, including RootCause#, SUR#, AINST#, INC# and Survey Analyst.
- Go to the Survey Analysis form, open the form context menu and select Configure > Related Lists.
- Move the new related list from Available to Selected and save.
- Turn on the user preference Organize form sections and related lists into tabs in classic forms, so the list shows as a tab.
- Remove the old Survey Analysis section fields and the Call Back Analysis tab through Configure > Form Layout.
- Keep Assessment Instance Questions as a tab. It looks like the out-of-box related list on the assessment instance, but please confirm the exact table name in your instance.
The columns that say automatically populated can be filled by a business rule on the child table’s insert. It would copy SUR#, AINST#, INC# and the overall rating from the Survey Analysis record. Overall Satisfaction Status is then Dissatisfied for ratings 1 to 3 and Satisfied for 4 and 5.
For the dependent drop-downs, use choice fields with a dependent field on the dictionary entry.
| Main Reasons for Rating | Overall Satisfaction Status |
| Root Causes for Rating | Main Reasons for Rating |
| Recommended Actions | Root Causes for Rating |
Because analysts must be able to add extra actions manually, keep Recommended Actions as a field that accepts free text in addition to the choices. A simple way is a separate free-text field next to the drop-down.
For the mandatory rule, make the required fields mandatory only when the Survey Analysis state changes to Closed Complete. A business rule on the parent that checks all child root cause rows before closing is the safest way, since a UI policy only sees the current form. Build everything in a sub-production instance and capture it in an update set before moving it to production.
If you can share your release and whether you use Workspace or the classic UI, we can sharpen the steps.
Hope you found it helpful.
Sources: