Showing posts with label populated. Show all posts
Showing posts with label populated. Show all posts

Saturday, February 25, 2012

Default Values not Selected on Report Manager

I have a report with quite a few parameters, both multivalue and single, all populated from a query. In the Report Designer I have set up default values and everything works great. When I deploy these reports the default values are not being set. Am I missing a step?It's a SQL report or an MDX report?

In the report manager when you choose the parameters and execute the report. It's rendered fine?|||

The server has behavior that it keeps the old parameter defaults that are set, even after republishing. Try deleting the report and republishing.

|||I have not seen the Report Server maintain default parameter values when a report is redeployed. After redeploying the report I have to manually reset the defaults (Properties tab --> Parameters page --> Override Default button).

If there is some property of the server that would persist the defaults between deployments, I'd love to learn about it. Thanks.

Default values in tables

Hello all,
I thought that I knew how to do this, but I must be having a mental
block. I have a SQL table, populated with 14,000 records. I have
several int columns which I need to change the default value to 0
(zero), and a datetime column which I would like to default to todays
date and current time. I have gone into design view for each of the
int columns and I have simply entered 0 in the "Default value" box.
For the datetime column, I have changed the Default Value to
getdate().
I have gone to enter a new record in the table, and none of the
defaults work. All still default to <null>.
Any ideas why this is not working? Does it only work on a table
without existing data?
Thanks
Colin
Bobby
It does work
CREATE TABLE #Test (c1 datetime DEFAULT GETDATE(),c2 INT DEFAULT 0)
INSERT INTO #Test DEFAULT VALUES
SELECT * FROM #Test
Check out that you have created default constraints
SELECT scobj.name, cols.name
FROM sysconstraints sc
INNER JOIN sysobjects scobj
ON sc.constid = scobj.id
AND sc.id=OBJECT_ID('tblname')
INNER JOIN syscolumns cols
ON sc.id = cols.id
AND sc.colid = cols.colid
GO
"Bobby" <bobby2@.blueyonder.co.uk> wrote in message
news:1174466348.874762.198710@.e1g2000hsg.googlegro ups.com...
> Hello all,
> I thought that I knew how to do this, but I must be having a mental
> block. I have a SQL table, populated with 14,000 records. I have
> several int columns which I need to change the default value to 0
> (zero), and a datetime column which I would like to default to todays
> date and current time. I have gone into design view for each of the
> int columns and I have simply entered 0 in the "Default value" box.
> For the datetime column, I have changed the Default Value to
> getdate().
> I have gone to enter a new record in the table, and none of the
> defaults work. All still default to <null>.
> Any ideas why this is not working? Does it only work on a table
> without existing data?
> Thanks
> Colin
>
|||On Mar 21, 1:39 pm, "Bobby" <bob...@.blueyonder.co.uk> wrote:
> Hello all,
> I thought that I knew how to do this, but I must be having a mental
> block. I have a SQL table, populated with 14,000 records. I have
> several int columns which I need to change the default value to 0
> (zero), and a datetime column which I would like to default to todays
> date and current time. I have gone into design view for each of the
> int columns and I have simply entered 0 in the "Default value" box.
> For the datetime column, I have changed the Default Value to
> getdate().
> I have gone to enter a new record in the table, and none of the
> defaults work. All still default to <null>.
> Any ideas why this is not working? Does it only work on a table
> without existing data?
> Thanks
> Colin
Existing data values in columns will not change when you introduce
default values. Only new records (insertions) will have default
values .
If you want to change for the existing records , you need to update
the value.
After updating the value , alter table not to allow nulls on these
columns
|||Hi[vbcol=seagreen]
He said that he inserted a new row as I understood it.
"M A Srinivas" <masri999@.gmail.com> wrote in message
news:1174467529.301295.252230@.l77g2000hsb.googlegr oups.com...
> On Mar 21, 1:39 pm, "Bobby" <bob...@.blueyonder.co.uk> wrote:
> Existing data values in columns will not change when you introduce
> default values. Only new records (insertions) will have default
> values .
> If you want to change for the existing records , you need to update
> the value.
> After updating the value , alter table not to allow nulls on these
> columns
>
|||On 21 Mar, 09:06, "Uri Dimant" <u...@.iscar.co.il> wrote:
> Hi
>
> He said that he inserted a new row as I understood it.
>
That's correct. I didn't mean that I wanted to change existing values,
what I meant was will default values only work on tables without
existing data.
However, I know now that they will work on tables with existing data.
I guess I've been working with Access too long. In Access, if I set
default values and then go to insert a new record directly into the
table, I can see the default values appear in the new row as I type.
However, if I do the same in SQL server, a load of nulls appear in the
new row, where the defaults should be. The defaults only appear after
I have closed the table and gone back into it. That's what confused
me.
Thanks for your help
Colin
|||Boddy
See my first reply to you. After setting DEFAULT constraint have save the
table's setting ? Can you show us step by step what you did so far?
"Bobby" <bobby2@.blueyonder.co.uk> wrote in message
news:1174470005.140442.271260@.e65g2000hsc.googlegr oups.com...
> On 21 Mar, 09:06, "Uri Dimant" <u...@.iscar.co.il> wrote:
> That's correct. I didn't mean that I wanted to change existing values,
> what I meant was will default values only work on tables without
> existing data.
> However, I know now that they will work on tables with existing data.
> I guess I've been working with Access too long. In Access, if I set
> default values and then go to insert a new record directly into the
> table, I can see the default values appear in the new row as I type.
> However, if I do the same in SQL server, a load of nulls appear in the
> new row, where the defaults should be. The defaults only appear after
> I have closed the table and gone back into it. That's what confused
> me.
> Thanks for your help
> Colin
>
|||Remember also that defaults are only assigned to columns that are NOT
part of the INSERT. If you do not use a column list you will not get
a default, even if you assign NULL.
INSERT TableName VALUES('abc', NULL)
That will only work with a two column table, and will not use defaults
for either column.
INSERT TableName (col1, col10) VALUES ('abc', NULL)
That will assign the specified values to those two columns, but assign
the default - or NULL if there is no default - to all other columns.
Roy Harvey
Beacon Falls, CT
On 21 Mar 2007 01:39:08 -0700, "Bobby" <bobby2@.blueyonder.co.uk>
wrote:

