- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-06-2022 03:28 PM
We have a global application using 2 tables and we would like to create this as a Scoped Application.
1. Is there a way to move existing application as a scoped application , without recreating everything ?
2. Can we move the data to the scoped Application and have same sysids of the records , SLAs , Attachments.
3. Is there a way to move data from Table A to Table B , within same Instance? (Without exporting data from table A and using Data Sources)
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-06-2022 03:57 PM
Hi,
- I would think the easiest method would be to recreate manually in your scoped application.
- If you move the data out of it's table IE task_sla or sys_attachment then the record is no longer an an attachment or a task_sla record, so I cannot see any value or benefit in doing this?
Perhaps you can clarify the requirement? - If Table A and Table B are related IE extended from task or cmdb_ci then you can update the records sys_class_name to change its table. BUT data will be lost where tableA.field1 does not exist on tableB
You may also find other issues occurring for related data, IE if you change record from incident to sc_request any attachments will still be mapped to the incident table, task_sla records may no longer be valid, the record state mapping will be incorrect....the list of potentail issues is long.
So while the answer is yes you can, I would not recommend that you consider this as a solution unless you have fully assessed and remediated the impact.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-06-2022 03:57 PM
Hi,
- I would think the easiest method would be to recreate manually in your scoped application.
- If you move the data out of it's table IE task_sla or sys_attachment then the record is no longer an an attachment or a task_sla record, so I cannot see any value or benefit in doing this?
Perhaps you can clarify the requirement? - If Table A and Table B are related IE extended from task or cmdb_ci then you can update the records sys_class_name to change its table. BUT data will be lost where tableA.field1 does not exist on tableB
You may also find other issues occurring for related data, IE if you change record from incident to sc_request any attachments will still be mapped to the incident table, task_sla records may no longer be valid, the record state mapping will be incorrect....the list of potentail issues is long.
So while the answer is yes you can, I would not recommend that you consider this as a solution unless you have fully assessed and remediated the impact.