No it's the opposite. I got a call from a user as I was tying to rewrite this yesterday. :(

I'm trying to say that I use to be able to get a newrow in a bizobject, an now Ihave to be in a IU to do it.

__Stephen

>Stephen,
>
>>Just one Q. I use to put allot of the WORK with data in the BizObject. In the latest version I now can only do some of that work in the GUI, which is confusing.
>
>I'm not sure what you're saying here...are you saying you WANT to put the data manipulation logic in the UI and can't? Although I don't recommend this approach, there's nothing that's changed since the previous version that would prevent you from doing this.
>
>>Case:
>>GUI has a save button. After the current DS is saved {normal} I needed to create an entry in another table. I use to have the BizObj responsible for adding a row or more and updating as needed per transaction and then passing the ds back via savedataset().
>
>I'm not sure why you feel you can't do this...the only API change we made in the current version is the NewRow method returns a DataRow rather than a boolean value. This gives you more information, not less.
>
>Regards,