Question

Import wizard doesn't overwrite existing zip file

When I try to import an existing .zip file, the import wizard gives me a warning saying that when I press "Next", the existing .zip will be overwritten.

Nevertheless, the existing .zip remains and I can't import the modifications made in the lower environment.

Correct Answer
September 17, 2019 - 4:35am

Out of curiosity, are you seeing the behavior being described here? https://community1.pega.com/community/pega-support/question/r-p-file-extraction-not-updated-when-specified-file-name-reused

If yes, its better to create an SR so that product support team will look into it.

Comments

Keep up to date on this post and subscribe to comments

September 17, 2019 - 3:09am

Hello, 

Maybe you do not have all authorization on this folder. Can you try to remove it manually and check?

Pega
September 17, 2019 - 3:59am

Hi,

Are you trying to import a RAP of your lower environment(s)?

What is the error/indicator that import has failed?

Thanks

September 17, 2019 - 4:03am

Yes. I try to import the RAP from DEV environment in our TST environment. The Creation Date and Instance count mentioned on the right on the second screen of the Import wizard tell me the old .zip is still used instead of the new one.

Pega
September 17, 2019 - 4:18am
Response to Jorre

While creating the RAP of your dev, did you perform a distribution or an export? 

If export was used, not sure if it is accounting the existing application data into account and hence you are seeing a discrepancy? 

September 17, 2019 - 4:27am

I started with creating a new instance of Product. On pressing the Create product file, I get a new version of the .zip, and another number of records exported. This is the number of rules I expect to see when importing it on the other side.

Pega
September 17, 2019 - 4:35am
Response to Jorre

Out of curiosity, are you seeing the behavior being described here? https://community1.pega.com/community/pega-support/question/r-p-file-extraction-not-updated-when-specified-file-name-reused

If yes, its better to create an SR so that product support team will look into it.

September 17, 2019 - 5:00am

It seems the same problem. When I do the export and use a new name, I end up with a smaller (correct 83 rules) file, where as if I reuse the same name, the file created is markably bigger (117 rules, as some rules were excluded after the first export). Trying to import this file (even with the name of the .zip modified to the old name so it should be overwritten in the TST environment), it actually mentions the right number of rules.

Thnx for the support!