123Aman / reportsync

Automatically exported from code.google.com/p/reportsync
0 stars 0 forks source link

Report Source created incorrectly #45

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. select a report
2. Sync
3.

What is the expected output? What do you see instead?
Expected to see the Destination Source used for the Report that was specified 
in the Map Data Sources screen. Instead the report was pointed to the data 
source: 'AutoGen__5C6358F2_4BB6_4a1b_A16E_8D96795D8602_

What version of the product are you using? On what operating system?
1.12

Please provide any additional information below.

Original issue reported on code.google.com by jonathon...@gmail.com on 3 Jun 2014 at 3:57

GoogleCodeExporter commented 8 years ago
That is quite odd.
Just to understand this better, how do I reproduce this?

Create a report with datasource A 
Map A=B in mapped data sources, where B is in the destination server
And press sync
?

Original comment by nunespascal on 3 Jun 2014 at 6:14

GoogleCodeExporter commented 8 years ago
More Detail: I understand AutoGen_xxx may be just fine, but when click on Data 
Sources under Shared data source it says: The shared data source reference is 
no longer valid. I must manually select the datasource. Why is report sync not 
doing this correctly

Original comment by jonathon...@gmail.com on 3 Jun 2014 at 10:39

GoogleCodeExporter commented 8 years ago
I am trying to migrate 500+ reports from SCCM 2007 to SCCM 2012 and each report 
migrated has this issue. Is there something I am doing wrong or is this an 
issue? I select only some of the 850+ reports on the SCCM 2007 side, then click 
Tools/Map and there is only 1 option for the destination map, then click SYNC. 
All come over to SCCM 2012 but the data source does not exist. I am hoping this 
is an easy fix.

Original comment by brettdav...@gmail.com on 10 Jul 2014 at 7:47

GoogleCodeExporter commented 8 years ago
Also, I am migrating from SQL Server 2005 on Windows Server 2008 R2 to SQL 
Server 2012 on Windows Server 2012.

Original comment by brettdav...@gmail.com on 10 Jul 2014 at 7:50