I hope I'm reading your scenario correctly ... so let me give you my
approach.

I normally design a DAL (Data Access Layer) to access the database. I also
design a BAL (Business Access Layer) which basically reflects the expected
business scenario. Afterwards, this same BAL (an object object oriented
model), can be exposed in several ways, where 2 of the most common are:

** WebApps
In this case, and for GridView (as an example) I design a simple object
without behavior to simply be used as an object data source for the
GridView. This simple object is the one that knows how to bridge the BAL to
itself. Basically, its not the BAL that is used directly in the ASP.NET
controls, but an object which may be different according to the visual needs

** WebServices
Again, in this case I design a simple object (DataContract) without behavior
to simply be used as a flat structure for SOAP exposure. This simple
structure, again, is the one that knows how to bridge the BAL to itself. And
again, its not the BAL that is used directly in SOAP (WCF, WSDL), but an
object which may be different according to the SOAP needs.

To conclude, its the BAL that is shared. Each kind of exposure (which may be
designed by other teams) is responsible for using the BAL indirectly to
expose the required data performing any transformations it feels required
(example: via WebApp a BAL numeric value is exposed with currency format,
via WebService is exposed with numeric format and another property with the
currency type).

Hope it helps,
Tiago Halm