Hi.
I have seen this behaviour now and then. On a development server we have created reports and updated those reports now and then with newer versions of the rdl-files. All works as intended on the dev-server there are no doubles. We export a Managed solution just containing reports. Then we import that solution on a test-server.
First I remove the existing report-solution just to be safe. I update the browser and my existing reports are gone. Check.
I then import the managed report-solution. CTRL-F5 a few times then I go to the report area and discover Doubles on two reports and another report contains an older rdl-file not showing in the dev-server.
On the Reporting Server we manually removed the older versions of one doppelganger but it still shows in Dynamics.
How is this possible and how do I fix it?
*This post is locked for comments
The last problem was resolved by removing the report completely and creating it again with an imported rdl.
I managed to get rid of one persisting doppelganger by importing a new rdl in to it and then I was allowed to delete the report. So I am down to the report that somehow exports an older version of a rdl. I should be able to fix that by removing the report completely from the dev-server and start over.
That is my next step but if I fix the exported solution I still have to fix the solution on the dev server. I think I will tear it down and start over.
Have you checked the Solution.xml and customizations.xml for any faulty/duplicate data?
I'm on version 1612 (8.2.2.112) (DB 8.2.2.112) local.
The solution is behaving very strange indeed. When I create a report within my solution and import a rdl a double post is now created within the solution. They are created at the same time, the same content and two different guid (of course). Then I remove one of them. Same the solution, publish export etc. When I import the solution I get my newest stuff ok but one old doppelganger shows up again and one existing file have an old version of a rdl-file in it.
I am considering saving all descripting texts, export the rdls, remove the solution and start over. This solution behaves like it is possessed. The target server just behaves like the solution tells it to do.
Hi,
On what CRM Build are you on?
If you compare the duplicates with the original entries - do you see any patterns (CreatedOn, CreatedBy, ModifiedOn, ModifiedBy, Owner)?
Regards,
Radu
Mohamed Amine Mahmoudi
83
Super User 2025 Season 1
Community Member
54
Victor Onyebuchi
6