- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi All,
We haven't used the Idea module for quite some time and are now planning to start using it again. However, we've noticed a few issues:
The portal is still displaying the old Idea State choices instead of the updated values.
The Idea State field is read-only, so we're unable to update it.
Existing ideas from the older implementation are not appearing in the Idea Portal.
While reviewing the data model, we noticed both the idea and im_idea_core tables. Could you clarify the difference between these two tables? Our historical data is currently stored in the idea table.
We also noticed the im_m2m_idea_category table. What is its purpose?
Additionally, what is the im_module table used for?
Finally, is there a migration process required to move data from the old idea table to the newer tables, or is there another recommended approach?
Thanks,
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago - last edited 3 weeks ago
Hi @pramodkumar ,
- Check dictionary, UI Policy, Client scripts or data policies on state field.
- im_idea_core table - This is the base idea table which needs to be extend to create new idea table based on different BU, Department or initiatives.
- idea table - OOB idea table extending base im_idea_core table. OOB this table stores all the created ideas.
- im_m2m_idea_category table - M2M table used to store idea and category relationship. As one idea can belong to multiple table. Idea table does not have any category field.
- im_module - configure your existing or custom idea modules. This table contains the configuration of all the idea modules. It's like a separate idea page for the ideas related to a particular table or condition. Default module is idea.
- For Migration refer - https://www.servicenow.com/docs/r/it-business-management/innovation-management/migrate-legacy-to-new...
ServiceNow Docs:
Thanks
Anand
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @pramodkumar
Refer :
Idea Record Migration to New Idea Portal
Regards
Tanushree Maiti
ServiceNow Technical Architect
LinkedIn: https://www.linkedin.com/in/tanushreemaiti
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago - last edited 3 weeks ago
Hi @pramodkumar ,
- Check dictionary, UI Policy, Client scripts or data policies on state field.
- im_idea_core table - This is the base idea table which needs to be extend to create new idea table based on different BU, Department or initiatives.
- idea table - OOB idea table extending base im_idea_core table. OOB this table stores all the created ideas.
- im_m2m_idea_category table - M2M table used to store idea and category relationship. As one idea can belong to multiple table. Idea table does not have any category field.
- im_module - configure your existing or custom idea modules. This table contains the configuration of all the idea modules. It's like a separate idea page for the ideas related to a particular table or condition. Default module is idea.
- For Migration refer - https://www.servicenow.com/docs/r/it-business-management/innovation-management/migrate-legacy-to-new...
ServiceNow Docs:
Thanks
Anand
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
Thanks @Anand__99
If we want to roll out OOB for a specific department, do we need to use idea table or create new table extending im_idea_core?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
Hi @pramodkumar ,
This depends on your architecture. If you want to restrict these idea to a specific department and add some specific configuration to it you can create a new table specific for that idea. However, if this will be utilized by only one department and you don't have any plans to use it for other department/users then go with OOB table.
I would suggest create a new table for this. But as it will be a custom table so also check for available tables under license.
Thanks
Anand