IBM Business Analytics

We had a corrupted deployed Framework Manager package - Sales. We redeployed Sales and it did not fix the issue. So we renamed Sales to Sales BAD and then redeployed Sales. In my experience when you rename a Package all of the report definitions are also changed to reference the new package name. So I expected all the report definitions to reference Sales BAD. But they still reference Sales. When they run the reports they still fail with the same error so I know that they are running against Sales BAD. Then edit the report, point to redeployed Sales and the report works. But the before (running against Sales Bad) and after repointing to Sales report definitions are identical. Can anyone explain this to me? i have a script that searches text in report definitions and i want to be able to keep track of Sales BAD and Sales reported to help the client keep track of the 500 reports that have to be repointed. Anyone have any experience with this? 

It has to do with browser cache. after restarting browser, and maybe deleting cache, it works fine.

We had a corrupted deployed Framework Manager package - Sales. We redeployed Sales and it did not fix the issue. So we renamed Sales to Sales BAD and then redeployed Sales. In my experience when you rename a Package all of the report definitions are also changed to reference the new package name. So I expected all the report definitions to reference Sales BAD. But they still reference Sales. When they run the reports they still fail with the same error so I know that they are running against Sales BAD. Then edit the report, point to redeployed Sales and the report works. But the before (running against Sales Bad) and after repointing to Sales report definitions are identical. Can anyone explain this to me? i have a script that searches text in report definitions and i want to be able to keep track of Sales BAD and Sales reported to help the client keep track of the 500 reports that have to be repointed. Anyone have any experience with this? 

@Thomas Bertl - what works fine? The renaming of the package will update the report definitions that reference the renamed package and i will see the new name in the report definition? 

It has to do with browser cache. after restarting browser, and maybe deleting cache, it works fine.

We had a corrupted deployed Framework Manager package - Sales. We redeployed Sales and it did not fix the issue. So we renamed Sales to Sales BAD and then redeployed Sales. In my experience when you rename a Package all of the report definitions are also changed to reference the new package name. So I expected all the report definitions to reference Sales BAD. But they still reference Sales. When they run the reports they still fail with the same error so I know that they are running against Sales BAD. Then edit the report, point to redeployed Sales and the report works. But the before (running against Sales Bad) and after repointing to Sales report definitions are identical. Can anyone explain this to me? i have a script that searches text in report definitions and i want to be able to keep track of Sales BAD and Sales reported to help the client keep track of the 500 reports that have to be repointed. Anyone have any experience with this? 

@brenda grossnickle - it does not affect the report definitions. In my opinion that works fine. only the properites of the reports are affected

@Thomas Bertl - what works fine? The renaming of the package will update the report definitions that reference the renamed package and i will see the new name in the report definition? 

It has to do with browser cache. after restarting browser, and maybe deleting cache, it works fine.

We had a corrupted deployed Framework Manager package - Sales. We redeployed Sales and it did not fix the issue. So we renamed Sales to Sales BAD and then redeployed Sales. In my experience when you rename a Package all of the report definitions are also changed to reference the new package name. So I expected all the report definitions to reference Sales BAD. But they still reference Sales. When they run the reports they still fail with the same error so I know that they are running against Sales BAD. Then edit the report, point to redeployed Sales and the report works. But the before (running against Sales Bad) and after repointing to Sales report definitions are identical. Can anyone explain this to me? i have a script that searches text in report definitions and i want to be able to keep track of Sales BAD and Sales reported to help the client keep track of the 500 reports that have to be repointed. Anyone have any experience with this? 

Sorry to be dense. My original question probably provided too much detail.  

1) will reports written against package1 still work when package1 is renamed to package2. 
2) does the report definitionchange when package1 is renamed to package2 (remember - the package name is in the report definition)

@brenda grossnickle - it does not affect the report definitions. In my opinion that works fine. only the properites of the reports are affected

@Thomas Bertl - what works fine? The renaming of the package will update the report definitions that reference the renamed package and i will see the new name in the report definition? 

It has to do with browser cache. after restarting browser, and maybe deleting cache, it works fine.

We had a corrupted deployed Framework Manager package - Sales. We redeployed Sales and it did not fix the issue. So we renamed Sales to Sales BAD and then redeployed Sales. In my experience when you rename a Package all of the report definitions are also changed to reference the new package name. So I expected all the report definitions to reference Sales BAD. But they still reference Sales. When they run the reports they still fail with the same error so I know that they are running against Sales BAD. Then edit the report, point to redeployed Sales and the report works. But the before (running against Sales Bad) and after repointing to Sales report definitions are identical. Can anyone explain this to me? i have a script that searches text in report definitions and i want to be able to keep track of Sales BAD and Sales reported to help the client keep track of the 500 reports that have to be repointed. Anyone have any experience with this?