Budget migration from classic to new experience (Investment Budget)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Wednesday
Hi All,
We are exploring the budget migration to new experience view which is investment budget. In project_funding table there are many fields exists but in investment budget(sn_invst_pln_invst_budget) table contains less fields compared to project funding, we would like to know if we will loose any data once we migrate the record from table to new table.
Appreciate if anyone can provide some information on this, Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Wednesday
I may have an old version (5.1.1) of the store app installed, but the script include InstDataMigrationUtil has a placeholder "to do" to allow for custom columns. At present, custom columns won't be migrated
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thursday
Hi Kieran,
Thanks for your reply, do you have any idea how the OOB field mappings are configured between legacy table and investment budget table while doing the migration.
We are trying to understand for example 20 fields in legacy table but 10 fields in investment budget table, while doing migration any field values are not mapped to new table which may lead to data loss.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thursday
They're within the various script includes, I'm unaware of a mapping document/table showing what is migrated.
Having a quick look, it doesn't look like any data is migrated directly from the project_funding record. Instead from associated data. So your legacy fields won't be migrated if they sit on the project_funding table