Transporting VC Models and related pages and iviews across portals

[Former Member]

Hi,

Hope you all are doing good.

We have a particular requirement, which i hope you will be able to give some inputs.

We have models for which we have .gml files. In addition we have the models deployed in Portal as iviews under Visual Composer folder.

Our requirements is to transport the models in VC and iviews in Portal to a new installation.

When we take the content dump from portal for the models and import into new installation it works fine.

But when we want to make changes in VC model (.gml) files and redeploy the VC application in Portal, it does not over write the existing iview for same VC application in Portal.

The ID's of the deployed iviews for same VC appls are getting changed and hence not updating the same one.

Any idea what we are missing ?

Appreciate your help

Regards

Sumit

[Former Member]

HI Sumit,

Whenever you import .gml file in new Portal firstly one model name should be created then only we can import the existing model from Dev box at that time the package name differ in such case.

this may be a precaution from SAP

I also tried the same thing what you did but getting the same kind of deployment what you are getting.

Hope your doubt are clear

Swapnil

[Former Member]

Hi..

I thought it is but obvious...and no need to mention that....

cheers

[Former Member]

All,

Just to note to follow up on SAP's responses to my OSS note on this subject.

SAP stated that you can not over-write the original objects. Visual Composer is designed to create a new instance of the iview/.par files.

This is true for both 7.0 and 7.1 per their response.

Regards,

Mark

[Former Member]

Sumit,

We are having the same issue.

Have you figured out a solution?

I have an opened OSS message on the topic and will update you on what I find out.

Best Regards,

Mark

[Former Member]

yes we have figured out the problem...

just when importing the models in VC it ask for a check box

"to import with all related components" (not sure abt the exact statement)but just check that box while importing the model and then redeploy it in portal...ur problem willbe solved...changes will be overwritten......

rewards point if helpful