URGENT - Move independent views from DEV to PROD via xml???

[veena_kvkk88]

Hello all!!

We moved update sets from dev to prod. Something went wrong and 2 of the views of a particular custom table don't reflect the dev instance. They are working perfectly in the Dev and that's the only issue, so we thought of migrating them to Prod independently using xml export and import.

This is what I did:

I exported the two view records (from UI views table) as xml.

I went to the prod instance, opened the Views table and clicked 'Import xml' from the header menu. And chose these two xml files and uploaded.

But there's no change in the views in Prod. What am I doing wrong? Is this not how it's supposed to be done? Please help!

[veena_kvkk88]

abhi_r, ctomasi, pradeepksharma, michael.ritchie Any advice?

[Chuck Tomasi · Accepted solution]

There are many records that make up a view.

You also need to get the corresponding "section" table entries from sys_ui_section. These are represented as related lists on the View form. It's a bit like getting a group with no members. You've got the 'shell' of the view definition, but not the content.

The easiest way to find your section is by table name.

You may also want to get the appropriate entry from sys_ui_form (by table.)

[veena_kvkk88]

Thanks Chuck for the prompt reply! I actually thought of this, but I assumed if I export the xml, everything including related lists are going to be exported. Let me export all corresponding forms, form sections, lists and Related lists as well and wil bug you again if something doesn't work.

[Chuck Tomasi]

Sounds good. The ability to export with related lists disappeared about 2011 if I recall. Not sure why. It was a nice feature in many cases.