BI Report Automation Publisher

Closed Issue: Parameter Replacement not working for Child Elements [2779]

kevinidzi — Thu, 16 May 2013 00:08:41 GMT

Replacement in the PerformancePointUpdates element works, and the collection items below if (data sources, etc). But the 'elements', not collections, do not have their replacements working (PasChanges)

Closed Issue: PAS Errors on Folder [2780]

kevinidzi — Thu, 16 May 2013 00:08:41 GMT

When the Libraries have Pages inside of Folders on the PAS Server, the tool errors and dies. The fix would be to support recursively going through the folder to find the guids and do the matching.
Due to the recursive nature of folders, the existing structure of Library / Book / Page will be used when mapping with the Excel lookup file, and will be used for PPS (still works fine!) to keep it simple and always 3 levels - the folder will simply be ignored.

Source code checked in, #80132

Project Collection Service Accounts — Mon, 01 Oct 2012 21:49:39 GMT

Upgrade: New Version of LabDefaultTemplate.xaml. To upgrade your build definitions, please visit the following link: http://go.microsoft.com/fwlink/?LinkId=254563

Source code checked in, #80131

Project Collection Service Accounts — Mon, 01 Oct 2012 21:43:10 GMT

Checked in by server upgrade

Source code checked in, #55373

_TFSSERVICE — Mon, 02 Aug 2010 22:49:34 GMT

Checked in by server upgrade

Created Issue: Enable configuration of SSAS database name [4327]

ham26a65 — Wed, 23 Sep 2009 09:45:23 GMT

We would like to be able to change the SSAS database name defined in the data source during publishing. Could this be added in?

Commented Issue: Display condition lost

kevinidzi — Fri, 17 Jul 2009 04:39:18 GMT

We use birap to deploy ppm dashboard from one server to the other.
Everything's fine, except for the display condition defined on reports view. They are lost in the deployment.
The display condition are defined on reports of type Analytic chart.

I wonder if we are doing something wrong ?
Comments: ** Comment from web user: kevinidzi **

<sigh> no. unfortunately you are not. This is an issue someone else actually reported and I currently do not have a good answer for it. This is due to the way the data is loaded in the tool when using a BWSX file. IT works if you give it a source server, and a target server. The tool picks up the dashboard object from the webservice and all is good.

When you use a BWSX file, it opens the file and takes the 'dashboard' element (which has the same structure as the webservice) and deserializes it to an object to use in the tool interchangeably with the rest of the code as if it came from a webservice. The issue is that this deserialization seems to not work with an embedded datatable inside the BWSX file. Something to do with the namespace and the data which is in the bwsx does not get into the object. Since the xmlserializer is a very general object, I have not found a way to make it also deserialize the datatable correctly with the rest of the object, so I am a bit stuck on that one.

Created Issue: Display condition lost

Batiste — Wed, 15 Jul 2009 15:27:27 GMT

New Post: Side By Side Review

kevinidzi — Fri, 19 Dec 2008 21:30:23 GMT

I'm beginning to think more about how to do the side by side versioning. The main goals of side by side deployment are:

Generate some sort of unique Prefix or Suffix to elements when deploying to notate Dev/Test (or remove for Production).
Enable someone to publish to Dev, and then go from Dev to Test, and from Test to Prod (or Dev to Prod)
Allow the option to regenerate IDs for all of the PPS Elemenets.
This is especially helpful if some other person publishes an item and you do not have access to overwrite it. With this, you can ignore theirs (if time is tight), publish with a different ID and have them fix the initial element when they get back (or delete it).
If regenerating IDs for target elements, then only regenerate the ID if the target object for the specified env correlation (Dev/test) is not created. If it already exists, reuse that ID (so if you deploy the dashboard for dev/test, you will not need to redeploy when updating elements).
1. Regenerating all of the IDs can be done by just deleting the elements which match the correlation for Dev/Test, and then republish again. Since they will not be found, new IDs will be generated.
Allow the ability to delete target elements. If you have a dev, test or other - you may want to clean up or remove things. Deleting items through PPS Editor can be a bit arduous, so having an easier way to do so would be helpful.

Proposal is below, hopefully it is self-explanatory, If you have any questions, comments, or suggestions, feel free to add them. The one thing that will make the next release break current scripts is that I will require the deployment have a correlationName. That will be used to group all of the matching elements together.