>Hello all,
>I thought that I knew how to do this, but I must be having a mental
>block. I have a SQL table, populated with 14,000 records. I have
>several int columns which I need to change the default value to 0
>(zero), and a datetime column which I would like to default to todays
>date and current time. I have gone into design view for each of the
>int columns and I have simply entered 0 in the "Default value" box.
>For the datetime column, I have changed the Default Value to
>getdate().
>I have gone to enter a new record in the table, and none of the
>defaults work. All still default to <null>.
>Any ideas why this is not working? Does it only work on a table
>without existing data?
>Thanks
>Colin

Default values in tables

Hello all,
I thought that I knew how to do this, but I must be having a mental
block. I have a SQL table, populated with 14,000 records. I have
several int columns which I need to change the default value to 0
(zero), and a datetime column which I would like to default to todays
date and current time. I have gone into design view for each of the
int columns and I have simply entered 0 in the "Default value" box.
For the datetime column, I have changed the Default Value to
getdate().
I have gone to enter a new record in the table, and none of the
defaults work. All still default to <null>.
Any ideas why this is not working? Does it only work on a table
without existing data?
Thanks
ColinBobby
It does work
CREATE TABLE #Test (c1 datetime DEFAULT GETDATE(),c2 INT DEFAULT 0)
INSERT INTO #Test DEFAULT VALUES
SELECT * FROM #Test
Check out that you have created default constraints
SELECT scobj.name, cols.name
FROM sysconstraints sc
INNER JOIN sysobjects scobj
ON sc.constid = scobj.id
AND sc.id=OBJECT_ID('tblname')
INNER JOIN syscolumns cols
ON sc.id = cols.id
AND sc.colid = cols.colid
GO
"Bobby" <bobby2@.blueyonder.co.uk> wrote in message
news:1174466348.874762.198710@.e1g2000hsg.googlegroups.com...
> Hello all,
> I thought that I knew how to do this, but I must be having a mental
> block. I have a SQL table, populated with 14,000 records. I have
> several int columns which I need to change the default value to 0
> (zero), and a datetime column which I would like to default to todays
> date and current time. I have gone into design view for each of the
> int columns and I have simply entered 0 in the "Default value" box.
> For the datetime column, I have changed the Default Value to
> getdate().
> I have gone to enter a new record in the table, and none of the
> defaults work. All still default to <null>.
> Any ideas why this is not working? Does it only work on a table
> without existing data?
> Thanks
> Colin
>|||On Mar 21, 1:39 pm, "Bobby" <bob...@.blueyonder.co.uk> wrote:
> Hello all,
> I thought that I knew how to do this, but I must be having a mental
> block. I have a SQL table, populated with 14,000 records. I have
> several int columns which I need to change the default value to 0
> (zero), and a datetime column which I would like to default to todays
> date and current time. I have gone into design view for each of the
> int columns and I have simply entered 0 in the "Default value" box.
> For the datetime column, I have changed the Default Value to
> getdate().
> I have gone to enter a new record in the table, and none of the
> defaults work. All still default to <null>.
> Any ideas why this is not working? Does it only work on a table
> without existing data?
> Thanks
> Colin
Existing data values in columns will not change when you introduce
default values. Only new records (insertions) will have default
values .
If you want to change for the existing records , you need to update
the value.
After updating the value , alter table not to allow nulls on these
columns|||Hi
>> I have gone to enter a new record in the table, and none of the
>> defaults work. All still default to <null>.
He said that he inserted a new row as I understood it.
"M A Srinivas" <masri999@.gmail.com> wrote in message
news:1174467529.301295.252230@.l77g2000hsb.googlegroups.com...
> On Mar 21, 1:39 pm, "Bobby" <bob...@.blueyonder.co.uk> wrote:
>> Hello all,
>> I thought that I knew how to do this, but I must be having a mental
>> block. I have a SQL table, populated with 14,000 records. I have
>> several int columns which I need to change the default value to 0
>> (zero), and a datetime column which I would like to default to todays
>> date and current time. I have gone into design view for each of the
>> int columns and I have simply entered 0 in the "Default value" box.
>> For the datetime column, I have changed the Default Value to
>> getdate().
>> I have gone to enter a new record in the table, and none of the
>> defaults work. All still default to <null>.
>> Any ideas why this is not working? Does it only work on a table
>> without existing data?
>> Thanks
>> Colin
> Existing data values in columns will not change when you introduce
> default values. Only new records (insertions) will have default
> values .
> If you want to change for the existing records , you need to update
> the value.
> After updating the value , alter table not to allow nulls on these
> columns
>|||On 21 Mar, 09:06, "Uri Dimant" <u...@.iscar.co.il> wrote:
> Hi
> >> I have gone to enter a new record in the table, and none of the
> >> defaults work. All still default to <null>.
> He said that he inserted a new row as I understood it.
>
That's correct. I didn't mean that I wanted to change existing values,
what I meant was will default values only work on tables without
existing data.
However, I know now that they will work on tables with existing data.
I guess I've been working with Access too long. In Access, if I set
default values and then go to insert a new record directly into the
table, I can see the default values appear in the new row as I type.
However, if I do the same in SQL server, a load of nulls appear in the
new row, where the defaults should be. The defaults only appear after
I have closed the table and gone back into it. That's what confused
me.
Thanks for your help
Colin|||Boddy
See my first reply to you. After setting DEFAULT constraint have save the
table's setting ? Can you show us step by step what you did so far?
"Bobby" <bobby2@.blueyonder.co.uk> wrote in message
news:1174470005.140442.271260@.e65g2000hsc.googlegroups.com...
> On 21 Mar, 09:06, "Uri Dimant" <u...@.iscar.co.il> wrote:
>> Hi
>> >> I have gone to enter a new record in the table, and none of the
>> >> defaults work. All still default to <null>.
>> He said that he inserted a new row as I understood it.
> That's correct. I didn't mean that I wanted to change existing values,
> what I meant was will default values only work on tables without
> existing data.
> However, I know now that they will work on tables with existing data.
> I guess I've been working with Access too long. In Access, if I set
> default values and then go to insert a new record directly into the
> table, I can see the default values appear in the new row as I type.
> However, if I do the same in SQL server, a load of nulls appear in the
> new row, where the defaults should be. The defaults only appear after
> I have closed the table and gone back into it. That's what confused
> me.
> Thanks for your help
> Colin
>|||Remember also that defaults are only assigned to columns that are NOT
part of the INSERT. If you do not use a column list you will not get
a default, even if you assign NULL.
INSERT TableName VALUES('abc', NULL)
That will only work with a two column table, and will not use defaults
for either column.
INSERT TableName (col1, col10) VALUES ('abc', NULL)
That will assign the specified values to those two columns, but assign
the default - or NULL if there is no default - to all other columns.
Roy Harvey
Beacon Falls, CT
On 21 Mar 2007 01:39:08 -0700, "Bobby" <bobby2@.blueyonder.co.uk>
wrote:
>Hello all,
>I thought that I knew how to do this, but I must be having a mental
>block. I have a SQL table, populated with 14,000 records. I have
>several int columns which I need to change the default value to 0
>(zero), and a datetime column which I would like to default to todays
>date and current time. I have gone into design view for each of the
>int columns and I have simply entered 0 in the "Default value" box.
>For the datetime column, I have changed the Default Value to
>getdate().
>I have gone to enter a new record in the table, and none of the
>defaults work. All still default to <null>.
>Any ideas why this is not working? Does it only work on a table
>without existing data?
>Thanks
>Colin

