So, if I want a BO that will be populated via a stored procedure, do I really need to create a view or table just so the BOM has something to map to? I can envision CFPs coming to the rescue, except that seems like a lot of work to do v. setting up a view.



No biggie... just wondering if there's an efficient way to avoid cluttering up the back end.



TIA

________________
_____/ Regards,
____/ al

But in the scenario I'm describing I would want to deploy all the sprocs - they would be the sprocs that represented all the structures in my structure only DDT project. Are you saying they would mess with existing sprocs or remove sprocs deployed by the main DDT project which is maintaining the apps real data ? Maybe I'm misunderstanding how it all works, but I thought I could deploy just the sprocs from a project and existing sprocs wouldn't be touched. No?

There may be a bit of confusion. But let's just recap, if you decide to create a pseudo table to which a BO will be mapped in a live profile, you cannot prevent that table from being deployed. That was the point I was trying to make and all I was getting at in regards to the SPROCs.