How to capture a database view in an update set?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-19-2018 02:13 AM
Hi everyone,
I created 3 database views on my DEV instance and it works fine.
But I get many errors while installing this update set on another instance :
"Could not find a table field referenced in this update" as if all columns in the database views were missing...
What did I forget?
Thanks for your help
Valérie

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-19-2018 02:19 AM
Hi Valerie,
I doubt it works well with update set but I did some research & what I got is link How to migrate database view in an update set which may be helpful.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-19-2018 02:29 AM
Hi Valerie,
Database views has some issue with update sets. Because this database views create there own tables to views final results..
Try importing and exporting part and pieces of database views, like conditions, tables, joins, etc.
Thank you,
Ashutosh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-01-2018 07:43 AM
Here is how it work on Istanbul:
When you define a new database view, you'll see all these customer updates in the update set:
#1. database view (db_view) and database view table (db_view_table) => of course, these are the core
#2. list layout and form layout
#3. Field labels
But unfortunately, #2 and #3 are not able to install correctly on the target instance... (probably because database views are not yet created, or the creation is not complete)
So I had to put #2 and #3 manually in a separate update set, and it worked fine.
Also don't forget to define ACL on the database view because it is not sufficient if the user has access to the tables that are joined.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-01-2018 08:03 AM
Hi Valerie,
Exactly!
There can be a difference in order of committing the customer updates.
Error occurred due to mismatch of references captured.
Thanks alot,
Ashutosh