Default values in tables

Hello all,
I thought that I knew how to do this, but I must be having a mental
block. I have a SQL table, populated with 14,000 records. I have
several int columns which I need to change the default value to 0
(zero), and a datetime column which I would like to default to todays
date and current time. I have gone into design view for each of the
int columns and I have simply entered 0 in the "Default value" box.
For the datetime column, I have changed the Default Value to
getdate().
I have gone to enter a new record in the table, and none of the
defaults work. All still default to <null>.
Any ideas why this is not working? Does it only work on a table
without existing data?
Thanks
ColinBobby
It does work
CREATE TABLE #Test (c1 datetime DEFAULT GETDATE(),c2 INT DEFAULT 0)
INSERT INTO #Test DEFAULT VALUES
SELECT * FROM #Test
Check out that you have created default constraints
SELECT scobj.name, cols.name
FROM sysconstraints sc
INNER JOIN sysobjects scobj
ON sc.constid = scobj.id
AND sc.id=OBJECT_ID('tblname')
INNER JOIN syscolumns cols
ON sc.id = cols.id
AND sc.colid = cols.colid
GO
"Bobby" <bobby2@.blueyonder.co.uk> wrote in message
news:1174466348.874762.198710@.e1g2000hsg.googlegroups.com...
> Hello all,
> I thought that I knew how to do this, but I must be having a mental
> block. I have a SQL table, populated with 14,000 records. I have
> several int columns which I need to change the default value to 0
> (zero), and a datetime column which I would like to default to todays
> date and current time. I have gone into design view for each of the
> int columns and I have simply entered 0 in the "Default value" box.
> For the datetime column, I have changed the Default Value to
> getdate().
> I have gone to enter a new record in the table, and none of the
> defaults work. All still default to <null>.
> Any ideas why this is not working? Does it only work on a table
> without existing data?
> Thanks
> Colin
>|||On Mar 21, 1:39 pm, "Bobby" <bob...@.blueyonder.co.uk> wrote:
> Hello all,
> I thought that I knew how to do this, but I must be having a mental
> block. I have a SQL table, populated with 14,000 records. I have
> several int columns which I need to change the default value to 0
> (zero), and a datetime column which I would like to default to todays
> date and current time. I have gone into design view for each of the
> int columns and I have simply entered 0 in the "Default value" box.
> For the datetime column, I have changed the Default Value to
> getdate().
> I have gone to enter a new record in the table, and none of the
> defaults work. All still default to <null>.
> Any ideas why this is not working? Does it only work on a table
> without existing data?
> Thanks
> Colin
Existing data values in columns will not change when you introduce
default values. Only new records (insertions) will have default
values .
If you want to change for the existing records , you need to update
the value.
After updating the value , alter table not to allow nulls on these
columns|||Hi
He said that he inserted a new row as I understood it.
"M A Srinivas" <masri999@.gmail.com> wrote in message
news:1174467529.301295.252230@.l77g2000hsb.googlegroups.com...[vbcol=seagreen]
> On Mar 21, 1:39 pm, "Bobby" <bob...@.blueyonder.co.uk> wrote:
> Existing data values in columns will not change when you introduce
> default values. Only new records (insertions) will have default
> values .
> If you want to change for the existing records , you need to update
> the value.
> After updating the value , alter table not to allow nulls on these
> columns
>|||On 21 Mar, 09:06, "Uri Dimant" <u...@.iscar.co.il> wrote:
> Hi
>
> He said that he inserted a new row as I understood it.
>
That's correct. I didn't mean that I wanted to change existing values,
what I meant was will default values only work on tables without
existing data.
However, I know now that they will work on tables with existing data.
I guess I've been working with Access too long. In Access, if I set
default values and then go to insert a new record directly into the
table, I can see the default values appear in the new row as I type.
However, if I do the same in SQL server, a load of nulls appear in the
new row, where the defaults should be. The defaults only appear after
I have closed the table and gone back into it. That's what confused
me.
Thanks for your help
Colin|||Boddy
See my first reply to you. After setting DEFAULT constraint have save the
table's setting ? Can you show us step by step what you did so far?
"Bobby" <bobby2@.blueyonder.co.uk> wrote in message
news:1174470005.140442.271260@.e65g2000hsc.googlegroups.com...
> On 21 Mar, 09:06, "Uri Dimant" <u...@.iscar.co.il> wrote:
> That's correct. I didn't mean that I wanted to change existing values,
> what I meant was will default values only work on tables without
> existing data.
> However, I know now that they will work on tables with existing data.
> I guess I've been working with Access too long. In Access, if I set
> default values and then go to insert a new record directly into the
> table, I can see the default values appear in the new row as I type.
> However, if I do the same in SQL server, a load of nulls appear in the
> new row, where the defaults should be. The defaults only appear after
> I have closed the table and gone back into it. That's what confused
> me.
> Thanks for your help
> Colin
>|||Remember also that defaults are only assigned to columns that are NOT
part of the INSERT. If you do not use a column list you will not get
a default, even if you assign NULL.
INSERT TableName VALUES('abc', NULL)
That will only work with a two column table, and will not use defaults
for either column.
INSERT TableName (col1, col10) VALUES ('abc', NULL)
That will assign the specified values to those two columns, but assign
the default - or NULL if there is no default - to all other columns.
Roy Harvey
Beacon Falls, CT
On 21 Mar 2007 01:39:08 -0700, "Bobby" <bobby2@.blueyonder.co.uk>
wrote:

