New SOW Tab contents not being saved
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-18-2025 08:13 AM
Hello!
I've added a new tab to the "SOW - Record tabs right" page collection. It loads and renders perfectly. I've got it against a view that shows just the fields I want and it shows all the data that is available from the record.
Unfortunately when you click Save on the SOW, any updates made on that tab aren't saved back to the database. Other (OOTB) tabs are saved fine. If you make updates in the Core UI they are updated OK.
I've obviously not wired something up correctly on the new page, but I've no idea what. If anyone has any pointers I'd really appreciate it!
Many thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-18-2025 08:17 AM - edited 08-18-2025 08:18 AM
what are the fields? just for info work notes/comments (journal fields) are not updated through list in workspace.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-18-2025 08:48 AM - edited 08-18-2025 08:48 AM
The fields are a mix of custom and OOTB MI fields. Not work notes or comments..
Cheers.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Did you find any solution for this? If so, I would appreciate it if you could share any information or insights you have. Any details or updates would be very helpful.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
We did solve this as it happens. There were a couple things that had to occur:
1. Our new page inherited the controllers from the parent page collection. The new form on the page came with its own controller (I'd added the bundled Form View component). We swapped the bundled component controller for the one that was inherited.
2. We still have to have the items on the other page, so we left them there but had a client script to hide the section.
I think that was it. All seems to work now.