Several Issues Encountered using ReportSync

[GoogleCodeExporter]

I have the following feedback on ReportSync 1.1.2
Overall this process was VERY helpful, but there are some issues that required 
some investigation. I have posted the major one – Shared Datasource not being 
set as Defect#45
Below are the other issues I encountered

#1. When clicking on Load it would be nice to get feedback that it is doing 
something

#2. It is not clear if you have to select the destination folder – especially 
on subsequent syncs
For example sync was done for most all categories and reports
Doing sync again select 1 report in a category that was not migrated.  Do you 
check anything on the right?  If I don’t the report gets put at the root.
So then check the category box, but then it sync’d ALL the reports. I only 
wanted one report – see below on all reports being checked

#3. If you check the box on the category all reports beneath that category are 
not selected, but if you save and open it open, then all will be selected

#4. It takes a bit for the sync to start, an hourglass would be nice

#5. The status bars stay completed after clicking OK that the ReportSync 
completed

#6. (this is defect #45) After migrating the report will not run  as the shared 
data source for the report server is not valid:
The report server cannot process the report or shared dataset. The shared data 
source 'AutoGen__5C6358F2_4BB6_4a1b_A16E_8D96795D8602_' for the report server 
or SharePoint site is not valid. Browse to the server or site and select a 
shared data source. (rsInvalidDataSourceReference) 

Selecting Manage for the report, then Data Sources shows:
AutoGen_5C6358F2_4BB6_4a1b_A16E_8D96795D8602_
A Shared data source is selected
Select a share data source [Browse]! The shared data source reference is no 
longer valid

I can be reached at TomG @ hp.com
Thanks

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

[GoogleCodeExporter]

Thanks for your very detailed feedback.
I will definitely investigate every one of them.

It will take me some time to fix these though, as this project is currently on 
the back burner.

If an issue really starts troubling you, mark it as a priority high and I will 
look into it immediately

Original comment by nunespascal on 11 Jun 2014 at 6:42

• Changed state: Accepted

[GoogleCodeExporter]

Agreed on all items. #6 is the biggest pain for me as I have 500+ reports to 
migrate for SCCM 2012 migration and I am trying to find a way to not have to 
touch each report. I shall also update issue #45.

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