>Hello all,
>I thought that I knew how to do this, but I must be having a mental
>block. I have a SQL table, populated with 14,000 records. I have
>several int columns which I need to change the default value to 0
>(zero), and a datetime column which I would like to default to todays
>date and current time. I have gone into design view for each of the
>int columns and I have simply entered 0 in the "Default value" box.
>For the datetime column, I have changed the Default Value to
>getdate().
>I have gone to enter a new record in the table, and none of the
>defaults work. All still default to <null>.
>Any ideas why this is not working? Does it only work on a table
>without existing data?
>Thanks
>Colin

Sunday, February 19, 2012

Default Value for Parameter with Query

I am trying to use the User!UserID field as a default value for a parameter. The list for the parameter is populated using a dataset that contains a list of names and User IDs. The value field for the query is User_ID. This field matches exactly with the User!UserID field, but it won't seem to default to that value. I'm sure I'm missing something obvious here. How can I get that list to default to my default value.If you keep User_ID in a field of fixed length (like char[X], not
varchar[X]), you may have spaces appended at the end of values which are
hard to notice. If you have trailing spaces in valid values and no trailing
spaces in the default value, default value won't be selected. See if this is
the case.
--
Dmitry Vasilevsky, SQL Server Reporting Services Developer
This posting is provided "AS IS" with no warranties, and confers no rights.
--
---
"leehaak" <leehaak@.discussions.microsoft.com> wrote in message
news:59867920-83DC-4248-8C90-F0DED42B7E12@.microsoft.com...
> I am trying to use the User!UserID field as a default value for a
parameter. The list for the parameter is populated using a dataset that
contains a list of names and User IDs. The value field for the query is
User_ID. This field matches exactly with the User!UserID field, but it
won't seem to default to that value. I'm sure I'm missing something obvious
here. How can I get that list to default to my default value.|||Thanks, unfortunately, that doesn't appear to be the problem, my User_ID field is a varchar field. I know that I can use User!UserID as a parameter in my query, and it works exactly as intended and has no trailing spaces. The value I'm setting as the default value should match my value field, correct? Are there any other requirements I'm missing to make those synch up?
"Dmitry Vasilevsky [MSFT]" wrote:
> If you keep User_ID in a field of fixed length (like char[X], not
> varchar[X]), you may have spaces appended at the end of values which are
> hard to notice. If you have trailing spaces in valid values and no trailing
> spaces in the default value, default value won't be selected. See if this is
> the case.
> --
> Dmitry Vasilevsky, SQL Server Reporting Services Developer
> This posting is provided "AS IS" with no warranties, and confers no rights.
> --
> ---
> "leehaak" <leehaak@.discussions.microsoft.com> wrote in message
> news:59867920-83DC-4248-8C90-F0DED42B7E12@.microsoft.com...
> > I am trying to use the User!UserID field as a default value for a
> parameter. The list for the parameter is populated using a dataset that
> contains a list of names and User IDs. The value field for the query is
> User_ID. This field matches exactly with the User!UserID field, but it
> won't seem to default to that value. I'm sure I'm missing something obvious
> here. How can I get that list to default to my default value.
>
>|||Here are a few things you can try.
1. Create a report with three text boxes. First text box should show value
of parameter. Second textbox should show value of Users!UserID. Last textbox
should show expression like (Parameters!Param.Value == Users!UserID). Run
this report and select the user you think is current, see if expression
returns true.
2. Make default value a query that would return first value from your table.
See if it is selected in this case.
Please, tell me you findings.
--
Dmitry Vasilevsky, SQL Server Reporting Services Developer
This posting is provided "AS IS" with no warranties, and confers no rights.
--
---
"leehaak" <leehaak@.discussions.microsoft.com> wrote in message
news:69A7ECF1-3BC4-4B5D-B411-81DC6347C44A@.microsoft.com...
> Thanks, unfortunately, that doesn't appear to be the problem, my User_ID
field is a varchar field. I know that I can use User!UserID as a parameter
in my query, and it works exactly as intended and has no trailing spaces.
The value I'm setting as the default value should match my value field,
correct? Are there any other requirements I'm missing to make those synch
up?
> "Dmitry Vasilevsky [MSFT]" wrote:
> > If you keep User_ID in a field of fixed length (like char[X], not
> > varchar[X]), you may have spaces appended at the end of values which are
> > hard to notice. If you have trailing spaces in valid values and no
trailing
> > spaces in the default value, default value won't be selected. See if
this is
> > the case.
> >
> > --
> > Dmitry Vasilevsky, SQL Server Reporting Services Developer
> > This posting is provided "AS IS" with no warranties, and confers no
rights.
> > --
> >
> > ---
> > "leehaak" <leehaak@.discussions.microsoft.com> wrote in message
> > news:59867920-83DC-4248-8C90-F0DED42B7E12@.microsoft.com...
> > > I am trying to use the User!UserID field as a default value for a
> > parameter. The list for the parameter is populated using a dataset that
> > contains a list of names and User IDs. The value field for the query is
> > User_ID. This field matches exactly with the User!UserID field, but it
> > won't seem to default to that value. I'm sure I'm missing something
obvious
> > here. How can I get that list to default to my default value.
> >
> >
> >|||Thanks, I did this as a diagnostic, and discovered that the problem was case.
Apparently, the when determining whether the value matches a value in the
list, case is evaluated. I changed the case of the default value, and it
worked exactly as expected.
"Dmitry Vasilevsky [MSFT]" wrote:
> Here are a few things you can try.
> 1. Create a report with three text boxes. First text box should show value
> of parameter. Second textbox should show value of Users!UserID. Last textbox
> should show expression like (Parameters!Param.Value == Users!UserID). Run
> this report and select the user you think is current, see if expression
> returns true.
> 2. Make default value a query that would return first value from your table.
> See if it is selected in this case.
> Please, tell me you findings.
> --
> Dmitry Vasilevsky, SQL Server Reporting Services Developer
> This posting is provided "AS IS" with no warranties, and confers no rights.
> --
> ---
> "leehaak" <leehaak@.discussions.microsoft.com> wrote in message
> news:69A7ECF1-3BC4-4B5D-B411-81DC6347C44A@.microsoft.com...
> > Thanks, unfortunately, that doesn't appear to be the problem, my User_ID
> field is a varchar field. I know that I can use User!UserID as a parameter
> in my query, and it works exactly as intended and has no trailing spaces.
> The value I'm setting as the default value should match my value field,
> correct? Are there any other requirements I'm missing to make those synch
> up?
> >
> > "Dmitry Vasilevsky [MSFT]" wrote:
> >
> > > If you keep User_ID in a field of fixed length (like char[X], not
> > > varchar[X]), you may have spaces appended at the end of values which are
> > > hard to notice. If you have trailing spaces in valid values and no
> trailing
> > > spaces in the default value, default value won't be selected. See if
> this is
> > > the case.
> > >
> > > --
> > > Dmitry Vasilevsky, SQL Server Reporting Services Developer
> > > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> > > --
> > >
> > > ---
> > > "leehaak" <leehaak@.discussions.microsoft.com> wrote in message
> > > news:59867920-83DC-4248-8C90-F0DED42B7E12@.microsoft.com...
> > > > I am trying to use the User!UserID field as a default value for a
> > > parameter. The list for the parameter is populated using a dataset that
> > > contains a list of names and User IDs. The value field for the query is
> > > User_ID. This field matches exactly with the User!UserID field, but it
> > > won't seem to default to that value. I'm sure I'm missing something
> obvious
> > > here. How can I get that list to default to my default value.
> > >
> > >
> > >
>
>