parameters not updated on re-publish

RS2005 sp1 - I have a report that was published to the report server. I needed to make changes to some of the parameters. I changed them to be INTERNAL. When I re-published the report from visual studio to the server (selecting overwrite item if exists) - that INTERNAL parameters were still showing and active when I chose VIEW report. Then I tried the Upload File from the report server to see if that would behave differently ... but I got the same result. Can someone tell me why this is happening?

I am having the same problem, if anyone can help I would appreciate it.

I recognize that deleting the deployed report fixes the problem but for a fast paced environment that is not very efficient.

We are on 2005 SP1.

Thanks,
Eric

parameters not updated on re-publish

RS2005 sp1 - I have a report that was published to the report server. I needed to make changes to some of the parameters. I changed them to be INTERNAL. When I re-published the report from visual studio to the server (selecting overwrite item if exists) - that INTERNAL parameters were still showing and active when I chose VIEW report. Then I tried the Upload File from the report server to see if that would behave differently ... but I got the same result. Can someone tell me why this is happening?

I am having the same problem, if anyone can help I would appreciate it.

I recognize that deleting the deployed report fixes the problem but for a fast paced environment that is not very efficient.

We are on 2005 SP1.

Thanks,
Eric

Parameters Bar

Hello,
I would like to expand the size of parameters bar, is it possible with SP1?
I have too many parameters to deal with and I don't want users to scroll
through.
Thanks.
Regards,
CemBecause of an IE issue the splitter bar between the parameter area and the
report body does not remember it location when Report Manager (http:
//<someservername>/reports/...). The splitter bar behavior works correctly
when you are view the report via the server (http://
<someservername>/reportserver/...)
--
Bruce Johnson [MSFT]
Microsoft SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Cem Demircioglu" <cem@.NoSpamPlease.com> wrote in message
news:%23r6kkCveEHA.3376@.TK2MSFTNGP10.phx.gbl...
>
> Hello,
> I would like to expand the size of parameters bar, is it possible with
SP1?
> I have too many parameters to deal with and I don't want users to scroll
> through.
> Thanks.
> Regards,
> Cem
>

Parameterized and static filter on the same article

Hi,
MS SQL Server Standart 2005 RTM, MS Windows Server 2003 SP1. Is it possible
to combine, mix, or have a static and a parameterized filter on the same
article simultaneously?
Thanks, Oskar.
Forgot to mention that I want to use a static filter only within the
boundaries of a dynamic partition, that is, I want to filter out rows of
dynamic filter by means of a static filter. Say, I have a table SALES and
columns LOCATION and STATUS in it. I want non-overlapping partitions by
LOCATION and in each LOCATION only rows which have STATUS = 'Placed'. Can I
do that?
"Oskar" wrote:

> Hi,
> MS SQL Server Standart 2005 RTM, MS Windows Server 2003 SP1. Is it possible
> to combine, mix, or have a static and a parameterized filter on the same
> article simultaneously?
> Thanks, Oskar.
|||Hi Oskar,
Once you have your partition by LOCATION, you should be able to use
AND in the filter's WHERE clause to limit your rows even further.
Something like
SELECT publishedColumns
FROM articleTable
WHERE LOCATION IN (SELECT LOCATION
FROM locationTable
WHERE username = suser_sname())
AND STATUS = 'Placed'
Thanks,
Ken
On Feb 16, 12:48 pm, Oskar <O...@.discussions.microsoft.com> wrote:[vbcol=seagreen]
> Forgot to mention that I want to use a static filter only within the
> boundaries of a dynamic partition, that is, I want to filter out rows of
> dynamic filter by means of a static filter. Say, I have a table SALES and
> columns LOCATION and STATUS in it. I want non-overlapping partitions by
> LOCATION and in each LOCATION only rows which have STATUS = 'Placed'. Can I
> do that?
> "Oskar" wrote:
|||Ken,
Problem with that is that rows with STATUS = 'Pending' won't be allowed in
SALES at subscribers by merge replication, because it "suspects" that
partitions will overlap.
"KenJ" wrote:

> Hi Oskar,
> Once you have your partition by LOCATION, you should be able to use
> AND in the filter's WHERE clause to limit your rows even further.
> Something like
> SELECT publishedColumns
> FROM articleTable
> WHERE LOCATION IN (SELECT LOCATION
> FROM locationTable
> WHERE username = suser_sname())
> AND STATUS = 'Placed'
>
> Thanks,
> Ken
> On Feb 16, 12:48 pm, Oskar <O...@.discussions.microsoft.com> wrote:
>
>