If you want to deploy the elements to a Test correlation (as a side-by-side, you can tell it to regenerate the IDs. Then the Dev correlation would remain, and new elements with the TEst correlation would appear. Otherwise, the Test correlated elements will overwrite the dev ones when you deploy.

<deployment type="testSharePointDeploySideBySide">
    <performancePointUpdates>
        <performancePoint sourceWorkspace="C:\test.bswx"
                targetMonitoringWebservice=http://...:40000/Webservice/pmservice.asmx
                correlationName="DEV"
                matchOnProperty="Reporting"
                matchOnValue="1.0.0.0"
                action="Publish">

Created Issue: PAS Errors on Folder

kevinidzi — Wed, 03 Dec 2008 05:28:06 GMT

Created Issue: Parameter Replacement not working for Child Elements

kevinidzi — Wed, 03 Dec 2008 05:25:22 GMT

Source code checked in, #18201

kevinidzi — Wed, 03 Dec 2008 00:07:38 GMT

Added support for Proclarity server to house pages under folders.

Source code checked in, #18184

kevinidzi — Tue, 02 Dec 2008 18:14:49 GMT

Update to fix an issue where child elements do not have replacements performed correctly.

Updated Release: BI Report Automation Publisher v1.5 (Nov 26, 2008)

kevinidzi — Wed, 26 Nov 2008 22:52:21 GMT

Purpose / Goals

To remove manual editing of Proclarity Analytic Server (PAS) report pages, PerformancePoint elements, and Excel Service files when moving from one server to another during either a BVT run, or nightly process.
Allow integration with deploy scripts or BVT execution during release cycles from one machine to another without the need for manual tweaking.

Features

Supports editing of key parts of Proclarity Analytic Server reports, PerformancePoint reports, Excel Service Data Connections, and numerous other things.

Changes

Includes support for modifying SSRS Server Links and Report Paths within PerformancePoint during publish
Support for command line parameter substitution in any configuration element to minimize 'hardcoding' values or requiring a post-deploy config modification of the file before execution.

Released: BI Report Automation Publisher v1.5 (Nov 26, 2008)

Wed, 26 Nov 2008 22:52:21 GMT

Purpose / Goals

To remove manual editing of Proclarity Analytic Server (PAS) report pages, PerformancePoint elements, and Excel Service files when moving from one server to another during either a BVT run, or nightly process.
Allow integration with deploy scripts or BVT execution during release cycles from one machine to another without the need for manual tweaking.

Features

Supports editing of key parts of Proclarity Analytic Server reports, PerformancePoint reports, Excel Service Data Connections, and numerous other things.

Changes

Includes support for modifying SSRS Server Links and Report Paths within PerformancePoint during publish
Support for command line parameter substitution in any configuration element to minimize 'hardcoding' values or requiring a post-deploy config modification of the file before execution.

Updated Release: BI Report Automation Publisher v1.5 (Nov 26, 2008)

kevinidzi — Wed, 26 Nov 2008 22:50:21 GMT

Purpose / Goals

To remove manual editing of Proclarity Analytic Server (PAS) report pages, PerformancePoint elements, and Excel Service files when moving from one server to another during either a BVT run, or nightly process.
Allow integration with deploy scripts or BVT execution during release cycles from one machine to another without the need for manual tweaking.

Features

Supports editing of key parts of Proclarity Analytic Server reports, PerformancePoint reports, Excel Service Data Connections, and numerous other things.

Source code checked in, #18071

kevinidzi — Wed, 26 Nov 2008 22:45:38 GMT

Added PPS SSRS Element Link Modification

Commented Feature: Reporting Services Integration

kevinidzi — Wed, 26 Nov 2008 22:44:10 GMT

Here are the things I'm thinking about, anything else you think needs to be here?

PPS Element
- Allow updating of PPS Element to change Server Name and have it link the correct target report
- Allow updating of matching report parameters (like with excel services)

ReportingServices Element
- Add ability to copy RDL from a source server to a target server
- Add ability to copy RDL from a local location to a target server
- Add ability to copy a Datasource from a local location to a target server (and change underlying server/credentials)
- Add ability to add / remove users and roles for Reporting Server
- Add ability to adjust some Execution Details
Comments: ** Comment from web user: kevinidzi **

Well, the PPS Element part is completed. It currently does not deploy anything for Reporting Services. If needed, RSDeploy already does this and can be used until it is fully integrated with this application.

Updated Wiki: Feature Roadmap

kevinidzi — Tue, 18 Nov 2008 19:10:20 GMT

I will leave it up to the community to determine the direction of this tool. There are some areas which would be interesting to move towards, as there are many scenarios that are rather tedious / manual for publishing reports currently.

PerformancePoint Target Location Redirection

Status: Feature in Tracker - on Radar

Currently, this tool moves PerformancePoint (PPS) Elements from the source to target retaining the same naming and structure as it came from. For some people, it might be useful to have the PPS elements moved with a suffix (or prefix) attached for side-by-side testing. And it might be helpful to have the linked reports be retargeted to point to different Libraries / folders within Sharepoint/PAS

This does not apply to Proclarity since the tool works directly on the reports. And it does not apply to the Excel Serivce direct updates since the target URL is included.

PPS Sql Server Reporting Services (SSRS) Report Support

Status: Feature in Tracker - on Radar

I have not worked with SSRS reports in my current work. If someone has and would like to work with me, we might be able to find a way to integrate support to allow redirecting the PPS Report's target server.

Deploying PPS Dashboard

Status: Method is known, time needed to code up solution

Currently, all of the elements are update, but if the dashboard itself is modified or components added/removed, it will need to be manually deployed. There are a string of Sharepoint Webservice calls when this happens to put the files at the target location and make it available. I'm thinking if instead of deploying, focusing on "Publishing" from PPS and then just make some more general elements in the config to copy files, or a folderful of files to SharePoint as-is, which would then work.

Updating Post-Deployed PPS Webparts

Status: Idea Percolating... needs a bit more research to link webpart with PPS element

Ever want to remove chrome on a webpart, or adjust the template externally (sharepoint site is secured from template modifications)? Then being able to adjust the webpart that PPS generates would be very helpful. Currently we are actually doing this as manual steps after we deploy (when we need to). It would be nice to use the Webpart ASMX to make adjustments as needed and remove the manual step.

Deploying PAS Reports

Status: Stalled - Would be nice, not sure how to continue

It might be helpful to have the tool actually take PAS reports from a source and deploy them on a target. In looking at this briefly, I have no idea how the Books are generated when sent to the server for an update, so any help would be appreciated.

Updated Wiki: Feature Roadmap

kevinidzi — Tue, 18 Nov 2008 19:09:47 GMT

PerformancePoint Target Location Redirection

Status: Feature in Tracker - on Radar

PPS Sql Server Reporting Services (SSRS) Report Support

Status: Feature in Tracker - on Radar

Deploying PPS Dashboard

Status: Method is known, time needed to code up solution

Updating Post-Deployed PPS Webparts

Status: Idea Percolating... needs a bit more research to link webpart with PPS element

BI Report Automation Publisher

Closed Issue: Parameter Replacement not working for Child Elements [2779]

Closed Issue: PAS Errors on Folder [2780]

Source code checked in, #80132

Source code checked in, #80131

Source code checked in, #55373

Created Issue: Enable configuration of SSAS database name [4327]

Commented Issue: Display condition lost

Created Issue: Display condition lost

New Post: Side By Side Review

Created Issue: PAS Errors on Folder

Created Issue: Parameter Replacement not working for Child Elements

Source code checked in, #18201

Source code checked in, #18184

Updated Release: BI Report Automation Publisher v1.5 (Nov 26, 2008)

Released: BI Report Automation Publisher v1.5 (Nov 26, 2008)

Updated Release: BI Report Automation Publisher v1.5 (Nov 26, 2008)

Source code checked in, #18071

Commented Feature: Reporting Services Integration

Updated Wiki: Feature Roadmap

PerformancePoint Target Location Redirection

PPS Sql Server Reporting Services (SSRS) Report Support

Deploying PPS Dashboard

Updating Post-Deployed PPS Webparts

Deploying PAS Reports

Updated Wiki: Feature Roadmap

PerformancePoint Target Location Redirection

PPS Sql Server Reporting Services (SSRS) Report Support

Deploying PPS Dashboard

Updating Post-Deployed PPS Webparts

Deploying PAS Reports (Would be nice, not sure how to continue)