Remote table
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-14-2025 08:24 AM
OOTB - remote table - v_st_sc_category (App use), the parent field is refering to sc_category. There is no script written on the v_st_sc_category table. Also, all the categories from sc_category table is not populated OOTB in v_st_sc_category table. I want to know from where the data is populating in that table. Is there any relation defined somewhere?
Also sn_me_st_topic (App use) table, the data get wiped out after deactivating one of the topics(topic) table.
I guess the only data availbale in sn_me_st_topic table is from the topic which I deactivated and, hence the sn_me_st_topic table don't contain the data any more. Again, why this remote table don't contain all the data which is refering to table that is present in database.
Is it possible to recover it?Is there any relation defined somewhere?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-14-2025 10:12 AM
Part 1: v_st_sc_category Table (Remote Table)
What it is:
v_st_sc_category is a view or remote table used by App Engine Studio or Studio Templates to access sc_category data.
It is not a standard table with its own data, but references or filters from existing tables like sc_category.
Why isn't all data showing?
It is filtered either by:
- User context
- App context
- Workspace or App Engine visibility rules
The parent field referencing sc_category does not pull everything unless there is a defined query or filter.
No visible script on v_st_sc_category? That is because the filtering is handled behind the scenes, potentially through:
- View definitions
- Module-specific GlideAjax calls
- Workspace metadata rules
Where is the relation defined?
Most likely via a GlideAjax call, portal script, or App Engine metadata rule that dynamically fetches visible categories for the app or experience.
Check:
- Studio App configuration
- UX rules in App Engine Studio
- Possibly the catalog item category mapping, if used in an App Engine flow
Part 2: sn_me_st_topic Table
What it is:
sn_me_st_topic is App Engine Studio metadata that helps define topics in a Studio Template app.
It is populated based on the topics you have activated, usually from the topic table or a related configuration table.
Why did data disappear?
You mentioned deactivating a topic record.
If that topic was the only one populating sn_me_st_topic, then the Studio logic clears it to stay in sync.
The data in sn_me_st_topic is often derived, not persistent — it acts like a materialized view, and deactivation removes its source.
Can it be recovered?
If you are lucky:
- Check audit logs for the sn_me_st_topic table to see if any record deletions were logged.
- Use the sys_audit or sys_journal_field tables.
But most likely:
- If the topic was deactivated and it was the only data source, the app cleared the related sn_me_st_topic entries by design.
- Re-activating the topic may bring the data back.
- If not, and it was not backed up, recovery may not be possible unless you have:
- An instance backup (for example, cloned or daily backup)
- Access to a dev or test environment with a copy of the data
Table: v_st_sc_category
Behavior: Remote or View
Why Data Is Missing: Data is filtered for app context
Where to Look: App Engine config, metadata rules
Table: sn_me_st_topic
Behavior: Remote or config view
Why Data Is Missing: Topic was deactivated and the source was removed
Where to Look: Reactivate topic or restore from backup
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-18-2025 04:08 AM
I can't re-activate the topic because it's no longer in use. The remote table should show other topics which are available in database. I checked mobile app config, there is nothing that is helpful.