Page 1 of 1

Designer and duplicated data columns

Posted: Fri Aug 13, 2010 10:16 am
by fuhrj
SQL Statement in my DataSource:

SELECT *
FROM tblCustomer AS C
LEFT JOIN tblCustomer AS C2 ON C2.custType = 1
WHERE C.custType = 0

In previous versions of the Designer, when you Retrieved Columns, it would automatically rename duplicated fields by adding a number to it. For example, phone, phone1.

I am using the March 2010 build and it no longer does that. So in the column list, you see something like this:

customer_name
phone
customer_name
phone

When you compile the report, the Designer complains that the report "already contains a definition for customer_name".

I imagine I can manually rename the columns, but that's kind of a pain when you have over 20 columns. Is there a way to get the auto-renaming feature back?

Thanks.

Designer and duplicated data columns

Posted: Fri Aug 13, 2010 2:22 pm
by Jan
Hello,

Problem solved. Patch will be available in next prerelease build.

Thank you.

Designer and duplicated data columns

Posted: Fri Mar 04, 2011 7:23 am
by gigipd
fuhrj wrote:SQL Statement in my DataSource:

SELECT *
FROM tblCustomer AS C
LEFT JOIN tblCustomer AS C2 ON C2.custType = 1
WHERE C.custType = 0

In previous versions of the Designer, when you Retrieved Columns, it would automatically rename duplicated fields by adding a number to it. For example, phone, phone1.

I am using the March 2010 build and it no longer does that. So in the column list, you see something like this:

customer_name
phone
customer_name
phone

When you compile the report, the Designer complains that the report "already contains a definition for customer_name".

I imagine I can manually rename the columns, but that's kind of a pain when you have over 20 columns. Is there a way to get the auto-renaming feature back?

Thanks.
I'm experiencing the same exact problem with the latest version just downloaded. I'm using version build 03/03/2011.

Designer and duplicated data columns

Posted: Sat Mar 05, 2011 4:46 am
by Alex K.
Hello,

We couldn't reproduce this bug. Could you explain your issue in more details and, if possible, send us a step-by-step guide how to reproduce the issue?

Thank you.