<?xml version="1.0"?><?xml-stylesheet type="text/xsl" href="http://www.codeplex.com/rss.xsl"?><rss version="2.0"><channel><title>bipublisher Work Item Rss Feed</title><link>http://www.codeplex.com/bipublisher/WorkItem/List.aspx</link><description>bipublisher Work Item Rss Description</description><item><title>Created Issue: Enable configuration of SSAS database name [4327]</title><link>http://bipublisher.codeplex.com/WorkItem/View.aspx?WorkItemId=4327</link><description>We would like to be able to change the SSAS database name defined in the data source during publishing. Could this be added in&amp;#63;&lt;br /&gt;</description><author>ham26a65</author><pubDate>Wed, 23 Sep 2009 09:45:23 GMT</pubDate><guid isPermaLink="false">Created Issue: Enable configuration of SSAS database name [4327] 20090923094523A</guid></item><item><title>Commented Issue: Display condition lost</title><link>http://bipublisher.codeplex.com/WorkItem/View.aspx?WorkItemId=3853</link><description>We use birap to deploy ppm dashboard from one server to the other.&lt;br /&gt;Everything&amp;#39;s fine, except for the display condition defined on reports view. They are lost in the deployment.&lt;br /&gt;The display condition are defined on reports of type Analytic chart.&lt;br /&gt;&lt;br /&gt;I wonder if we are doing something wrong &amp;#63;&lt;br /&gt;Comments: ** Comment from web user: kevinidzi ** &lt;p&gt;&amp;#60;sigh&amp;#62; 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.  &lt;/p&gt;&lt;p&gt;When you use a BWSX file, it opens the file and takes the &amp;#39;dashboard&amp;#39; element &amp;#40;which has the same structure as the webservice&amp;#41; 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.&lt;/p&gt;</description><author>kevinidzi</author><pubDate>Fri, 17 Jul 2009 04:39:18 GMT</pubDate><guid isPermaLink="false">Commented Issue: Display condition lost 20090717043918A</guid></item><item><title>Created Issue: Display condition lost</title><link>http://bipublisher.codeplex.com/WorkItem/View.aspx?WorkItemId=3853</link><description>We use birap to deploy ppm dashboard from one server to the other.&lt;br /&gt;Everything&amp;#39;s fine, except for the display condition defined on reports view. They are lost in the deployment.&lt;br /&gt;The display condition are defined on reports of type Analytic chart.&lt;br /&gt;&lt;br /&gt;I wonder if we are doing something wrong &amp;#63;&lt;br /&gt;</description><author>Batiste</author><pubDate>Wed, 15 Jul 2009 15:27:27 GMT</pubDate><guid isPermaLink="false">Created Issue: Display condition lost 20090715032727P</guid></item><item><title>Created Issue: PAS Errors on Folder</title><link>http://www.codeplex.com/bipublisher/WorkItem/View.aspx?WorkItemId=2780</link><description>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.  &lt;br /&gt;Due to the recursive nature of folders, the existing structure of Library &amp;#47; Book &amp;#47; Page will be used when mapping with the Excel lookup file, and will be used for PPS &amp;#40;still works fine&amp;#33;&amp;#41; to keep it simple and always 3 levels - the folder will simply be ignored.&lt;br /&gt;</description><author>kevinidzi</author><pubDate>Wed, 03 Dec 2008 05:28:06 GMT</pubDate><guid isPermaLink="false">Created Issue: PAS Errors on Folder 20081203052806A</guid></item><item><title>Created Issue: Parameter Replacement not working for Child Elements</title><link>http://www.codeplex.com/bipublisher/WorkItem/View.aspx?WorkItemId=2779</link><description>Replacement in the PerformancePointUpdates element works, and the collection items below if &amp;#40;data sources, etc&amp;#41;.  But the &amp;#39;elements&amp;#39;, not collections, do not have their replacements working &amp;#40;PasChanges&amp;#41;&lt;br /&gt;</description><author>kevinidzi</author><pubDate>Wed, 03 Dec 2008 05:25:22 GMT</pubDate><guid isPermaLink="false">Created Issue: Parameter Replacement not working for Child Elements 20081203052522A</guid></item><item><title>Commented Feature: Reporting Services Integration</title><link>http://www.codeplex.com/bipublisher/WorkItem/View.aspx?WorkItemId=2648</link><description>Here are the things I&amp;#39;m thinking about, anything else you think needs to be here&amp;#63;&lt;br /&gt;&lt;br /&gt;PPS Element&lt;br /&gt;- Allow updating of PPS Element to change Server Name and have it link the correct target report&lt;br /&gt;- Allow updating of matching report parameters &amp;#40;like with excel services&amp;#41;&lt;br /&gt;&lt;br /&gt;ReportingServices Element&lt;br /&gt;- Add ability to copy RDL from a source server to a target server&lt;br /&gt;- Add ability to copy RDL from a local location to a target server&lt;br /&gt;- Add ability to copy a Datasource from a local location to a target server &amp;#40;and change underlying server&amp;#47;credentials&amp;#41;&lt;br /&gt;- Add ability to add &amp;#47; remove users and roles for Reporting Server&lt;br /&gt;- Add ability to adjust some Execution Details&lt;br /&gt;Comments: ** Comment from web user: kevinidzi ** &lt;p&gt;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.&lt;/p&gt;</description><author>kevinidzi</author><pubDate>Wed, 26 Nov 2008 22:44:10 GMT</pubDate><guid isPermaLink="false">Commented Feature: Reporting Services Integration 20081126104410P</guid></item><item><title>Created Feature: Reporting Services Integration</title><link>http://www.codeplex.com/bipublisher/WorkItem/View.aspx?WorkItemId=2648</link><description>Here are the things I&amp;#39;m thinking about, anything else you think needs to be here&amp;#63;&lt;br /&gt;&lt;br /&gt;PPS Element&lt;br /&gt;- Allow updating of PPS Element to change Server Name and have it link the correct target report&lt;br /&gt;- Allow updating of matching report parameters &amp;#40;like with excel services&amp;#41;&lt;br /&gt;&lt;br /&gt;ReportingServices Element&lt;br /&gt;- Add ability to copy RDL from a source server to a target server&lt;br /&gt;- Add ability to copy RDL from a local location to a target server&lt;br /&gt;- Add ability to copy a Datasource from a local location to a target server &amp;#40;and change underlying server&amp;#47;credentials&amp;#41;&lt;br /&gt;- Add ability to add &amp;#47; remove users and roles for Reporting Server&lt;br /&gt;- Add ability to adjust some Execution Details&lt;br /&gt;</description><author>kevinidzi</author><pubDate>Tue, 18 Nov 2008 19:01:26 GMT</pubDate><guid isPermaLink="false">Created Feature: Reporting Services Integration 20081118070126P</guid></item><item><title>Commented Feature: Side by Side Deployment</title><link>http://www.codeplex.com/bipublisher/WorkItem/View.aspx?WorkItemId=2647</link><description>Allow elements to be given unique IDs so that they can be redeployed to the same server to facilitate a dev&amp;#47;test environment.  At the same time, a prefix or suffix should be added to the name of all affected elements &amp;#40;Dashboard&amp;#47;Scorecard&amp;#47;KPI&amp;#47;Reports&amp;#47;Data Source&amp;#47;Indicator&amp;#41; to allow the different iterations to be picked out.&lt;br /&gt;Comments: ** Comment from web user: kevinidzi ** &lt;p&gt;The downwind items that need to be thought out for this to work deeply for a true side-by-side approach&amp;#58;&lt;/p&gt;&lt;p&gt;- This will not be available for PAS reports, although the PPS PAS elements would be updated.&lt;/p&gt;&lt;p&gt;- Do DCL&amp;#39;s in Sharepoint also get setup with Side By Side pre&amp;#47;suffix&amp;#63; If so, they need to be &amp;#39;approved&amp;#39; at the same time. Currently DCLs need to pre-exist since they require approval.&lt;/p&gt;&lt;p&gt;- Excel Services &lt;br /&gt;Does this use side-by-side pre&amp;#47;suffix&amp;#63; If so, the Excel XLSX report link could have the target file be added maunally in the config with the suffix &amp;#40;can do this now&amp;#41;, and then in the excelReports node for PPS, it could be stated to add the suffix&amp;#47;prefix for all of the excel reports in the matching group which would connect to the xlsx file.  That might suffice for now.&lt;/p&gt;&lt;p&gt;- Web Page Link&lt;br /&gt;PPS Element would be copied with prefix&amp;#47;suffix added to name.  Using the find&amp;#47;replace, the side by side can be done using the existing functionality.&lt;/p&gt;&lt;p&gt;- Reporting Services&amp;#63; Need to add this support first.&lt;/p&gt;</description><author>kevinidzi</author><pubDate>Tue, 18 Nov 2008 18:53:54 GMT</pubDate><guid isPermaLink="false">Commented Feature: Side by Side Deployment 20081118065354P</guid></item><item><title>Created Feature: Side by Side Deployment</title><link>http://www.codeplex.com/bipublisher/WorkItem/View.aspx?WorkItemId=2647</link><description>Allow elements to be given unique IDs so that they can be redeployed to the same server to facilitate a dev&amp;#47;test environment.  At the same time, a prefix or suffix should be added to the name of all affected elements &amp;#40;Dashboard&amp;#47;Scorecard&amp;#47;KPI&amp;#47;Reports&amp;#47;Data Source&amp;#47;Indicator&amp;#41; to allow the different iterations to be picked out.&lt;br /&gt;</description><author>kevinidzi</author><pubDate>Tue, 18 Nov 2008 18:45:22 GMT</pubDate><guid isPermaLink="false">Created Feature: Side by Side Deployment 20081118064522P</guid></item><item><title>Closed Feature: Add Find/Search Replacement for Web Page Reports</title><link>http://www.codeplex.com/bipublisher/WorkItem/View.aspx?WorkItemId=2646</link><description>Add the ability to replace out anything in a URL set for a web page report.&lt;br /&gt;</description><author>kevinidzi</author><pubDate>Tue, 18 Nov 2008 18:01:41 GMT</pubDate><guid isPermaLink="false">Closed Feature: Add Find/Search Replacement for Web Page Reports 20081118060141P</guid></item><item><title>Created Feature: Add Find/Search Replacement for Web Page Reports</title><link>http://www.codeplex.com/bipublisher/WorkItem/View.aspx?WorkItemId=2646</link><description>Add the ability to replace out anything in a URL set for a web page report.&lt;br /&gt;</description><author>kevinidzi</author><pubDate>Tue, 18 Nov 2008 18:01:04 GMT</pubDate><guid isPermaLink="false">Created Feature: Add Find/Search Replacement for Web Page Reports 20081118060104P</guid></item><item><title>Closed Feature: Enable loading PPS data from a Workspace file (BSWX)</title><link>http://www.codeplex.com/bipublisher/WorkItem/View.aspx?WorkItemId=2638</link><description>The app will load the data for PPS from a local BSWX. The current filtering that is used &amp;#40;based on a particular property for each element&amp;#41; will still be used, even for the workspace when selecting which items to update.&lt;br /&gt;</description><author>kevinidzi</author><pubDate>Mon, 17 Nov 2008 22:31:37 GMT</pubDate><guid isPermaLink="false">Closed Feature: Enable loading PPS data from a Workspace file (BSWX) 20081117103137P</guid></item><item><title>Created Feature: Enable loading PPS data from a Workspace file (BSWX)</title><link>http://www.codeplex.com/bipublisher/WorkItem/View.aspx?WorkItemId=2638</link><description>The app will load the data for PPS from a local BSWX. The current filtering that is used &amp;#40;based on a particular property for each element&amp;#41; will still be used, even for the workspace when selecting which items to update.&lt;br /&gt;</description><author>kevinidzi</author><pubDate>Mon, 17 Nov 2008 22:30:05 GMT</pubDate><guid isPermaLink="false">Created Feature: Enable loading PPS data from a Workspace file (BSWX) 20081117103005P</guid></item><item><title>Closed Feature: Add IsEnabled to all elements within a collection</title><link>http://www.codeplex.com/bipublisher/WorkItem/View.aspx?WorkItemId=2624</link><description>It is easier to just have an IsEnabled attribute on the elements to help with setting up the sections, and turning things off when environmental issues are found.  With the other feature about using parameters, you could have everything related to proclarity, for example, be disabled if for some reason it is not working, yet still deploy and work with the other items as needed.&lt;br /&gt;</description><author>kevinidzi</author><pubDate>Sun, 16 Nov 2008 09:57:43 GMT</pubDate><guid isPermaLink="false">Closed Feature: Add IsEnabled to all elements within a collection 20081116095743A</guid></item><item><title>Closed Feature: Ability to inject parameter substitution for values in config file</title><link>http://www.codeplex.com/bipublisher/WorkItem/View.aspx?WorkItemId=2623</link><description>Feature will allow user to enter command line parameters.  When done, any entries for the selected deployment using those parameters in brackets will be replaced with the command line parameter.  This will allow a deployment type to be reused across different tiers, using different command line arguments &amp;#40;vs hardwiring it in the config file&amp;#41;.&lt;br /&gt;</description><author>kevinidzi</author><pubDate>Sun, 16 Nov 2008 09:57:43 GMT</pubDate><guid isPermaLink="false">Closed Feature: Ability to inject parameter substitution for values in config file 20081116095743A</guid></item><item><title>Created Feature: Add IsEnabled to all elements within a collection</title><link>http://www.codeplex.com/bipublisher/WorkItem/View.aspx?WorkItemId=2624</link><description>It is easier to just have an IsEnabled attribute on the elements to help with setting up the sections, and turning things off when environmental issues are found.  With the other feature about using parameters, you could have everything related to proclarity, for example, be disabled if for some reason it is not working, yet still deploy and work with the other items as needed.&lt;br /&gt;</description><author>kevinidzi</author><pubDate>Sun, 16 Nov 2008 09:56:18 GMT</pubDate><guid isPermaLink="false">Created Feature: Add IsEnabled to all elements within a collection 20081116095618A</guid></item><item><title>Created Feature: Ability to inject parameter substitution for values in config file</title><link>http://www.codeplex.com/bipublisher/WorkItem/View.aspx?WorkItemId=2623</link><description>Feature will allow user to enter command line parameters.  When done, any entries for the selected deployment using those parameters in brackets will be replaced with the command line parameter.  This will allow a deployment type to be reused across different tiers, using different command line arguments &amp;#40;vs hardwiring it in the config file&amp;#41;.&lt;br /&gt;</description><author>kevinidzi</author><pubDate>Sun, 16 Nov 2008 09:38:09 GMT</pubDate><guid isPermaLink="false">Created Feature: Ability to inject parameter substitution for values in config file 20081116093809A</guid></item><item><title>Closed Feature: Make app UAC aware</title><link>http://www.codeplex.com/bipublisher/WorkItem/View.aspx?WorkItemId=2609</link><description>When running app in a non-uac command prompt, it fails, vs prompting for elevation.  The app must be run in admin console generally, so add a manifest to require that at compiletime.&lt;br /&gt;Comments: Related to the recent release</description><author>kevinidzi</author><pubDate>Fri, 14 Nov 2008 18:12:34 GMT</pubDate><guid isPermaLink="false">Closed Feature: Make app UAC aware 20081114061234P</guid></item><item><title>Closed Issue: No paramaeters at command line causes app to fail</title><link>http://www.codeplex.com/bipublisher/WorkItem/View.aspx?WorkItemId=2608</link><description>Update the app to show the deployments in the configuration file which are loadable, if no commands are provided at commandline for app.&lt;br /&gt;Comments: Related to the recent release</description><author>kevinidzi</author><pubDate>Fri, 14 Nov 2008 18:12:33 GMT</pubDate><guid isPermaLink="false">Closed Issue: No paramaeters at command line causes app to fail 20081114061233P</guid></item><item><title>Closed Feature: Support for syncing an Excel Services document to any target location</title><link>http://www.codeplex.com/bipublisher/WorkItem/View.aspx?WorkItemId=2573</link><description>Currently, the folder under the source and target sites must be the same to deploy. It would be helpful if a target folder could be provided.&lt;br /&gt;Comments: Related to the recent release</description><author>kevinidzi</author><pubDate>Fri, 14 Nov 2008 18:12:32 GMT</pubDate><guid isPermaLink="false">Closed Feature: Support for syncing an Excel Services document to any target location 20081114061232P</guid></item></channel></rss>