Well, you've hit right on one of the key differences between the editions.
We don't do much if any custom reporting for our Standard Edition customers,
so it hasn't been an issue for us. You might checkout the following document
that provides pretty good information about what reports are supported in
both editions vs. those that are only in the Enterprise edition. From that
you can extrapolate what data is and is not available in the Standard
Edition Data Warehouse.

http://www.microsoft.com/commercese...ew/editions.asp

--
Zoe Hart
Commerce Server MVP

"Hulot" <Hulot@discussions.microsoft.com> wrote in message
news:FC1A4F77-2974-4BA6-9788-7E14FEF5D1D7@microsoft.com...
> Hi Zoe
>
> Sorry for the long delay to reply. I will try to explain what has been
done:
> Reports have been built using BIA (Business Internet Analytics) in
Commerce
> Server Developer Edition. Whenever the development team uses the reports
> containing, for example, profile data (reports that are not supported by
> Commerce Standard) the site package cannot be restored in production
> environment, blocking the site deployment. The problem is that during
> development phase there were not any restrictions about which reports
within
> BIA should be available for each Commerce Server version - so it is
> impossible for the development team to be comfortable working with a
feature
> set available in development environment that will not be available when
the[vbcol=seagreen]
> site moves to real production environment.
>
>
>
> "Zoe Hart [MVP]" wrote:
> 
for[vbcol=seagreen] 
any[vbcol=seagreen] 
(Developer[vbcol=seagreen] 
deployment[vbcol=seagreen] 
done[vbcol=seagreen] 
Enterprise.[vbcol=seagreen] 
for[vbcol=seagreen] 

[ Post a follow-up to this message ]