Surveys Not Triggering

Nia McCash
Mega Sage
Mega Sage

I created a Survey (with Trigger Conditions) on a dev instance and moved it over to our production instance via update set.   The Surveys are NOT triggering on the production instance and I'm not sure why.   Has anyone run into this before?  

I verified that the survey configurations were migrated to the production instance correctly.   All Trigger Conditions and Business Rules are there but not executing.

1 ACCEPTED SOLUTION

Nia McCash
Mega Sage
Mega Sage

I finally received an answer from HI support and it seems the root cause of my issue is that I was missing an asmt_assessable_record.   HI support's response was:



I noticed that there's a missing asmt_assessable_record for the survey on your developer instance. Without this record, linking to the survey, the trigger will never fire because it doesn't realize there's records to assess.



I noticed that the missing was NOT captured in an update set (not sys_update_xml entry created).


View solution in original post

16 REPLIES 16

sudharsanv36
Kilo Guru

Hello Nia,



We have faced the similar issue while migrating surveys. I would recommend to create a new survey with trigger condition.



Once everything is completed, From the application navigator go to "View Surveys --> Your Survey --> Right Click --> Export Assessment".



Once the xml file is downloaded, go to your target instance --> retrieved update sets --> upload update sets using xml --> select the downloaded xml --> click on upload.


Migrating surveys this way helped alot. Please note Export Assessment is a UI action which can only accessed from View Surveys list view.


Nia McCash
Mega Sage
Mega Sage

I finally received an answer from HI support and it seems the root cause of my issue is that I was missing an asmt_assessable_record.   HI support's response was:



I noticed that there's a missing asmt_assessable_record for the survey on your developer instance. Without this record, linking to the survey, the trigger will never fire because it doesn't realize there's records to assess.



I noticed that the missing was NOT captured in an update set (not sys_update_xml entry created).


Thanks a lot !