Using the Data from Other Data Source is very powerful ... but manually entering the columns is pretty difficult. I notice that on the stand-alone report designer, it automatically adds the columns for the grouped field and all the result fields. Can this be added to the Reports.Web report designer too? It is very confusing to explain to report designers that they need to manually add columns that match the names of the Grouped field and the Results.
Thanks!
Auto-create columns for Data from Other Data Source
-
- Posts: 251
- Joined: Fri Feb 04, 2011 11:46 am
- Location: San Diego, CA
Auto-create columns for Data from Other Data Source
Hello,
We have fixed an error in the resulting dialog. Now when you select the column and the resulting function, the name of the column will be generated automatically. The update will be available in the next prerelease build from May, 24.
Thank you.
We have fixed an error in the resulting dialog. Now when you select the column and the resulting function, the name of the column will be generated automatically. The update will be available in the next prerelease build from May, 24.
Thank you.
-
- Posts: 251
- Joined: Fri Feb 04, 2011 11:46 am
- Location: San Diego, CA
Auto-create columns for Data from Other Data Source
The new build almost works 
It does add the Results columns to the datasource, but it does not add the "Group" column to the datasource automatically like the stand-alone report designer does. The group column is probably the most important column to have

It does add the Results columns to the datasource, but it does not add the "Group" column to the datasource automatically like the stand-alone report designer does. The group column is probably the most important column to have

Auto-create columns for Data from Other Data Source
Hello,
You are right, the columns for groups are not automatically added. We will fix this error to the next prerelease build on June, 1.
Sorry for the inconvenience.
Than you.
You are right, the columns for groups are not automatically added. We will fix this error to the next prerelease build on June, 1.
Sorry for the inconvenience.
Than you.