"AisDisableSearchSignalEvent undefined, maybe missing global qualifier" error
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
a month ago
Hello Community,
When the RITM is changed from active to inactive, there is a error on the form which goes "AisDisableSearchSignalEvent undefined, maybe missing global qualifier".
I found which BR and Script Include is doing this, they are in different scopes, not sure if that is the problem or something else...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 weeks ago
I have the same issue since I migrated my PDI to Zürich. Also found the issue at a customer's place running Yokohama on premise. It seems to me that the issue is linked to the move from Zing to AI Search. Interestingly, if you create a complete custom table and add a "Active" true/false field, the same error will apply...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
I have been seeing this error too. It seems like it started for us after upgrading from Yokohama Patch 5 to Yokohama Patch 7 HF 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Same here. After some digging, it turns out that when you use Zing instead of AIS, Servienow is creating BRs in your app do disable the call to the AIS events. If your app is scoped, then you get this error message because as such, you are not allow to call a Global function from a scoped application without implementing Cross-scope privileges. It helped for me 🙂
