PARAMETER ORDER CHANGES IN CE? 2

[LMCRYER]

Using CR9 I developed a report with 6 parameters. I set them in the order which I wanted them to come up for users.
I then put the report out on CE 9, and for some odd reason the report parameters are now listed "out of order".

Example: Original report has 6 params
@PART_NO [EMPTY]
@PART_DESC_1 [EMPTY]
@PART_DESC_2 [EMPTY]
@PART_DESC_3 [EMPTY]
@PART_DESC_4 [EMPTY]
@PART_DESC_5 [EMPTY]


When moved to CE9, the parameters come in this order:
Parameter Value
@PART_DESC_2 [EMPTY]
@PART_DESC_3 [EMPTY]
@PART_DESC_4 [EMPTY]
@PART_DESC_5 [EMPTY]
@PART_NO [EMPTY]
@PART_DESC_1 [EMPTY]

I searched the kbase and couldnt find anything, has anyone had this issue and if so, how do I fix it? Its really important they get these questions in the right order...
Thanks



LMC

 

[lbass]

Not sure about this, but I think I've read about both of the following. It might be that CE is either ordering them according to the order in which they were created or that CE is ordering them alphabetically and that there is some variation in the way you named Part_Desc_1 that we cannot observe here. So in CR you could try adding a space before "NO" and check the name for desc_1, or you could try recreating the parameters in the correct order.

-LB

 

[bdreed35]

Between the time that you changed the order of the parameters, and then uploaded it to CE, did you save the report locally? I just thought we could eliminate that as a possibility since if you hadn't saved it, it may be reverting back to the order that was used when it was saved last.

~Brian

 

[LMCRYER]

Hm. I did save it locally first (renamed, from the original) and then saved it up into CE with the new name.
It is in the same folder though. I wonder if the fact that they both have the same stuff and reference the same stored procedure has anything to do with it? I will try all suggestions listed and will post results.

LMC

 

[bdreed35]

Are these Stored Procedure parameters? You may need to change the order that they are named in the SP. I think that may do the trick for you.

~Brian

 

[bdreed35]

If the parameters are actually Stored Procedure parameters, you may need to rearrange them inside the Stored Procedure.

I would look to see what order they are defined in the SP
It is probably:
@PART_DESC_2 [EMPTY]
@PART_DESC_3 [EMPTY]
@PART_DESC_4 [EMPTY]
@PART_DESC_5 [EMPTY]
@PART_NO [EMPTY]
@PART_DESC_1 [EMPTY]

If so, rearrange them to the order you want:
@PART_NO [EMPTY]
@PART_DESC_1 [EMPTY]
@PART_DESC_2 [EMPTY]
@PART_DESC_3 [EMPTY]
@PART_DESC_4 [EMPTY]
@PART_DESC_5 [EMPTY]

And then recompile the SP, then open the report, do a Verify Database, Save it locally, then Save it to CE under a brand new name.




~Brian

 

[LMCRYER]

Actually, only one of them are stored proc params (the part_no) - the others are not. Hm. Im going to try taking them all out and then recreating in order.

LMC

 

[LMCRYER]

I resolved this by going in and setting up the parameters that were NOT in the stored procedure to be inside of it.
I made sure they were in order. I then refreshed the datasource for the report and viola, it works beautifully.
It seems perhaps theres something weird about using params that are in a stored proc with some that are not (within one report) but..I havent been able to find that on the kbase!

Thanks to ALL who replied! =)



LMC